Starting to see people getting stuck on this with SBS essentials. Migrating from an existing SBS 2003 where the netbios domain name is 16 characters or longer.
On SBS 2003 it gracefully would handle this. On SBS 2011 Essentials the symptom you get is
Existing domain name too long 16 characters: http://social.technet.microsoft.com/Forums/en-IN/smallbusinessserver/thread/bab3b80a-61c6-4d6a-91e1-b0629fd7e9a8
Hang loose as we determine what the best cause of action is. Bottom line, count up the number of characters in the netbios domain name.
===============
I'm seeing this error message when attempting Win7 join to domain: “An unexpected error has occurred. To resolve this issue, contact the person responsible for your network.” According to http://onlinehelp.microsoft.com/sbs2011essentials/computer-connection-support-1.aspx the issue could be "The WSS Certificate Web Service might not be running." The service is running, and stopping / starting does not change issue. CSetup.log follows: [11/11/2011 14:29:37 a8c] wmain: Start of CSetup [11/11/2011 14:29:37 a8c] CoCreateInstance CLSID_DOMDocument60 succeeded. [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - selectSingleNode [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - get_firstChild [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - get_nodeValue [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - SysAllocString value: JLMSBS2011 [11/11/2011 14:29:37 a8c] CoCreateInstance CLSID_DOMDocument60 succeeded. [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - selectSingleNode [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - get_firstChild [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - get_nodeValue [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - SysAllocString value: 192.168.111.4 [11/11/2011 14:29:37 a8c] CoCreateInstance CLSID_DOMDocument60 succeeded. [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - selectSingleNode [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - get_firstChild [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - get_nodeValue [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - SysAllocString value: 50 [11/11/2011 14:29:37 a8c] CoCreateInstance CLSID_DOMDocument60 succeeded. [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - selectSingleNode [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - get_firstChild [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - get_nodeValue [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - SysAllocString value: Administrator [11/11/2011 14:29:37 a8c] CoCreateInstance CLSID_DOMDocument60 succeeded. [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - selectSingleNode [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - get_firstChild [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - get_nodeValue [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - SysAllocString value: en-US [11/11/2011 14:29:37 a8c] CoCreateInstance CLSID_DOMDocument60 succeeded. [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - selectSingleNode [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - get_firstChild [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - get_nodeValue [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - SysAllocString value: 1033 [11/11/2011 14:29:37 a8c] CoCreateInstance CLSID_DOMDocument60 succeeded. [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - selectSingleNode [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - get_firstChild [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - get_nodeValue [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - SysAllocString value: JuniorLeagueofMemphis [11/11/2011 14:29:37 a8c] CServer::GetNodeValue - Failed to Copy Node Value: hr = 0x8007007a [11/11/2011 14:29:37 a8c] Failed to load server domain netbios name from server info xml file C:\Windows\Temp\Client Deployment Files\ServerInfo.Xml: hr =0x8007007a [11/11/2011 14:29:37 a8c] wmain: CServer::LoadInfoFromXml failed: hr = 0x8007007a [11/11/2011 14:29:37 a8c] wmain: Unexcepted error occured - exiting program. [11/11/2011 14:29:39 a8c] wmain: End of CSetup: hr=0x8007007aThe key hint there is that it's getting stuck on the server domain netbios name from the server xml file.
If you enjoyed this article, please consider sharing it!
Is there a fix for this? I am having this issue.
Checking on the status, it’s still an open bug in connect.
I think I figured out a work around;
Run the connect
After the error, go to the temp folder in Windows (C:\Windows\Temp\Client Deployment Files\), correct the NetBios information in the XML file, and then run the connect.exe application from within that folder. If you re-run it from the Connect website, it will overwrite the changes to the XML file.
So far so good; now the question is how to correct the original XML file so it pushes out correctly.
Ah; the prices we pay for the sins of our fathers…or our own sins from when we didn’t know any better.
I ran into an identical issue with the XML file. In my case, the Netbios Domain name was different from the Domain name. The connect wizard and xml file use the Domain name (not the Netbios Domain name). This causes the authentication to fail with unknown user / wrong password.
If I edit the xml file, I find the the Netbios Domain name used is not correct. If I change it to the actual Netbios Domain name, the wizards completes as it should.
For instance, the domain name is Contoso and the Netbios Domain name (aka Pre-Windows 2000 name) is HOME, the xml file will use Contoso rather than HOME for the Netbios Domain. Wizard fails.
Edit the xml file to use HOME for Netbios Domain, save it in the temp directory and execute the wizard. Wizards runs correctly.
This appears to be a bug. Anyone know where, on the server, the connect wizard builds the xml file? I would like to change it on the server before it pushes it out.
Thank you,
Gary
I ran into an identical issue with the XML file. In my case, the Netbios Domain name was different from the Domain name. The connect wizard and xml file use the Domain name (not the Netbios Domain name). This causes the authentication to fail with unknown user / wrong password.
If I edit the xml file, I find the the Netbios Domain name used is not correct. If I change it to the actual Netbios Domain name, the wizards completes as it should.
For instance, the domain name is Contoso and the Netbios Domain name (aka Pre-Windows 2000 name) is HOME, the xml file will use Contoso rather than HOME for the Netbios Domain. Wizard fails.
Edit the xml file to use HOME for Netbios Domain, save it in the temp directory and execute the wizard. Wizards runs correctly.
This appears to be a bug. Anyone know where, on the server, the connect wizard builds the xml file? I would like to change it on the server before it pushes it out.
Thank you,
Gary
Another user, Green Yi
<http://social.microsoft.com/Profile/en-US?user=Green+Yi>, has
replied to a thread you have subscribed to in the Windows Small
Business Server
<http://social.microsoft.com/Forums/en-US/partnerwinserversbs/threads/>
Forum.
Thread TitleCannot connect domain-joined workstations after SBS 2011
Essentials Migration
<http://social.microsoft.com/Forums/en-US/partnerwinserversbs/thread/085
ccc95-cb12-4c78-8f37-2dd2ddd6f99f/>
Started by: Peter Opert
<http://social.microsoft.com/Profile/en-US?user=Peter+Opert>
Reply:
Hi Peter,
Thank you for your patience.
After testing this problem in my lab, I encounter the same problem.
In addition, I forwarded this issue to product team for the bug
check. Finally,we figure out it is a bug of the Connect Computer
wizard(SBS2011 Essentials). Now, our engineers are working on this
issue and trying to find out the root cause of this problem.
For you, we have a workaround to fix this connect computer problem.
1. On the client machine, edit the *ServerInfo.Xml* file at the
following location:
*C:\Windows\Temp\Client Deployment Files\ServerInfo.Xml*
2. Find the following contents:
3. Manually change the *DomainNetBiosName *value per your network
settings.
After that, please running CSetup from the temp folder above.
At this time, the client should be able to run the connect computer
wizard successfully.
————————————————————————
Best regards,
*Green Yi
*Partner Online Technical Community
————————————————————————
—————–