dexterhome
asked on
Sharepoint 3.0 / 2007 issue after dcpromo ran
Hi All,
I had a situation and had to promote a sharepoint server (windows server 2003 R2 x32)(Sharepopint 3.0 / 2007) to be a domain controller.
Note: inherited network - no sharepoint experience
Now this has been done i have lost access to the sharepoint intranet.
when connecting to intranet:7636 (our port) it just advises -service unavailable
i have found lots of information on the web but need some more questions answering.
Point:
SQL databases appear ok.
Possible solutions:
Some posts are advising that the original install was performed under a local account and dcpromo has removed that account - replace that account using admin commands
Issues with solution above:
Do I create a new domain account (specifically for sharepoint) first and use those credentials.
If that works how does it know to use the existing sql DBs.
Do i need to somehow map the new domain user to the sql DBs.
Help:
please can some advise a simple step by step guide to recover this issue.
I am trying to avoid attempting too many fixes that could possibly stop a valid solution.
I had a situation and had to promote a sharepoint server (windows server 2003 R2 x32)(Sharepopint 3.0 / 2007) to be a domain controller.
Note: inherited network - no sharepoint experience
Now this has been done i have lost access to the sharepoint intranet.
when connecting to intranet:7636 (our port) it just advises -service unavailable
i have found lots of information on the web but need some more questions answering.
Point:
SQL databases appear ok.
Possible solutions:
Some posts are advising that the original install was performed under a local account and dcpromo has removed that account - replace that account using admin commands
Issues with solution above:
Do I create a new domain account (specifically for sharepoint) first and use those credentials.
If that works how does it know to use the existing sql DBs.
Do i need to somehow map the new domain user to the sql DBs.
Help:
please can some advise a simple step by step guide to recover this issue.
I am trying to avoid attempting too many fixes that could possibly stop a valid solution.
ASKER
Update -
I tried to run the repair wizrd but it failed and created this event log entry
(It appears to be advising of mapping issue (so presume user account as kb article))-
Failed to secure the SharePoint resources.
An exception of type System.Security.Principal. IdentityNo tMappedExc eption was thrown. Additional exception information: Some or all identity references could not be translated.
System.Security.Principal. IdentityNo tMappedExc eption: Some or all identity references could not be translated.
at System.Security.Principal. NTAccount. Translate( IdentityRe ferenceCol lection sourceAccounts, Type targetType, Boolean forceSuccess)
at System.Security.Principal. NTAccount. Translate( Type targetType)
at System.Security.AccessCont rol.Common ObjectSecu rity.Modif yAccess(Ac cessContro lModificat ion modification, AccessRule rule, Boolean& modified)
at System.Security.AccessCont rol.Common ObjectSecu rity.AddAc cessRule(A ccessRule rule)
at System.Security.AccessCont rol.Regist rySecurity .AddAccess Rule(Regis tryAccessR ule rule)
at Microsoft.SharePoint.PostS etupConfig uration.Re sourceAcce ss.SetRegi stryAccess Rule()
at Microsoft.SharePoint.PostS etupConfig uration.Re sourceAcce ss.Secure( )
at Microsoft.SharePoint.PostS etupConfig uration.Se curityTask .SecureRes ources()
at Microsoft.SharePoint.PostS etupConfig uration.Se curityTask .Run()
at Microsoft.SharePoint.PostS etupConfig uration.Ta skThread.E xecuteTask ()
For more information, see Help and Support Center at
I tried to run the repair wizrd but it failed and created this event log entry
(It appears to be advising of mapping issue (so presume user account as kb article))-
Failed to secure the SharePoint resources.
An exception of type System.Security.Principal.
System.Security.Principal.
at System.Security.Principal.
at System.Security.Principal.
at System.Security.AccessCont
at System.Security.AccessCont
at System.Security.AccessCont
at Microsoft.SharePoint.PostS
at Microsoft.SharePoint.PostS
at Microsoft.SharePoint.PostS
at Microsoft.SharePoint.PostS
at Microsoft.SharePoint.PostS
For more information, see Help and Support Center at
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the post yagyashree
Either I am missing somethink or are these just links to issues with this promotion and not actually ways to fix my problem.
I found this through one of the links:
http://www.cleverworkarounds.com/2008/09/16/sometimes-microsoft-bashing-is-justified/
this is closer to my issues.
this post is advising demoting the server and then fixing sharepoint - with issues I meant add.
I was looking more for a fix I could effectively use
Either I am missing somethink or are these just links to issues with this promotion and not actually ways to fix my problem.
I found this through one of the links:
http://www.cleverworkarounds.com/2008/09/16/sometimes-microsoft-bashing-is-justified/
this is closer to my issues.
this post is advising demoting the server and then fixing sharepoint - with issues I meant add.
I was looking more for a fix I could effectively use
ASKER
I have now fixed my issue - here are my steps so it should be easier for people to follow:
1. I demoted my newly promoted dc to become a member server again.
2. I then reconfigured sharepoint using this very helpful guide here:
http://www.cleverworkarounds.com/2008/09/16/sometimes-microsoft-bashing-is-justified/
3. After this I still could not get to the admin panel which left me blind of this report
4. I then used this document as a guide to to check the IIS permissions for the account used.
http://support.microsoft.com/kb/823552
5. This effectively allowed sharepoint to work again and users to access it.
Job done - few.
1. I demoted my newly promoted dc to become a member server again.
2. I then reconfigured sharepoint using this very helpful guide here:
http://www.cleverworkarounds.com/2008/09/16/sometimes-microsoft-bashing-is-justified/
3. After this I still could not get to the admin panel which left me blind of this report
4. I then used this document as a guide to to check the IIS permissions for the account used.
http://support.microsoft.com/kb/823552
5. This effectively allowed sharepoint to work again and users to access it.
Job done - few.
ASKER
Thanks for your help with this issue - I have only rated B as your post did not really help, but did lead me to the guide that partially helped in the end.
ASKER
http://support.microsoft.com/kb/934838