SharePoint_Config database

We recently switched the SharePoint_Config database to Simple recovery model to control the transaction logs. However, the ldf file still gets larger than the actual database file(mdf).
I have researched some of the autogrowth/pre-sizing settings, and I just don't understand it for the log portion. Right now, they are just set to the default SQL Server settings.
Does anyone have any suggestions as to what I can do to keep the transaction log smaller than the database files or at least relatively small?
I have checked, and I do not have any active transactions at the moment.
Thanks!

It is still growing. Yesterday, it was at 51MB and now it is at 110MB(which I know is not much compared to others, but we really rely on the server that SharePoint is on), so I am guessing it grows after the database backup(@10:15pm), and then the growth
doesn't change much throughout the day since I am the only one using it for development.
Yes, it may be completely normal, but I just don't want it to continue to grow 50MB+ every night, if it is not normal.
I no longer truncate the logs every night since it is in Simple recovery. Should I still be doing that?
I tried to find out through internet research if I still needed to, but everyone was saying that Simple recovery takes care of the truncation when the file gets a certain size. Well is there a way to check the size that the auto truncation will take place?

Similar Messages

Change SharePoint_Config Database to simple recovery mode. Risk.

Hello,
we have SBS 2008 with Exchnage and OWA-Service.
The Logfile of SharePoint is very large (30 GB).
But we don't use SharePoint.
I want to change the recovery mode of SharePoint_Config Database to simple.
But i don't know, what of Application/Services/Programms use SharePoint Database.
What are the risks of changing SharePoint_Config Database to Simple Mode?
What of the Sevices/Programms use SharePoint Database ?
Thank You

Hi ,
As Dimitri pointed out, SharePoint DB is in SQL database, the change of it won't affect Exchange and Outlook Web Access.
If you use SharePoint in future, you may take a look at the following article about the effect to SharePoint database with simple recovery mode.
http://searchwinit.techtarget.com/tip/How-SQL-Server-recovery-models-impact-your-SharePoint-databases
Thanks
Daniel Yang
TechNet Community Support

Huge SharePoint_Config Database/Timer Job History Overflow

Hello All,
I know there are quite a few sites about this issue, but none of them seem to work for me so I was hoping for some help.
Just for reference, this is in my dev environment on a VM running:
SP2010
SQL Server 2008 R2
Windows Server 2008 R2
It is the same old story of SharePoint's "Delete Job History" timer job not running and therefor the “TimerJobHistory” database table growing massive. For the last couple of months
my drive keeps running out of space and putting a halt to my work. So I went to the Net looking for a solution. I found a few that looked promising, but either caused more problems or simply did not work. Now that I have my environment back up and running
I was hoping for some help in solving this.
Does anyone know how to purge the “TimerJobHistory” table so my SharePoint_Config database will not keep filling up my space? From there is there anyway to prevent this from happening again?
The “Delete Job History” will not run currently even though I have adjusted the days to keep history and increased the duration that the job should run.
So far here is what I tried and the results:
http://sharepoint.it-professional.co.uk/?p=228 – Runs for a while and seems promising, but keeps growing the log and database
file until out of space, then crashes. I have to spend a lot of time freeing up space, detaching, and reattaching the config database. At this point I have removed everything from that drive that I can so no more space can be freed.
Shrinking files – This is only a temporary fix and I heard that it is a bad idea to do this more than once every now and again anyway. I am sure my database is already fragmented terribly
(which also if anyone can point me to a working solution for defragging in SQL Server 2008 R2 I would greatly appreciate it.)
There are a number of other sites that make recommendations that seem to be… well… less than what would be considered a “good practice” so I avoided those.
For the time being I have done what I had hoped not to and turned the SharePoint Timer service off to prevent the database from filling up again. If I turn it back on the log fill will be full
in a matter of seconds which will move me back to no space and in a bad position.
This seems to be happening to all the devs here, but I got a bit too brave and tried to find a solution… I learn a lot from my mistakes though!
If any other information is needed, please let me know.
Any help would be GREATLY appreciated.
Thanks,
J.

Hi,
We need to reduce the amount of data being deleted by the timer job during each run, so I need to modify the daystokeephistory value of the timer job.
The following PowerShell script for your reference:
$history = Get-SPTimerJob | Where-Object {$_.name -eq "job-delete-job-history"}
$history.daystokeephistory = 25
$history.update()
$history.runnow()
More information:
http://convergingpoint.blogspot.com/2012/05/sharepoint-configuration-database-too.html
http://www.techgrowingpains.com/2012/01/out-of-control-sharepoint_config-database/
Best Regards
Dennis Guo
TechNet Community Support

Incorrect/Corrupt Farm Configuration database server name

I have a SharePoint 2007 farm (version 12.0.0.6219) with a corrupt configuration database (SQL Server 2008 R2) consisting of a Central Administration server and a database server for Windows SharePoint Services Database. In a failed attempt to move the configuration
database to a new SQL server, the farm is referring to a SQL server that no longer exists. All databases on the new SQL server have been successfully moved from the old SQL server, but SharePoint does not recognize the configuration database. The network name
of the old SQL server has been aliased to the never SQL server, so the farm is operational. But the
Servers in Farm page states the old server as the configuration database server.
After doing my own research, it appears to me the issue is in the Objects table in the
SharePoint_Config database below.
Id
ClassId
ParentId
Name
Status
Version
1
AF14B6A3-2152-41BB-9407-3BB3D8E30C10
3112E92F-B97D-481E-8CEB-03FDE15ED1A7
BD5B4337-4294-4FC4-8EE2-0D51968D05DB
0
0x00000000000007DD
2
990CCD53-6D0F-4998-A060-45408E818ED5
3112E92F-B97D-481E-8CEB-03FDE15ED1A7
5DAA8D3C-B6EF-443C-B6AC-E1F704E35A94
0
0x00000000000BDF1D
3
DA951888-B47A-473E-97C2-B0EF78226512
E6591A38-008A-4F23-A88F-36A181C7D4EB
AF14B6A3-2152-41BB-9407-3BB3D8E30C10
SharePoint_Config
0
0x00000000000007E3
4
109CA292-69CB-417D-AFDF-C2A9DCE44A1B
674DA553-EA77-44A3-B9F8-3F70D786DE6A
109CA292-69CB-417D-AFDF-C2A9DCE44A1B
SharePoint_Config
0
0x00000000000008E7
5
BD5B4337-4294-4FC4-8EE2-0D51968D05DB
E77AAF47-3CAC-4001-BC6B-5BCCB6486318
109CA292-69CB-417D-AFDF-C2A9DCE44A1B
Old SQL Server
0
0x00000000000007D4
6
5A9AAEA8-A7E8-490F-8107-3D61F0D2A4E5
E77AAF47-3CAC-4001-BC6B-5BCCB6486318
109CA292-69CB-417D-AFDF-C2A9DCE44A1B
Exchange server
0
0x0000000000039216
7
3886B6E4-0E9E-499B-96A0-7CC677F8A5D0
E77AAF47-3CAC-4001-BC6B-5BCCB6486318
109CA292-69CB-417D-AFDF-C2A9DCE44A1B
Web Server
0
0x00000000000BFE51
8
5DAA8D3C-B6EF-443C-B6AC-E1F704E35A94
E77AAF47-3CAC-4001-BC6B-5BCCB6486318
109CA292-69CB-417D-AFDF-C2A9DCE44A1B
New SQL server
0
0x00000000000BDF17
It looks like all I’d have to do delete row id’s ...E1F704E35A94 and ...45408E818ED5 (<red>red</red> row #’s 8 and 2) after shutting down all SharePoint Web Applications and services. Then update
Old SQL Server with New SQL Server. Possibly even deleting row ...B0EF78226512 (orange row # 3) could be done as it appears to be an orphaned part of the configuration. These ids are not referenced in any other table in this database.
Any help on this would be appreciated. Thanks in advance.
P.S. Sorry it looks like my table rendering didn't work as intended.
-----&gt;Executive Vector

are you using the SQL alias to pointing to the Config Database server?
did you stop all the timers services, admin services other services before moving the Config DB and configuring the alias to new server.if you did not then it will corrupted.
If you are not using the SQL Alias and using the sql server name then you cannot move it.
you need to rebuild new farm with creation of new Config DB, then create SSP /Web apps and attached your content Database.
Directly playing with the Config Database is not a good idea at all and i am sure deletion is not supported in any means.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

SQL database login for 'SharePoint_Config_2010' on instance 'DB server' failed. Additional error information from SQL Server is included below.

we formatted Database server and restored all the databases from the backup. but the sharepoint site is giving below error when i access the home page.
we have 3 application servers in that two are working fine, but only one server getting the below error.
SQL database login for 'SharePoint_Config_2010' on instance 'db server' failed. Additional error information from SQL Server is included below.
Login failed for user 'domain\user'.
could you help what is the issue?

Hi,
According to your post, my understanding is that you failed to access sharepoint site with one application server.
It was due to the MOM/SCOM Agent that has a SharePoint management pack installed, the agents Windows Service runs as ‘Local System’ and thus causes this.
The workaround is to either kill the SCOM agent service, or set it to run as a dedicated service account.
In addtion, I recommend to add the logon account of the SharePoint Timer service as a user of the SharePoint_Config database. Give role membership to the account db_owner.
You also need to add the SharePoint accounts back into sql server.
There are some similar articles for you to take a look at:
http://blog.blksthl.com/2012/04/26/login-for-sharepoint_config-login-failed-for-user-domaincomputername-scom-agent/
http://msdn.microsoft.com/en-us/library/jj551781(v=nav.70).aspx
http://sharepoint.stackexchange.com/questions/51623/moved-sql-databases-for-sharepoint-2010-and-now-have-a-3351-error
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Which of database list i need to backup sharepoint

I'm trying to deploy SharePoint server in Azure according this article (msdn.microsoft.com/en-us/library/azure/dn275957.aspx).
And I have a question about databases that I need to backup. I have more than 20 bases in the databases node.
Do I need to backup all of them? Is there among these bases unnecessary or temporary bases which don't need to backup? Or I need to backup Sharepoint_config database only?

Hi all,
You can follow this guide: http://technet.microsoft.com/en-us/library/ee428327(v=office.15).aspx

Shrink Sharepoint Config Database

Dear Experts,
Is it wise to Shrink Sharepoint_Config databases in MOSS 2007 / MOSS 2010 . The log files grow upto 40 GB and consume disk soace. Is ther a way to find what may be causing this.
Thanks,
Kunal Jaiswal

ou can always shrink your SQL server log file and set the database to simple recovery so that log files dont grow more. but this will be a problem when you plan to recover database.
http://microtechpoint.com/index.php?route=blog/article&article_id=10
Expand the Databases node and expand User Databases
Right-click the database, and click Properties,
which opens the Database Properties dialog
box.
In the Select a page pane, click Options.
View the current recovery model in the Recovery model
list box, which should be set to Full
Click the dropdown arrow in the recovery model section
and select the Simple recovery model
Click OK.
Right-click on the same database name and click Task-> Shrink->
Files
Use the File type drop-down menu and choose Log
You can use the default setting of Release Unused Space or select Reorganize pages before releasing unused space, and you can specify the file size by supplying a value in the Shrink file to option.
Note:
the shrink may take some time depending on how large the file is and how much it has to shrink.
After the shrink completes, change the recovery model back to Full by clicking the recovery model dropdown arrow and selecting the Full recovery
model
Keep it simple of you dont want to have log files
http://www.satheesh.net/2011/04/05/how-to-shrink-sql-sharepoint-database-log-files/
If this helped you resolve your issue, please mark it Answered

An error The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered after launching a ps1 script from cmd file.

I'm trying to load sharepoint script from *.cmd file.
I have Sharepoint 2010 installed on Windows 7 x64 and SQL server 2008r2.
My cmd file is:
Powershell -v 2 -NonInteractive -NoLogo -File 1.ps1
My sharepoint file 1.ps1 is:
$snapin="Microsoft.SharePoint.PowerShell"
if ($action -eq $null -or $action -eq '')
{<br />
# Action by default is complete uninstallation.
$action='uninstall'
$uninstall = $true
else
$action = $action.ToLower()
switch($action)
{ $_ -eq "uninstall" } { $uninstall = $true; break }
{ $_ -eq "removesolution" } { $removeSolution = $true; break }
{ $_ -eq "deactivatecorpus" } { $deactivateCorpus = $true; break }
{ $_ -eq "deactivatesupport" } { $deactivateSupport = $true; break }
default { Write-Host -f Red "Error: Invalid action: $action "; Exit -1 }
Check the Sharepoint snapin availability.
if (Get-PSSnapin $snapin -ea "silentlycontinue")
Write-Host "PS snapin $snapin is loaded."
elseif (Get-PSSnapin $snapin -registered -ea "silentlycontinue")
Write-Host "PS snapin $snapin is registered."
Add-PSSnapin $snapin
Write-Host "PS snapin $snapin is loaded."
else
Write-Host -f Red "Error: PS snapin $snapin is not found."
Exit -1
$url = "http://pc1/sites/GroupWork/"
$site= new-Object Microsoft.SharePoint.SPSite($url )
$loc= [System.Int32]::Parse(1033)
$templates= $site.GetWebTemplates($loc)
foreach ($child in $templates){ write-host $child.Name " " $child.Title}<br />
$site.Dispose()
The script works fine from the Sharepoint 2010 management shell after launching the shell from the start menu (or from windows cmd by entering powershell -v 2):
PS C:\2> .\1.ps1
PS snapin Microsoft.SharePoint.PowerShell is loaded.
GLOBAL#0 Global template
STS#0 Team Site
STS#1 Blank Site
STS#2 Document Workspace
MPS#0 Basic Meeting Workspace
MPS#1 Blank Meeting Workspace
MPS#2 Decision Meeting Workspace
MPS#3 Social Meeting Workspace
MPS#4 Multipage Meeting Workspace
CENTRALADMIN#0 Central Admin Site
WIKI#0 Wiki Site
BLOG#0 Blog
SGS#0 Group Work Site
TENANTADMIN#0 Tenant Admin Site
{248A640A-AE86-42B7-90EC-45EC8618D6B4}#MySite2 MySite2
{95629DC2-03B1-4C92-AD70-BC1FEAA49E7D}#MySite1 MySite1
{7F01CFE4-F5E2-408B-AC87-E186D21F624C}#NewSiteTemplate NewSiteTemplate
PS C:\2>
I have an access to the database Sharepoint_Config from current domain user and from other 2 users. All users have db_owner rights to the Sharepoint_Config database. But
i've loaded in windows from the user which is dbo in the database (dbo with windows authentication with domain\username for the current user). The dbo user has do_owner rights in the Sharepoint_Config database. I've tried to login under other users and launch
the cmd file but without success.
My PowerShell has version 2.0:
PS C:\2> $psversiontable
Name Value
CLRVersion 2.0.50727.5477
BuildVersion 6.1.7601.17514
PSVersion 2.0
WSManStackVersion 2.0
PSCompatibleVersions {1.0, 2.0}
SerializationVersion 1.1.0.1
PSRemotingProtocolVersion 2.1
After launching the script from 1.cmd file i get an errors:
C:\2>Powershell -v 2 -NonInteractive -NoLogo -File 1.ps1
PS snapin Microsoft.SharePoint.PowerShell is registered.
The local farm is not accessible. Cmdlets with FeatureDependencyId are not regis
tered.
Could not read the XML Configuration file in the folder CONFIG\PowerShell\Regist
ration.
Could not find a part of the path 'C:\2\CONFIG\PowerShell\Registration'.
No xml configuration files loaded.
Unable to register core product cmdlets.
Could not read the Types files in the folder CONFIG\PowerShell\types.
Could not find a part of the path 'C:\2\CONFIG\PowerShell\types'.
"No Types files Found."
Could not read the Format file in the folder CONFIG\PowerShell\format.
Could not find a part of the path 'C:\2\CONFIG\PowerShell\format'.
No Format files Found.
PS snapin Microsoft.SharePoint.PowerShell is loaded.
New-Object : Exception calling ".ctor" with "1" argument(s): "The Web applicati
on at http://Pc1/sites/GroupWork/ could not be found. Verify t
hat you have typed the URL correctly. If the URL should be serving existing con
tent, the system administrator may need to add a new request URL mapping to the
intended application."
At C:\2\1.ps1:48 char:18
+ $site= new-Object <<<< Microsoft.SharePoint.SPSite($url )
+ CategoryInfo : InvalidOperation: (:) [New-Object], MethodInvoca
tionException
+ FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.Power
Shell.Commands.NewObjectCommand
Please help me. I don't understand why the script is launched from the sharepoint management shell but doesn't work from the cmd file.

I have an answer for my problem: for solving a problem I've made several steps:
1. Run farm installation under AD admin credentials - runas /user:Domain1\DomainAdmin1 "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\psconfigui.exe".
This user has been added as farm administrator in the wizard.
This user has been added as DBO in the SQL Server. (This is the main difference with my previous attempts)
2. Execute a command Add-SPShellAdmin Domain1\UserAccount1 in
the Management Shell of Sharepoint.
3. Run SQL server and add Sharepoint_Shell_Access to the Domain1\UserAccount1
(my main account) in the Config database
4. Run CMD file only from Start->Run menu.
runas /user:Domain1\UserAccount1 "C:\1.cmd".
Do not use Total Commander command prompt or file list for executing *.cmd of *.bat files without root administrator account.
Thanks all for help.

Error while deploying Sandbox Solution in SharePoint 2010 using Visual Studio

Hi,
I am creating a custom webpart as a sandbox solution.
While deploying I am getting an error
Error occurred in deployment step 'Retract Solution': <nativehr>0x80070005</nativehr><nativestack></nativestack>Access denied.
I have necessary permissions and part of admin group.
Please suggest what could be the issue.

Hello,
can you check if your account have access to the SharePoint_Config database? if it's still doesn't work, check if the used account is a local administrator of the machine
Best regards, Christopher.
Blog |
Mail
Please remember to click "Mark As Answer" if a post solves your problem or
"Vote As Helpful" if it was useful.

While loading site collection in SharePoint 2010, Error shows "Could not find the file or assembly or one of its dependencies. The system cannot find the file specified."

I have restored one web application in SharePoint Server 2010 from a different domain and can complete successfully. Changed each users domain also to old to new one by using Move-SPUser. But While accessing the site collection it is showing an error
that "Could not load file or assembly 'A##.SP.Intranet, Version=1.0.0.0, Culture=neutral, PublicKeyToken=03b4f320ebedaffc' or one of its dependencies. The system cannot find the file specified."
What may be the reason? Please help me to solve this issue since I am stuck up on this .
Regards
Mine1981

Hi Nico
Martens,
Thank you for your reply. But
how can I find out the custom solutions in the source farm. I didn't got any other details regarding this farm other than WSS_Content, Web application Database, SharePoint_Config database back ups.
Please help me to solve the
issue.
Regards
Mine

Error occurred in deployment step 'Install app for SharePoint': We're sorry, we weren't able to complete the operation, please try again in a few minutes. If you see this message repeatedly, contact your administrator.

While deploying sharepoint hosted app i am getting error "Error occurred in deployment step 'Install app for SharePoint': We're sorry, we weren't able to complete the operation, please try again in a few minutes. If you see this message repeatedly, contact
your administrator.". From the developer site i remove the app manually and after deploying i am getting the same error again.
Harminder singh

I was trying to install SharePoint 2013 on premise development environment and encountered the following issues while deploying the app using Visual studio 2013.
Please refer these articles for configuration settings.
http://blogs.msdn.com/b/how24/archive/2013/06/14/prepare-your-sharepoint-2013-farm-for-app-development-and-debugging.aspx
http://www.codeproject.com/Articles/515677/MyplusFirstplusSharepoint-HostedplusAppplusinplus2
http://blogs.technet.com/b/mspfe/archive/2013/01/31/configuring-sharepoint-on-premise-deployments-for-apps.aspx
http://aanuwizard.com/2012/12/07/article-14-from-30-system-account-can-not-deploy-or-purchase-an-app-in-sharepoint-2013-rtm/
Error 1:
Error occurred in deployment step 'Install app for SharePoint': The System Account cannot perform this action.
Error 2:
The local SharePoint server is not available. Check that the server is running and connected to the SharePoint farm.
Error 3:
Error occurred in deployment step 'Install app for SharePoint': We're sorry, we weren't able to complete the operation, please try again in a few minutes. If you see this message repeatedly, contact your administrator.
Solution:
For error 1, follow these instructions:
a. Create a new domain account DOMAIN\myApp_Admin
b. add DOMAIN\myApp_Admin to local admin group
c. add DOMAIN\myApp_Admin to Farm Administrators group
   Central Admin site --> Site Settings --> People and groups
   Add DOMAIN\myApp_Admin
For error 2 & 3, follow these instructions:
1. Grant DOMAIN\myApp_Admin accont a sysadmin server role on SQL server
2. Open SharePoint Power Shell and execute Add-SPShellAdmin <DOMAIN\myApp_Admin> command.
3. Grant DOMAIN\myApp_Admin a db_owner rights to web application Content database that you would like to use for debugging SharePoint 2013 app.
4. Make sure following roles are assigned for SharePoint_Config database
   SharePoint_Shell_Access
   SPDDataAccess
   public
5. Make sure following roles are assigned for SharePoint_Content database
   db_owner
5. Make sure following roles are assigned for SharePoint_AdminContent database
   public

EXECUTE permission was denied on the object 'proc_putObjectTVP'

Today I have seen the following error on one of my SharePoint servers.
The EXECUTE permission was denied on the object 'proc_putObjectTVP', database 'SharePoint_Config', schema 'dbo'.
The account that was denied EXECUTE permissions is the Service Application App Pool account.
Having googled the problem - most posts seem to suggest manually granting execute rights to the WSS_Content_Application_Pools role on the SharePoint_Config database to the following stored procedures:
[dbo].[proc_putObjectTVP]
[dbo].[proc_putObject]
[dbo].[proc_putDependency]
However it seems odd that there is not a SharePoint way to do this rather than modifying SQL permissions via SQL Management Studio. Has anyone else encountered this problem and is there a SharePoint way to fix it?
I should add that Microsoft say this about Service and other Application Pool accounts:
"This account is assigned to the WSS_CONTENT_APPLICATION_POOLS role associated with the farm configuration database."
https://technet.microsoft.com/en-us/library/cc678863%28v=office.15%29.aspx#Section3

Hi,
From your description, you might find error 5214 in event log, one or more of the following might be the cause:
The service account to which SharePoint is set does not have sufficient permissions to the database to which it is trying to connect.
The service account is not set up properly in SharePoint.
When using least privilege setup of the Farm.
Please perform the steps below and test the issue again:
1. Expand Databases then expand the SharePoint_Config Database.
2. Expand Security -> Roles -> Database Roles
3. Find WSS_Content_Application_Pools role, right click it, and select Properties
4. Click on Securables and click Search
5. Next click Specific objects and click OK
6. Click Object Types and select Stored Procedures. Click OK
7. Add the Stored Procedure 'proc_putObjectTVP' and click OK (if it does not automatically grant it exec permission; you need to click the checkbox on "execute" and save it)
Regards,
Rebecca Tu
TechNet Community Support

Sharepoint 2010 SQL Backups to taken

Hi,
What are the DB's needs to backed up on regular basis for share point?
One back up that I know is "Sharepoint Content Database".
Please Explain!
Thanks,
Meenakshi

Hi,
According to your description, my understanding is that you want to know which SharePoint database needs to be backed up.
Per my knowledge, besides the "SharePoint Content Database", you also need to back up "SharePoint_Config" database and some other sevice applications database such as "Managed Metadata service application","Managed Metadata
service application","PerformancePoint Services service application","User Profile service application" databases.
More information:
Back Up a Content Database from SharePoint 2010
Thanks
Best Regards
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Regarding VS Web part Solution Deployment Permission in SharePoint Server other than Admin

Hi,
While deploying the Visual Studio Web part, one error occurred i;e, “Error occurred in deployment step 'Recycle IIS Application Pool': The local SharePoint server
is not available. Check that the server is running and connected to the SharePoint farm.”
Actually we want that two user can deploy their web part simultaneously. One is admin that is able to deploy web part. But another user is facing this problem.
Solution which we have tried:
Make Local admin to that user.
Assign db_owner permission to that user in database.
Add that user in WSS_Admin_WPG group.
Add in Farm administrator group.
But still we are facing the same issue

Hello,
To be able to deploy solution, the user needs to have permissions on SharePoint_Config Database too. (maybe also the SharePoint_Admin database too)
Best regards, Christopher.
Blog |
Mail
Please remember to click "Mark As Answer" if a post solves your problem or
"Vote As Helpful" if it was useful.
Why mark as answer?

Deploy app in Visual Studio 2013 error

When i try to deploy my app in Visual Studio 2013 i get this error:
Error occurred in deployment step 'Install app for SharePoint': We're sorry, we weren't able to complete the operation, please try again in a few minutes. If you see this message repeatedly, contact your administrator.
What could the problem be?

Hi,
The following steps for your reference:
1. Grant DOMAIN\myApp_Admin accont a sysadmin server role on SQL server
2. Open SharePoint Power Shell and execute Add-SPShellAdmin <DOMAIN\myApp_Admin> command.
3. Grant DOMAIN\myApp_Admin a db_owner rights to web application Content database that you would like to use for debugging SharePoint 2013 app.
4. Make sure following roles are assigned for SharePoint_Config database
   SharePoint_Shell_Access
   SPDDataAccess
   public
5. Make sure following roles are assigned for SharePoint_Content database
   db_owner
6. Make sure following roles are assigned for SharePoint_AdminContent database
   public
More information:
http://sharepointinterface.com/2012/12/21/whaddaya-mean-i-cant-deploy-my-sharepoint-app/
https://kolliparachandra.wordpress.com/2014/09/02/apps-development-visual-studio-issues/
Best Regards,
Dennis Guo
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

SharePoint_Config database

Similar Messages

Maybe you are looking for