VSEWSS - The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'Negotiate,NTLM'."

I faced this issue after installing VSeWSS (Visual Studio Extensions for Windows SharePoint Services) V1.3. O/S was Windows Server 2003 SP2 and I was trying to package my solution for SharePoint in Visual Studio 2008 when it kept failing by giving following errors:

“The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'Negotiate,NTLM'.""

and (at times when I was trying different things) the following error:

“The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'Negotiate,NTLM'.”

Do the following to resolve, go to (try after each step in order):

0. If you are using domain account, make sure you are connected to that domain otherwise user (against which the VSeWSS site application pool is running) will not be able to authenticate.

1. Follow this article and make sure IIS enables NTAuthenticationProviders. http://support.microsoft.com/kb/215383

2. Start Menu > Administrative Tools > Local Security Policy > (Expand) Local Policies > Security Options > (Look for) Network Security: LAN Manager Authentication Level > (set it to) Send LM & NTLM – use NTLMv2 Session security if negotiated. > Hit OK and restart the system.

If above step doesn’t resolve the problem, make sure the following are true:

1. Enable the Anonymous access to the VSeWSS site (which the VSeWSS setup creates during installation).

2. Make sure you are able to access the VseWSS site.

3. Make sure correct address is there in the registry.
Start > Run > regedit (hit enter)
Then select following key in registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0
Look for “VSeWSSServiceURL” key and make sure it is pointing to an accessible address of your service site.

4. You may have to restart IIS, Visual Studio or computer depending upon what you change.

Best of luck

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

The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.

Image
  While configuring the SharePoint 2010 for Forms Based Authentication, I encountered above error. To get the problem, I had to change “IncludeExceptionDetailInFaults” to true somewhere. But WHERE? Here is what solved my problem: Go to following path: 1. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\SecurityToken 2. Open Web.config there. 3. Add following in the “behaviors > serviceBehaviors > behavior” node. <serviceDebug includeExceptionDetailInFaults="true"/> Now try to login and see what error it gives, off to a next error
Read more