SPDocKit Consultant
Try it for FreeContact UsProduct Site
  • SPDocKit Consultant by Syskit
  • Product Updates
    • SPDocKit Consultant 12
    • SPDocKit Consultant 11.1.0
    • SPDocKit Consultant 11
    • SPDocKit Consultant 10
    • SPDocKit Consultant 9.1.0
    • SPDocKit Consultant 9
    • SPDocKit Consultant 8.0.3
    • SPDocKit Consultant 8
  • Requirements
    • SharePoint On-Premises User Permissions Requirements
    • Supported SharePoint Editions
    • System Requirements
    • Server Load Permission Requirements
    • Service Application Permission Requirements
  • Installation
    • Installation Guide
    • Upgrade to the Latest Version
    • Uninstallation Guide
    • PowerShell Guide
  • Activation
    • Activation Privacy Statement
    • Online Activation
    • Offline Activation
    • Manage License
    • Activation FAQ
    • Consultant License FAQ
  • Get To Know SPDocKit Consultant
    • Backstage Screen
      • Options Wizard
      • Compare Wizard
    • Farm Explorer Screen
      • Farm Dashboard
      • Farm Explorer Reports
      • Passwords and Product keys
    • Best Practices Screen
    • Snapshots Screen
    • PowerShell Commands
  • How To
    • Create Snapshot
    • Farm Documentation
      • Create Farm Documentation
      • Customize Documentation Template
    • Compare Wizard
      • Compare Farms
      • Compare Servers
      • Compare Web Applications
      • Compare Site Collections
      • Compare Web.Config Files
    • Best Practices
      • Available Best Practices Reports
      • Create Custom Best Practices Reports
      • Personalize Best Practices Reports
    • Generate an AutoSPInstaller XML Configuration File
  • FAQ
    • Miscellaneous
    • Security
    • Troubleshooting
      • RPC Server is Unavailable
      • Could not access content database
      • Error occurred while loading Web Application
      • Error occurred while trying to load ‘Problems and Solutions’ and ‘Rule Definitions’
      • Error while loading IIS Settings Information
      • Errors while trying to load the SharePoint farm
      • Errors while loading server information
      • Failed at retrieving SQL Accounts from the following servers
      • The service application 'UPA Name' does not have any proxies that are default in a proxy group
      • SQL Server is unavailable
  • Known Issues
    • CREATE TABLE permissions denied
    • Distributed Cache loading issue
    • Load crashes with NullReference exception
    • Available Windows updates
    • PowerPivot FileNotFoundException issue
    • Unaccounted differences in the UPA settings
Powered by GitBook
On this page
  • Summary
  • Solution

Was this helpful?

  1. Known Issues

CREATE TABLE permissions denied

An error appears in the ULS log, stating that SPDocKit Snapshot Wizard or SPDocKit PowerShell module processes are trying to create tables in SharePoint databases.

Summary

Errors appear in the ULS log that states that SPDocKit Snapshot Wizard or SPDocKit PowerShell module processes are trying to create tables in SharePoint databases.

First and foremost, SPDocKit Snapshot Wizard or SPDocKit PowerShell module does not create tables or modify SharePoint databases during the snapshot process. The problem occurs when there is a permissions issue when taking a snapshot.

SPDocKit Snapshot Wizard and SPDocKit PowerShell module query the NeedsUpgrade property of the SharePoint database. The query fails because of the lack of SELECT permission from the Versions table. This causes SharePoint to erroneously conclude that the database should be upgraded, but fails because the CREATE TABLE permission is missing as well. When the permissions are correctly set up, there are no attempts to create tables.

The issue can easily be reproduced in PowerShell by running the snapshot is taken using the account that lacks sufficient permissions:

    $myDB = Get-SPDatabase | ?{$_.Name -eq "[SPDatabaseName]"}
    $myDB.NeedsUpgrade

After running these commands, two things can be noticed:

  1. The NeedsUpgrade property will return the wrong value: it will always be true.

  2. CREATE TABLE errors will appear in the ULS log.

Solution

Please ensure that the user account running the SPDocKit Snapshot Wizard or SPDocKit PowerShell module has the required permissions on the database in question. You need to manually add the SELECT permission to the Versions table on all of the affected SharePoint databases.

  1. Run the following SQL query to grant the necessary permissions:

       USE [SPDatabaseName];  
       GRANT SELECT ON OBJECT::[dbo].[Versions] TO [DOMAIN\USERNAME];  
       GO
  2. Now, when your account/user has the proper privileges, please restart/rerun the Snapshot Wizard or the PowerShell Module.

PreviousKnown IssuesNextDistributed Cache loading issue

Last updated 2 years ago

Was this helpful?