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.
LVL 5
dexterhomeAsked:
Who is Participating?
 
dexterhomeAuthor Commented:
this is the KB arcticle I was looking at performing

http://support.microsoft.com/kb/934838
0
 
dexterhomeAuthor Commented:
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.IdentityNotMappedException was thrown.  Additional exception information: Some or all identity references could not be translated.
System.Security.Principal.IdentityNotMappedException: Some or all identity references could not be translated.
   at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
   at System.Security.Principal.NTAccount.Translate(Type targetType)
   at System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified)
   at System.Security.AccessControl.CommonObjectSecurity.AddAccessRule(AccessRule rule)
   at System.Security.AccessControl.RegistrySecurity.AddAccessRule(RegistryAccessRule rule)
   at Microsoft.SharePoint.PostSetupConfiguration.ResourceAccess.SetRegistryAccessRule()
   at Microsoft.SharePoint.PostSetupConfiguration.ResourceAccess.Secure()
   at Microsoft.SharePoint.PostSetupConfiguration.SecurityTask.SecureResources()
   at Microsoft.SharePoint.PostSetupConfiguration.SecurityTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

For more information, see Help and Support Center at
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
dexterhomeAuthor Commented:
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
0
 
dexterhomeAuthor Commented:
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.
0
 
dexterhomeAuthor Commented:
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.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.