SharePoint 2003: Portal creation failed: The server principal "user" is not able to access the database "db" under the current security context

I tried to restore SharePoint 2003 portal on SQL Server 2005 and it failed with following error even though I granted db owner rights to the user:

Portal creation failed System.Data.SqlClient.SqlException: The server principal "domain\sharepointadmin" is not able to access the database "ORG_SITE" under the current security context. at Microsoft.SharePoint.Portal.Data.a.c(SqlCommand A_0, Boolean A_1) at Microsoft.SharePoint.Portal.Data.a.b(SqlCommand A_0) at Microsoft.SharePoint.Portal.Topology.Database.d(a A_0, String A_1) at Microsoft.SharePoint.Portal.Topology.Database.a(String A_0, String A_1, String A_2, Boolean A_3) at Microsoft.SharePoint.Portal.Admin.c.b() at Microsoft.SharePoint.Portal.Admin.c.f()


Investigation the issue, it ended up as a SQL server's security issue.
Resolution:
I granted the domain\sharepointadmin user sysadmin role on the SQL Server 2005 and problem was solved! It restored portal smoothly.

Comments

Post a Comment

Feel free to give constructive feedback or let me know if it was helpful.

Popular posts from this blog

Unable to delete Shared Services Provider in SharePoint (MOSS)

Sometimes The SSP you create in MOSS are not created properly. This can be result of interruption while SSP was being created or in result of bad migration from SPS03 or MCMS to MOSS. Symptoms: 1. In left nav of SharePoint Central Administration, the name of your new SSP will not render rather, it will show up as text. 2. If you try to delete that from the Central Admin, the Delete option is disabled. Resolution: You should delete the SSP using stsadm command line tool (NOTE: My SSP's name is "SSP" which is specified after "title" in command: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsa dm -o deletessp -title "SSP" However, if you have any dependencies, you will have to delete them first or you will get following error when you try deleting it through command line tool: An object in the SharePoint administrative framework, "SharedResourceProvider Na me=SSP Parent=SPFarm Name=SharePoint_Config...
Read more

Cannot add a SimpleContent column to a table containing element columns or nested relations

Recently I ran into a problem while dealing with DataSets. I was adding a colum to an XSD through Visual Studio desinger and it kept failing with following error: Cannot add a SimpleContent column to a table containing element columns or nested relations. This is a known issue. However, the solution is not well known :) To be simple and streight forward, I tell you the solution which I tried and it worked, 1. Note down the column names, datatypes and relationships of the table. 2. Delete the table. 3. Add new table and add columns to it. 4. Redefine relationships. Best of luck.
Read more

Future of Hard-Disk Drives?

All tape drives of the past and most recent high capacity drives used today after all are magnetic drives (which use "ferromagnets" to store bits). Then Solid State Drives (SSDs) gave a new direction of fastest drives. I think that's the future of hard-drives for another 5 years. However, what if we had a mixture of two? The real future of storage I think will be storage using atomic structures with an addressing scheme and algorithm of an SSD and a four-atom-wide wires. Instead of flip-flops, "antiferromagnets" will be used and result will be lightening fast drives with thousands of TB of storage... ? Read about flip-flop replacement: Tiny hard drive stores one byte of data with just 12 atoms About connecting-wire replacement: Four-atom-wide wire may herald tiny computers I am ready to buy that drive as soon as it becomes available ;)
Read more