Windows cannot bind to XXX domain. (Invalid Credentials) - Event ID: 1006 and 1030

Problem
You probably noticed that I’m checking through the event logs of our servers. I found another issue today! This one is related to a Windows Server issue.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1006
User: admin.XXX
Description:
Windows cannot bind to XXX domain. (Invalid Credentials). Group Policy processing aborted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

and

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
User: admin.XXX
Description:
Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Solution
I browsed a couple of Google results and found an interesting post.

5 Jan 2006 2:43 PM scole
I am not positive, but I think there was a problem with someone remoting into the server and never logging out. Then their password changed. I was able to go in and kill their connection (which had been open for 5 months). Hope this helps. Source

I looked into the Terminal Services Manager and found a user that was "idle" for a while. I told the manager to logout the user. After a few hours I checked the event log again and noticed that the errors were no longer occurring.

Guess this solved the problem! :-)

ContentDeploymentJobReport with ID '{e379594a-a267-4dfc-ae37-70f8f392798c}' was not found - Event ID: 4958

The Problem
Unfortunately there were several errors occurring on our source machine. These errors originated from the MOSS content deployment.

Event Type: Error
Event Source: Office
SharePoint Server
Event Category: Content Deployment
Event ID: 4958
Description:
Publishing: Content deployment job failed. Error: 'System.ArgumentOutOfRangeException:
ContentDeploymentJobReport with ID '{e379594a-a267-4dfc-ae37-70f8f392798c}' was not found.
Parameter name: jobReportId at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobReport.GetInstance(Guid jobReportId)
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.get_LastReport()
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.EnsureLastReport()
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Run(Boolean
runAsynchronously)'
For more information, see Help and Support
Center at http://go.microsoft.com/fwlink/events.asp.

In the SharePoint Logs I found:

07/01/2009 13:35:52.63 w3wp.exe (0x1120)
0x0958
CMS
Content Deployment 0 Unexpected
ContentDeploymentJobReport with ID '{e379594a-a267-4dfc-ae37-70f8f392798c}' was
not found in 'Job Reports' so throwing exception.

07/01/2009 13:35:52.63 w3wp.exe (0x1120)
0x0958 CMS
Content Deployment 5ro8
Critical Publishing:
Content deployment job failed. Error: 'System.ArgumentOutOfRangeException:
ContentDeploymentJobReport with ID '{e379594a-a267-4dfc-ae37-70f8f392798c}' was
not found. Parameter name: jobReportId at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobReport.GetInstance(Guid
jobReportId)
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.get_LastReport()
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.EnsureLastReport()
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Run(Boolean
runAsynchronously)'

This error always occurred with the same GUID. The error occurred every 15 minutes. This was actually the time the Quick Deployment Job was running. When I tried to open the history of the Quick Deployment Job, the error page below was displayed.

Then, when I was looking at the Deployment list: (<your site>/Quick Deploy Items/AllItems.aspx)

The attempts

I deleted all items, but it didn't work. Another side effect of what I did was that I couldn't test if the Quick Deployment Job worked or not, because it needed at least one item to start the task. As such, I recovered the items from the Recycling Bin.

I could not create a new path to the old location. This was because there could only be one path to one source-destination-pair. So this didn't work either.

The Solution
To fix the problem I deleted the old paths and Deployment Jobs. I created a new path and new Deployment Jobs on our server and it worked.

A downside to this solution is that I had to run a full deployment again, because all file GUIDs weren't matching. But that wasn't a big problem, because that seems to happen quite frequently with Sharepoint.

Search Query Webservice for Moss 2007 Tool

Great tool spotted by a collegue of mine @QNH!

It allows you to change property flags, generate the request XML, send the string to the web service and see the results in the UI.


Click here!

It's a great tool to test those bloody queries!

Get ready for SharePoint 2010!

I spotted a great site to figure out what you have to upgrade to version 13 ... euh 14 ;-). It's called SharePoint 2010.
Go see http://sharepoint.microsoft.com/2010/Sneak_Peek/Pages/Get_Ready.aspx or http://blogs.msdn.com/sharepoint/archive/2009/05/07/announcing-sharepoint-server-2010-preliminary-system-requirements.aspx

Cannot insert duplicate key row in object 'dbo.UserMemberships' - Event ID: 7888

On our front-end server the following error occurred:

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server General
Event ID: 7888

Description:
A runtime exception was detected. Details follow.
Message: Cannot insert duplicate key row in object 'dbo.UserMemberships' with unique index 'CX_UserMemberships_RecordId_MemberGroupId_SID'.
The statement has been terminated.

Techinal Details:
System.Data.SqlClient.SqlException: Cannot insert duplicate key row in object 'dbo.UserMemberships' with unique index 'CX_UserMemberships_RecordId_MemberGroupId_SID'.
The statement has been terminated.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.Office.Server.Data.SqlSession.ExecuteNonQuery(SqlCommand command)
at Microsoft.Office.Server.UserProfiles.WSSSynchSqlSession.SynchExecuteNonQuery(SqlCommand cmd, Boolean throwOnFail)
at Microsoft.Office.Server.UserProfiles.WSSSynchSqlSession.SynchExecuteNonQuery(SqlCommand cmd)
at Microsoft.Office.Server.UserProfiles.SiteSynchronizer.WriteChangeLogConsumed()
at Microsoft.Office.Server.UserProfiles.SiteSynchronizer.Synch()
at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Problem
The Profile database could not be synchronised. There were a couple of ‘databases’ that generated errors when Sharepoint synchronised the profiles.

Solution
(Source)

DEALOGIC:

HI delmarvamonkey, contacted Microsoft who told me it was because of an
old database that couldn't synchronise in the config database:

As
discussed on the phone, here the link to the command for deleting unsynchronized
databases:

http://technet.microsoft.com/en-us/library/cc263196.aspx

IN your case, just use:
stsadm -o sync -listolddatabases 1 to see
the old databases,
and: stsadm -o sync -deleteolddatabases 1 to delete the
links in the config_DB.

If you run these commands it should do it, but I
haven't actually tried it on the production server as yet.

I tried this solution and found that my problems disappeared and no futher errors occurred.

Moss 2007 SP2: Trail version Fix

Finally there's a hotfix on the web that fixes the SP 2 bug that degraded MOSS to a trial version of the application:

971620 - When you install the 2007 Microsoft Office servers Service Pack 2, the product expiration date is activated incorrectly. Source

To download, visit microsoft.com:

• 32-bit version
• 64-bit version

My First Blog-post

This is the first post on http://jasperbeerens.blogspot.com/

In the future you are going to find interesting information about .NET, SharePoint, MS CRM, etc. on this blog.

About the author:

I'm a MCTS certified .NET Software Engineer with a bachelor degree. I have a lot of experience with creating custom developed webapplications (ASP.NET - C#), programming webparts, and other components for MOSS (SharePoint) and MS CRM. I'm a Microsoft specialist in Dynamics CRM and MOSS. I like to work in a team, but I can also function very well on my own.

Because of my broad interest in technical things I love gadgets and mobile applications. In my spare time I do some cardio fitness to stay fit as well. Furthermore I like to watch movies, listen to music, and I like reading books.