Tuesday, August 2, 2011

Win32 Time debugging

If you have clients routinely getting the W32time warnings/errors in their event logs run the following commands to enable logging:

reg add HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config /v FileLogSize /t REG_Dword /d 1000000
reg add HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config /v FileLogName /d C:\windows\Temp\w32time.log
reg add HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config /v FileLogEntries /d 0-116
net stop w32time && net start w32time

Friday, July 29, 2011

winrm qc fails with

WSManFault
Message = The system cannot find the file specified.

Error number: -2147024894 0x80070002
The system cannot find the file specified.


This is how my issue was resolved.

sc config WinRM start= delayed-auto
net start WinRM
winrm create winrm/config/listener?Address=*+Transport=HTTP
netsh firewall add portopening TCP 80 "Windows Remote Management"

Tuesday, July 12, 2011

Download Details - Microsoft Download Center - Active Directory Management Gateway Service

Download Details - Microsoft Download Center - Active Directory Management Gateway Service

Active Directory Management Gateway Service (Active Directory Web Service for Windows Server 2003 and Windows Server 2008)

The Active Directory® Management Gateway Service enables administrators to manage Active Directory Domain Services and Active Directory Lightweight Directory Services (AD LDS) or Active Directory Application Mode (ADAM) using Active Directory module for Windows PowerShell and the Active Directory Administrative Center.

Friday, June 24, 2011

SharePoint databases report ‘Database is in compatibility range and upgrade is recommended’ after upgrade - Paul Grimleys Blog

SharePoint databases report ‘Database is in compatibility range and upgrade is recommended’ after upgrade - Paul Grimleys Blog


Repost from Paul's site:


Following on from previous blog and day 2 of upgrade found some of the databases were reporting the following error:
Database is in compatibility range and upgrade is recommended
This was appearing on non content databases (as in SharePoint system databases).
This seemed strange as I mentioned in my previous blog that the upgrade had been successful so was a little perplexed to find this issue.
After a little research there didn't seem to be anything that looked to answer my problem.
Although this blog was referring to Windows 7 it was interesting in helping my trail of thought and also made me aware that you can only upgrade content databases and not just standard SharePoint system databases using PowerShellhttp://blogs.technet.com/b/blairb/archive/2010/07/16/patching-sharepoint-2010-on-windows-7.aspx.
Another article relating to this was found here where no solution had actually been found (at the time of blogging)http://social.technet.microsoft.com/Forums/en-IE/sharepoint2010setup/thread/7d3ee7cf-56f8-46fe-b2c9-b8662e88825a
So concluding that I could only upgrade content databases the above did not help in resolving the issue.
The two databases in question were:
Database – Type
WSS_Search - SPSearchDatabase
WSS_UsageApplication - SPUsageDatabase
I finally managed to resolve the problem by running a b2b upgrade command:
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
Credit to this blog (http://blog.techgalaxy.net/archives/2585) for pointing out the b2b command as I was having issues running this prior to finding this.