asked on

Cannot join Win10 client to SBS 2011 Standard domain...

I've had this issue for a while and and now trying again to connect a new PC to the domain correctly with the http://connect instruction. What happens though is I get a Server Error in '/' Application. It is a Runtime Error that is not displayed on the new client. When I run the command on the server, I get a lot more:

-----------------------------------------------------
Server Error in '/' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load file or assembly 'Microsoft.SharePoint' or one of its dependencies. The system cannot find the file specified.

Source Error:

Line 1: <%@ Assembly Name="Microsoft.SharePoint"%><%@ Application Language="C#" Inherits="Microsoft.SharePoint.ApplicationRuntime.SPHttpApplication" %>

Source File: /global.asax Line: 1

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.SharePoint' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Version Information: Microsoft .NET Framework Version:2.0.50727.5737; ASP.NET Version:2.0.50727.5710

-------------------------------------

I'm really not a server guy at all, just a firefighter. But it's my hat to wear occasionally. I'm not sure why this error has ever existed. Regardless, I cannot get any new client to connect to the domain appropriately. It also seems that deploying the portable media doesn't help much, but that may be more of a DNS issue. I'd like to resolve this particular error though, and appreciate any help I can get.

ASKER CERTIFIED SOLUTION

Scott C

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Colin_UK

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Colin_UK

Just to add, personally I wouldn't simply join the domain (like you would on a standard Win server) as you will need to run an awful lot of additional commands on the server to provide the full SBS integration for that workstation.

The easiest way to make SBS reliable is ALWAYS USE THE WIZARDS (unfortunately).

Colin

SOLUTION

Larry Struckmeyer MVP

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Scott C

Agreed. As you said, you're not a "server guy". Getting in and changing files may break something that you are not able to fix.

Probably not in this case, but why take chances?

Firemedic41

ASKER

I added them, but that didn't seem to resolve the original error. Looks like I would need to add those lines regardless, but I even get this error specifically when I run the "connect" webapp on a browser on the server.

Firemedic41

ASKER

I likely could just join the domain the old fashioned way, but everything I seem to read says to use the wizards. This clearly has seemed ot be something on the server that I've been unable to track down.

Firemedic41

ASKER

So, I opted to just join the domain from the client side the old way, and yes, nothing had to be moved as it was a clean new unit. I wonder what (if anything) may be missed.

Although I did edit the XML files. I did not modify the build numbers. That would probably be a good thing to check, but again, I get this error seemingly regardless of the system that's been deployed (7 -10).

Any thoughts about what might be missed connecting the old way? Any other thoughts on why a SharePoint error is happening when trying to use the connect app?

Scott C

Nothing should be missing connecting the "old way". I've joined dozens if not hundreds using the old method and never ran into an issue.

Firemedic41

ASKER

Also, as far as the IP address goes, it's all statically assigned (I am a former network engineer...just not a MS server guy), and the DNS is pointed correctly with the domain appended for good measure. Not using DHCP for these machines. However, all lookups work fine internally, and the server can be browsed by name.

Firemedic41

ASKER

So although I did just cave in and connect the client the old way, I still seem to have an error on the server that is unexplained. :-/

I'm concerned that this issue isn't strictly a problem that is relegated to connecting a client to the domain.

Scott C

What error are you seeing on the server?

Is it showing up in the Event Logs?

Firemedic41

ASKER

Yep.

----------------------

Event code: 3006
Event message: A parser error has occurred.
Event time: 3/1/2017 12:27:23 PM
Event time (UTC): 3/1/2017 7:27:23 PM
Event ID: f0f194addc3148f9a539a45b6ab37572
Event sequence: 1
Event occurrence: 1
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/ROOT-104-131328700436598297
Trust level: Full
Application Virtual Path: /
Application Path: C:\inetpub\wwwroot\
Machine name: BAILEY

Process information:
Process ID: 27936
Process name: w3wp.exe
Account name: SAFDNET\spfarm

Exception information:
Exception type: HttpException
Exception message: Could not load file or assembly 'Microsoft.SharePoint' or one of its dependencies. The system cannot find the file specified.

Request information:
Request URL: http://192.168.1.254/connect/
Request path: /connect/
User host address: 192.168.1.108
User:
Is authenticated: False
Authentication Type:
Thread account name: SAFDNET\spfarm

Thread information:
Thread ID: 32
Thread account name: SAFDNET\spfarm
Is impersonating: False
Stack trace: at System.Web.Compilation.BuildManager.ReportTopLevelCompilationException()
at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters)

Custom event details:

***AND Details in XML View***
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="ASP.NET 2.0.50727.0" />
<EventID Qualifiers="32768">1310</EventID>
<Level>3</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-01T19:27:23.000000000Z" />
<EventRecordID>2355336</EventRecordID>
<Channel>Application</Channel>
<Computer>BAILEY.safdnet.local</Computer>
<Security />
</System>
- <EventData>
<Data>3006</Data>
<Data>A parser error has occurred.</Data>
<Data>3/1/2017 12:27:23 PM</Data>
<Data>3/1/2017 7:27:23 PM</Data>
<Data>f0f194addc3148f9a539a45b6ab37572</Data>
<Data>1</Data>
<Data>1</Data>
<Data>0</Data>
<Data>/LM/W3SVC/1/ROOT-104-131328700436598297</Data>
<Data>Full</Data>
<Data>/</Data>
<Data>C:\inetpub\wwwroot\</Data>
<Data>BAILEY</Data>
<Data />
<Data>27936</Data>
<Data>w3wp.exe</Data>
<Data>SAFDNET\spfarm</Data>
<Data>HttpException</Data>
<Data>Could not load file or assembly 'Microsoft.SharePoint' or one of its dependencies. The system cannot find the file specified.</Data>
<Data>http://192.168.1.254/connect/</Data>
<Data>/connect/</Data>
<Data>192.168.1.108</Data>
<Data />
<Data>False</Data>
<Data />
<Data>SAFDNET\spfarm</Data>
<Data>32</Data>
<Data>SAFDNET\spfarm</Data>
<Data>False</Data>
<Data>at System.Web.Compilation.BuildManager.ReportTopLevelCompilationException() at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters)</Data>
</EventData>
</Event>

Scott C

I'd suggest opening another question as this looks like it's something to do with SharePoint.

Be sure to add "SharePoint" as one of the topics.

Laroy Shtotland

Edit the supportedOS.xml as suggested above, then use Edge instead of Internet Explorer for http://connect/
Is SharePoint installed and running on the same ADC?

Firemedic41

ASKER

So the XML was updated. Using Edge doesn't change anything. And SharePoint is installed. I can close the question, but the fix is the same fix I've been doing and not the one per the question, which was using the "connect" feature that is clearly throwing the error. I can re-open under an additional SharePoint tag too as suggested. I'm curious as to why that error is occurring.

Firemedic41

ASKER

Still have the error, but I appreciate the feedback. Question re-opened with a SharePoint tag to try to resolve the error being seen.

Colin_UK

I know this was closed, but I think I should stress the importance of using http://connect vs manually joining the domain.

SBS is a collection of Microsoft servers, it includes Exchange and has a ready made Sharepoint server along with Remote Web Workspaces. All these additional services need to be configured, along with folder redirection, local admin assignment & various GPO's pre-made for a small business use.

When joining the domain manually the computer object will not be put into the correct OU in AD. It will be putting the computer in the Computers container instead of MyBusiness > Computers > SBSComputers container. The problem with this is that the computer and possibly users will not get the correct SBS Group Policies and other strange things can happen.

If you end up not using the Connect wizard, you need to go into Active Directory Users and Computers and move the computer object to the correct container.

Don't create anymore work for yourself than you have to, always use the SBS wizards. And believe me I have learn't this the hard way.

Firemedic41

ASKER

Colin, maybe I've just been lucky! I did go check in case I had to move the units, but it looks like all of my machines have landed correctly in MyBusiness > Computers > SBS Computers. I don't have anything in the Computers folder luckily!

Firemedic41

ASKER

And I would agree that using the Wizards are the best way generally. Not always the easiest when they don't sync up right, but always the preferred route.