Despite dealing with the (bad) tonsillitis, today (especially towards the end) proved to be productive. On tonight’s menu : dead domain controller demotion, plus checking Service Principal Names duplicate entries. That made me discover a lovely little utility included in windows : LDP.exe

Removing the SPN entry drove our Sharepoint blind, couldn’t see the database server anymore! That’s certainly linked to Kerberos. I’ve added again the SPN entry in ADSIEdit.msc and all is fine again.

More tomorrow!

It’s been now several days that I’m fighting against this error when trying to activate Sharepoint Publishing Infrastructure at the site collection level.

I’ve posted something about it in Technet Forums @ Microsoft, see the following link:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3528645&SiteID=1

Any help is welcome :-)

Cheers,

Max

Morning folks, this morning a weird issue (no, really?) some permissions simply disappeared during the night on some of our Sharepoint lists. No reasons for that, nothing in event logs. Classical. Had to set them back again, now it works fine.

This morning one of our users reported that his adwords editor suddenly keeps freezing. After trying to uninstall and reinstall without success, I tried to do it a bit harsher… and it worked! I uninstalled adwords editor, went to the user’s “Application Data” and “Local Settings\Application Data” folders and deleted there both “Google Adwords” folders. Then I reinstalled and it now works like a charm.

If you ever encounter an event ID 10536 error saying that “the external credentials in the SSO database are more recent”, check your system time and set it correctly. On this developer workstation, the time was set incorrectly as being on the 11th may while the correct date was the 15th may.

Event Type: Warning
Event Source: ENTSSO
Event Category: Enterprise Single Sign-On
Event ID: 10536
Date: 5/11/2008
Time: 4:47:19 PM
User: N/A
Computer: XXXXX-DEV
Description:
SSO AUDIT
Function: SetConfigInfo
Tracking ID: 7849f8bf-d3dc-47a5-bace-f6bdabbcc6d2
Client Computer: XXXXX-DEV (mmc.exe:5016)
Client User: XXXXX-DEV\Administrator
Application Name: {378278B5-C479-4D53-8A47-613FC6DAB2CA}
Error Code: 0xC0002A40, The external credentials in the SSO database are more recent.

Whenever you run into repeating error 18456 / Anonymous Logon failure on your SQL server, be sure to check that Single Sign-On has been set up properly on your Sharepoint farm. To set up SSO, you will need to log into the server (and also into central administration) not with your admin account, but with the service account under which sharepoint is running.

Expect to see more sharepoint related tips as i’m having a lot of fun with it at the moment :)

Cheers! ;)

I hate Acer and I want them to die, that should have been the right title of Nirvana’s hit. My unfaithful, twisted Acer Aspire 3104 WLMi, already famous for it’s overheating issues and semi-USB failures (one port out of three not working, only one port running at full USB 2.0, problems with the internal webcam) decided to die this weekend, just 3 days before ADSL will be installed at my apartment.

All USB ports are dead, the keyboard and touchpad as well, despite all my attempts to resurrect this carcass.
Plugging an external keyboard / mouse also proved to be useless.

I’m now stuck in Acer Hell waiting for a reply from their tech support, and also for warranty info from my reseller (I bought it in August 2007, speak about reliability!)

On a Windows x64 Enterprise Edition machine you may happen to have problems with the Active Directory users & computers MMC snap-in. Try the following to fix the issue :

%windir%\syswow64\mmc.exe %systemroot%\system32\dsa.msc -32

this will launch the 32bit version of the snap-in, without errors (hopefully).

If you’re trying to run newsid.exe on windows vista you will most probably get an error saying that newsid.exe can’t find the computer SID. The problem can be fixed easily :

right-click on newsid.exe and select “run as administrator;-)

If you can’t run it as an admin, launch a cmd.exe and use the runas command to get privileged access :
runas /user:domain\username newsid.exe

This issue occurs on Windows 2003 systems because the update file is too large. To fix this issue, install the microsoft hotfix KB925336 (http://support.microsoft.com/kb/925336)

You can expect to encounter this issue when applying Visual Studio 2005 service pack.