Domain Controller Reboot problem

Yesterday we had a very strange problem.

Last week our dns and DC's were upgraded to Win 2008

Yesterday, After the DC reboot, Sharepoint crashed. trying to understand what happened, I saw that SQL server was unable to accept new connections and was continuously throwing this errors:


Event Type: Error
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 17806
Date: 6/23/2010
Time: 10:05:26 AM
User: N/A
Computer: SRV29
Description:
SSPI handshake failed with error code 0x80090304 while establishing a connection with integrated security; the connection has been closed. [CLIENT: 10.3.0.49]


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


---

Event Type: Failure Audit
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 18452
Date: 6/23/2010
Time: 10:05:26 AM
User: N/A
Computer: SRV29
Description:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 10.3.0.49]

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

I was panicked, that was really trouble! The first thing I did was to restart the SQL Server service, and an IIS reset on the WFE of Sharepoint side..


But it didnt work. So I reboot both the WFE and SQL Server of Sharepoint farm and everything started to work again.


After a little investigation, we saw that our technician had entered only the first DNS , forgot the second. After he entered both DNS we reboot the DC machines again and everything went fine. -Actually, there was a 5 seconds of interruption, which could be seen on SQL server's event log but it  did not cause any service interruption and SharePoint & other applications was not affected.-


So If you encounter this errors after DC reboots, check if the dns name resolving is working..

Upgrade to MOSS 2010

To upgrade my existing Moss 2007 installation, which is completely sitting on a 32 Bit Windows 2003 system, first step was to install a clean Moss 2007 on Windows 2008 Server (64-bit)

After installing  the brand-new Sharepoint 2007, I simply created a new Web Application and attached my content database to it. (You can find a detailed how-to here.)

After ensuring everything was working on the new installation, I started the SharePoint 2010 installation. Not very suprisingly, it required tones of stuff to be installed on the machine. which are:

- 2007 Office Server SP2 (Its a shame we're still on SP1)
- Windows Identity Foundation (which requires Windows Update service to be started to be installed!)
- Microsoft Sync Framework Runtime v.1.0
- SQL Server Native Client -very simple to install <3
- Enable Windows Server Roles- Features (just enabling Web Server and Application roles should do it)
- MS Filter Pack 2.0 (Which is very annoying to install, because on the net you find Filter Pack 1.0 only. the trick is that the real name of this package is Microsoft Office 2010 Filterpack. you should seek this package for installing Filter Pack 2.0)
- Hotfix KB976394
- PowerShell v.2.0
- Ms Chart controls for .net 3.5

After completing this steps you are ready to run the setup.exe of SharePoint 2010.. But beware the language packs! For example we had Turkish Language Pack installed on our old 2007 system.. But the release of Turkish Lang. pack for SharePoint 2010 will approximately be in July..So the upgrade will fail if you have Turkish Language Package installed on your 2007 SharePoint..

Deleting IIS logs

IIS logs are residing under c:\windows\system32\logfiles  by default. (on windows 2003 server)
It should be named like  W3SVCxxx

I have an internal website, and its used by SharePoint, so I dont really need to store IIS logs older than 1 week. There is no way to automatically delete this logs. They can grow up to 50 gb in 1 year!

Its safe to delete them, just keep the recent.

SQL server Restore Error

I got this error when trying to restorea database from the SQL Server Management Studio..

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------
ADDITIONAL INFORMATION:

The media family on device '\\tup03srv32\Backup\SQL\tup03srv06\WSS_Content_backup_201006100000.bak' is incorrectly formed. SQL Server cannot process this media family.
RESTORE HEADERONLY is terminating abnormally. (Microsoft SQL Server, Error: 3241)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=3241&LinkId=20476

Then I run the restore command via Query Editor and it worked!

RESTORE DATABASE [WSS_Content] FROM DISK = N'\\Tup03srv32\backup\SQL\tup03srv06\WSS_Content_backup_201006100000.bak' WITH FILE = 1, MOVE N'WSS_Content' TO 'c:\evrak\WSS_Content.mdf', MOVE N'WSS_Content_log' TO N'C:\evrak\WSS_Content.ldf', NOUNLOAD, REPLACE, STATS = 10 GO

Add new content database error

I normally prefer to do my operations from central administration. But this morning when I tried to add a new content database to a web application i got the error:


Attaching this database requires upgrade, which could time out the browser session.  You must use the STSADM command 'addcontentdb' to attach this database.

So I connected to the SERVER02 -which is the wfe hosting Central Admin-

And run this command:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm -o addcontentdb -url http://SERVER02:81 -databasename WSS_Content_01 -databaseserver SERVER01

It worked!