Fun with SQL Express II

03/29/08

Fun with SQL Express II

I think I’ve resolved the issue with SQL Express (see Fun with SQL Express).

I changed

Data Source=.\SQLEXPRESS;AttachDbFilename={0};Integrated Security=True;User Instance=True

to

Data Source=.\SQLEXPRESS;AttachDbFilename={0};Integrated Security=True;User Instance=False;Connect Timeout=60

and removed the NAnt build script calls to restart the SQL Express service, kill the RANU processes, and clean up the RANU files. I should know better than to establish procedures like that; they’re akin to a code smell.

For more details on RANU and other oddities of SQL Express, see:
http://blogs.msdn.com/sqlexpress/archive/2008/02/22/sql-express-behaviors-idle-time-resources-usage-auto-close-and-user-instances.aspx
http://technet.microsoft.com/en-us/library/ms143684.aspx


Or maybe not. Now I’m getting:

SqlException : A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)

This person had similar problems:
http://blogs.mantiso.com/blog/kevin/2005/11/15/SQLExpress-Problems.html

Deleting the SQLEXPRESS per-user (RANU) directory isn’t the answer, though.

Update - March 30, 2008

In addition to adding the CruiseControl.NET service login to the Administrators group (which I’d already done), I also had to give the SQL Server (SQLEXPRESS) service an administrative login. I think that was because the check-out directory was a mounted volume, but I’m not sure.

Update - April 25, 2008

Most of the problems have disappeared. I still have to reboot the build server once or twice a week due to SQL Express connection failures and hanging file locks, though. :-P


Your Host: webmaster@truewill.net
Copyright © 2000-2013 by William Sorensen. All rights reserved.