Two quick MySQL tips

Posted by on Oct 4, 2010 in CRM 4.0 |

MySQL: Running a SQL script from the command line:

MySQL: Stopping a long query:

Get the id from the first column then run:

Read More

WSS 3.0: Deleted Config LDF file – no backups, now what?

Posted by on Jun 26, 2009 in Deployment, Sharepoint |

Well guys, i just had the pleasure of deleting the LDF database file for my WSS 3.0 dev site.

Why? The server had literally 0.99MB of hard disk space and out of desperation, i deleted the 7GB log file by stopping the sql service and deleting the LDF file – i know, i wasn’t thinking straight…

Anyway, SQL went into a heap.. I couldn’t detach the database so i could re-attach it and re-create the logs..

The error was: It couldn’t find the log file so it couldn’t detach <- i mean how stupid is that…

Anyway, after fanning around, i uninstalled WSS3.0 and restarted the server.

Logged into SQL management studio, started a new Query and ran the following;

USE [master]
(FILENAME = N'D:\Path\To\Sharepoint\ConfigDB.mdf')

 Now, the other database has detached itself and the new database SharePointTest is up and working with a LDF file.

My main concern now was will WSS 3.0 install and connect to an existing database? is it smart enough?

I managed to install WSS as usuall (stand alone server), then i went to Central Administration and it said none had been configured so hit next and to my amazement it configured it and launched sharepoint and boom i was back to my old sharepoint site.

Fantastic huh!

Read More

Sharepoint – EventID: 17137

Posted by on May 16, 2009 in Sharepoint |

You recieve the event (17137) in the eventlog when you migrate the databases to a different disk or partition (in this case i moved it to a different partition).

The description for Event ID ( 17137 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: WSS_Content.

 The problem here is that when we re-attached the database to the SQL server the ‘AutoClose’ option (this option when ON closes the database cleanly when the last user logs off) is set to true.


  1. Start SQL management studio and connect to the MSSQL#SSEE instance (this is the default sql instance installed by WSS for windows server 2003) – Server name should be: np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query

  3. Select the database from which the event in the event viewer is complaining about and go to properties > options and set the ‘AutoClose’ option to ‘false’

Read More
%d bloggers like this: