Hi,
We have a Windows 2000 server (domain server) as suport for our database,
with two instances of SQL Server 2000 (one sensitive and one insensitive) and
decided to move the sensitive instance on a Windows 2003 server.
When I try to make the registration of the instance from Windows 2003
Server on Enterprise Manager from Windows 2000 Server it fail with time out
message.
I need to make a link server on instance from Windows 2000 but it seems
Windows 2003 has a security setting that stop me from doing this.
Any idea would be appreciated."You may not be able to connect to an instance of SQL Server 2000 Service
Pack 2 or earlier that is installed on a Windows Server 2003 computer
through the TCP/IP port"
http://support.microsoft.com/default.aspx?scid=kb;en-us;884012
Cristian Lefter, SQL Server MVP
"Traian" <Traian@.discussions.microsoft.com> wrote in message
news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> Hi,
> We have a Windows 2000 server (domain server) as suport for our database,
> with two instances of SQL Server 2000 (one sensitive and one insensitive)
> and
> decided to move the sensitive instance on a Windows 2003 server.
> When I try to make the registration of the instance from Windows 2003
> Server on Enterprise Manager from Windows 2000 Server it fail with time
> out
> message.
> I need to make a link server on instance from Windows 2000 but it seems
> Windows 2003 has a security setting that stop me from doing this.
> Any idea would be appreciated.
>|||Thank you, but on both systems SQL Server instances are with Service Pack 3
installed. Windows 2000 server is with Service Pack 4 installed.
"Cristian Lefter" wrote:
> "You may not be able to connect to an instance of SQL Server 2000 Service
> Pack 2 or earlier that is installed on a Windows Server 2003 computer
> through the TCP/IP port"
> http://support.microsoft.com/default.aspx?scid=kb;en-us;884012
> Cristian Lefter, SQL Server MVP
> "Traian" <Traian@.discussions.microsoft.com> wrote in message
> news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> > Hi,
> > We have a Windows 2000 server (domain server) as suport for our database,
> > with two instances of SQL Server 2000 (one sensitive and one insensitive)
> > and
> > decided to move the sensitive instance on a Windows 2003 server.
> > When I try to make the registration of the instance from Windows 2003
> > Server on Enterprise Manager from Windows 2000 Server it fail with time
> > out
> > message.
> > I need to make a link server on instance from Windows 2000 but it seems
> > Windows 2003 has a security setting that stop me from doing this.
> >
> > Any idea would be appreciated.
> >
>
>|||By default when you install win2k3 all network connections are firewalled so
I think you must enable tcp port 1433 in your firewall.
Right click on LAN connection, chose properties then chose advanced tab, on
services tab click add button and Write name and description of service,
chose Tcp, and put 1433 in both textboxes.
Regards,
Daniel
"Traian" <Traian@.discussions.microsoft.com> wrote in message
news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> Hi,
> We have a Windows 2000 server (domain server) as suport for our database,
> with two instances of SQL Server 2000 (one sensitive and one insensitive)
and
> decided to move the sensitive instance on a Windows 2003 server.
> When I try to make the registration of the instance from Windows 2003
> Server on Enterprise Manager from Windows 2000 Server it fail with time
out
> message.
> I need to make a link server on instance from Windows 2000 but it seems
> Windows 2003 has a security setting that stop me from doing this.
> Any idea would be appreciated.
>|||Thank you, I'll try your tip. I didn't do this because the firewall option
was unchecked. But it could be active some other way.
"Daniel Joskovski" wrote:
> By default when you install win2k3 all network connections are firewalled so
> I think you must enable tcp port 1433 in your firewall.
> Right click on LAN connection, chose properties then chose advanced tab, on
> services tab click add button and Write name and description of service,
> chose Tcp, and put 1433 in both textboxes.
> Regards,
> Daniel
> "Traian" <Traian@.discussions.microsoft.com> wrote in message
> news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> > Hi,
> > We have a Windows 2000 server (domain server) as suport for our database,
> > with two instances of SQL Server 2000 (one sensitive and one insensitive)
> and
> > decided to move the sensitive instance on a Windows 2003 server.
> > When I try to make the registration of the instance from Windows 2003
> > Server on Enterprise Manager from Windows 2000 Server it fail with time
> out
> > message.
> > I need to make a link server on instance from Windows 2000 but it seems
> > Windows 2003 has a security setting that stop me from doing this.
> >
> > Any idea would be appreciated.
> >
>
>
Showing posts with label instance. Show all posts
Showing posts with label instance. Show all posts
Thursday, March 29, 2012
Failed to register instance from Windows 2003 server
Hi,
We have a Windows 2000 server (domain server) as suport for our database,
with two instances of SQL Server 2000 (one sensitive and one insensitive) an
d
decided to move the sensitive instance on a Windows 2003 server.
When I try to make the registration of the instance from Windows 2003
Server on Enterprise Manager from Windows 2000 Server it fail with time out
message.
I need to make a link server on instance from Windows 2000 but it seems
Windows 2003 has a security setting that stop me from doing this.
Any idea would be appreciated."You may not be able to connect to an instance of SQL Server 2000 Service
Pack 2 or earlier that is installed on a Windows Server 2003 computer
through the TCP/IP port"
http://support.microsoft.com/defaul...kb;en-us;884012
Cristian Lefter, SQL Server MVP
"Traian" <Traian@.discussions.microsoft.com> wrote in message
news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> Hi,
> We have a Windows 2000 server (domain server) as suport for our database,
> with two instances of SQL Server 2000 (one sensitive and one insensitive)
> and
> decided to move the sensitive instance on a Windows 2003 server.
> When I try to make the registration of the instance from Windows 2003
> Server on Enterprise Manager from Windows 2000 Server it fail with time
> out
> message.
> I need to make a link server on instance from Windows 2000 but it seems
> Windows 2003 has a security setting that stop me from doing this.
> Any idea would be appreciated.
>|||Thank you, but on both systems SQL Server instances are with Service Pack 3
installed. Windows 2000 server is with Service Pack 4 installed.
"Cristian Lefter" wrote:
> "You may not be able to connect to an instance of SQL Server 2000 Service
> Pack 2 or earlier that is installed on a Windows Server 2003 computer
> through the TCP/IP port"
> http://support.microsoft.com/defaul...kb;en-us;884012
> Cristian Lefter, SQL Server MVP
> "Traian" <Traian@.discussions.microsoft.com> wrote in message
> news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
>
>|||By default when you install win2k3 all network connections are firewalled so
I think you must enable tcp port 1433 in your firewall.
Right click on LAN connection, chose properties then chose advanced tab, on
services tab click add button and Write name and description of service,
chose Tcp, and put 1433 in both textboxes.
Regards,
Daniel
"Traian" <Traian@.discussions.microsoft.com> wrote in message
news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> Hi,
> We have a Windows 2000 server (domain server) as suport for our database,
> with two instances of SQL Server 2000 (one sensitive and one insensitive)
and
> decided to move the sensitive instance on a Windows 2003 server.
> When I try to make the registration of the instance from Windows 2003
> Server on Enterprise Manager from Windows 2000 Server it fail with time
out
> message.
> I need to make a link server on instance from Windows 2000 but it seems
> Windows 2003 has a security setting that stop me from doing this.
> Any idea would be appreciated.
>|||Thank you, I'll try your tip. I didn't do this because the firewall option
was unchecked. But it could be active some other way.
"Daniel Joskovski" wrote:
> By default when you install win2k3 all network connections are firewalled
so
> I think you must enable tcp port 1433 in your firewall.
> Right click on LAN connection, chose properties then chose advanced tab, o
n
> services tab click add button and Write name and description of service,
> chose Tcp, and put 1433 in both textboxes.
> Regards,
> Daniel
> "Traian" <Traian@.discussions.microsoft.com> wrote in message
> news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> and
> out
>
>sql
We have a Windows 2000 server (domain server) as suport for our database,
with two instances of SQL Server 2000 (one sensitive and one insensitive) an
d
decided to move the sensitive instance on a Windows 2003 server.
When I try to make the registration of the instance from Windows 2003
Server on Enterprise Manager from Windows 2000 Server it fail with time out
message.
I need to make a link server on instance from Windows 2000 but it seems
Windows 2003 has a security setting that stop me from doing this.
Any idea would be appreciated."You may not be able to connect to an instance of SQL Server 2000 Service
Pack 2 or earlier that is installed on a Windows Server 2003 computer
through the TCP/IP port"
http://support.microsoft.com/defaul...kb;en-us;884012
Cristian Lefter, SQL Server MVP
"Traian" <Traian@.discussions.microsoft.com> wrote in message
news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> Hi,
> We have a Windows 2000 server (domain server) as suport for our database,
> with two instances of SQL Server 2000 (one sensitive and one insensitive)
> and
> decided to move the sensitive instance on a Windows 2003 server.
> When I try to make the registration of the instance from Windows 2003
> Server on Enterprise Manager from Windows 2000 Server it fail with time
> out
> message.
> I need to make a link server on instance from Windows 2000 but it seems
> Windows 2003 has a security setting that stop me from doing this.
> Any idea would be appreciated.
>|||Thank you, but on both systems SQL Server instances are with Service Pack 3
installed. Windows 2000 server is with Service Pack 4 installed.
"Cristian Lefter" wrote:
> "You may not be able to connect to an instance of SQL Server 2000 Service
> Pack 2 or earlier that is installed on a Windows Server 2003 computer
> through the TCP/IP port"
> http://support.microsoft.com/defaul...kb;en-us;884012
> Cristian Lefter, SQL Server MVP
> "Traian" <Traian@.discussions.microsoft.com> wrote in message
> news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
>
>|||By default when you install win2k3 all network connections are firewalled so
I think you must enable tcp port 1433 in your firewall.
Right click on LAN connection, chose properties then chose advanced tab, on
services tab click add button and Write name and description of service,
chose Tcp, and put 1433 in both textboxes.
Regards,
Daniel
"Traian" <Traian@.discussions.microsoft.com> wrote in message
news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> Hi,
> We have a Windows 2000 server (domain server) as suport for our database,
> with two instances of SQL Server 2000 (one sensitive and one insensitive)
and
> decided to move the sensitive instance on a Windows 2003 server.
> When I try to make the registration of the instance from Windows 2003
> Server on Enterprise Manager from Windows 2000 Server it fail with time
out
> message.
> I need to make a link server on instance from Windows 2000 but it seems
> Windows 2003 has a security setting that stop me from doing this.
> Any idea would be appreciated.
>|||Thank you, I'll try your tip. I didn't do this because the firewall option
was unchecked. But it could be active some other way.
"Daniel Joskovski" wrote:
> By default when you install win2k3 all network connections are firewalled
so
> I think you must enable tcp port 1433 in your firewall.
> Right click on LAN connection, chose properties then chose advanced tab, o
n
> services tab click add button and Write name and description of service,
> chose Tcp, and put 1433 in both textboxes.
> Regards,
> Daniel
> "Traian" <Traian@.discussions.microsoft.com> wrote in message
> news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> and
> out
>
>sql
Failed to register instance from Windows 2003 server
Hi,
We have a Windows 2000 server (domain server) as suport for our database,
with two instances of SQL Server 2000 (one sensitive and one insensitive) and
decided to move the sensitive instance on a Windows 2003 server.
When I try to make the registration of the instance from Windows 2003
Server on Enterprise Manager from Windows 2000 Server it fail with time out
message.
I need to make a link server on instance from Windows 2000 but it seems
Windows 2003 has a security setting that stop me from doing this.
Any idea would be appreciated.
"You may not be able to connect to an instance of SQL Server 2000 Service
Pack 2 or earlier that is installed on a Windows Server 2003 computer
through the TCP/IP port"
http://support.microsoft.com/default...b;en-us;884012
Cristian Lefter, SQL Server MVP
"Traian" <Traian@.discussions.microsoft.com> wrote in message
news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> Hi,
> We have a Windows 2000 server (domain server) as suport for our database,
> with two instances of SQL Server 2000 (one sensitive and one insensitive)
> and
> decided to move the sensitive instance on a Windows 2003 server.
> When I try to make the registration of the instance from Windows 2003
> Server on Enterprise Manager from Windows 2000 Server it fail with time
> out
> message.
> I need to make a link server on instance from Windows 2000 but it seems
> Windows 2003 has a security setting that stop me from doing this.
> Any idea would be appreciated.
>
|||Thank you, but on both systems SQL Server instances are with Service Pack 3
installed. Windows 2000 server is with Service Pack 4 installed.
"Cristian Lefter" wrote:
> "You may not be able to connect to an instance of SQL Server 2000 Service
> Pack 2 or earlier that is installed on a Windows Server 2003 computer
> through the TCP/IP port"
> http://support.microsoft.com/default...b;en-us;884012
> Cristian Lefter, SQL Server MVP
> "Traian" <Traian@.discussions.microsoft.com> wrote in message
> news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
>
>
|||By default when you install win2k3 all network connections are firewalled so
I think you must enable tcp port 1433 in your firewall.
Right click on LAN connection, chose properties then chose advanced tab, on
services tab click add button and Write name and description of service,
chose Tcp, and put 1433 in both textboxes.
Regards,
Daniel
"Traian" <Traian@.discussions.microsoft.com> wrote in message
news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> Hi,
> We have a Windows 2000 server (domain server) as suport for our database,
> with two instances of SQL Server 2000 (one sensitive and one insensitive)
and
> decided to move the sensitive instance on a Windows 2003 server.
> When I try to make the registration of the instance from Windows 2003
> Server on Enterprise Manager from Windows 2000 Server it fail with time
out
> message.
> I need to make a link server on instance from Windows 2000 but it seems
> Windows 2003 has a security setting that stop me from doing this.
> Any idea would be appreciated.
>
|||Thank you, I'll try your tip. I didn't do this because the firewall option
was unchecked. But it could be active some other way.
"Daniel Joskovski" wrote:
> By default when you install win2k3 all network connections are firewalled so
> I think you must enable tcp port 1433 in your firewall.
> Right click on LAN connection, chose properties then chose advanced tab, on
> services tab click add button and Write name and description of service,
> chose Tcp, and put 1433 in both textboxes.
> Regards,
> Daniel
> "Traian" <Traian@.discussions.microsoft.com> wrote in message
> news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> and
> out
>
>
We have a Windows 2000 server (domain server) as suport for our database,
with two instances of SQL Server 2000 (one sensitive and one insensitive) and
decided to move the sensitive instance on a Windows 2003 server.
When I try to make the registration of the instance from Windows 2003
Server on Enterprise Manager from Windows 2000 Server it fail with time out
message.
I need to make a link server on instance from Windows 2000 but it seems
Windows 2003 has a security setting that stop me from doing this.
Any idea would be appreciated.
"You may not be able to connect to an instance of SQL Server 2000 Service
Pack 2 or earlier that is installed on a Windows Server 2003 computer
through the TCP/IP port"
http://support.microsoft.com/default...b;en-us;884012
Cristian Lefter, SQL Server MVP
"Traian" <Traian@.discussions.microsoft.com> wrote in message
news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> Hi,
> We have a Windows 2000 server (domain server) as suport for our database,
> with two instances of SQL Server 2000 (one sensitive and one insensitive)
> and
> decided to move the sensitive instance on a Windows 2003 server.
> When I try to make the registration of the instance from Windows 2003
> Server on Enterprise Manager from Windows 2000 Server it fail with time
> out
> message.
> I need to make a link server on instance from Windows 2000 but it seems
> Windows 2003 has a security setting that stop me from doing this.
> Any idea would be appreciated.
>
|||Thank you, but on both systems SQL Server instances are with Service Pack 3
installed. Windows 2000 server is with Service Pack 4 installed.
"Cristian Lefter" wrote:
> "You may not be able to connect to an instance of SQL Server 2000 Service
> Pack 2 or earlier that is installed on a Windows Server 2003 computer
> through the TCP/IP port"
> http://support.microsoft.com/default...b;en-us;884012
> Cristian Lefter, SQL Server MVP
> "Traian" <Traian@.discussions.microsoft.com> wrote in message
> news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
>
>
|||By default when you install win2k3 all network connections are firewalled so
I think you must enable tcp port 1433 in your firewall.
Right click on LAN connection, chose properties then chose advanced tab, on
services tab click add button and Write name and description of service,
chose Tcp, and put 1433 in both textboxes.
Regards,
Daniel
"Traian" <Traian@.discussions.microsoft.com> wrote in message
news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> Hi,
> We have a Windows 2000 server (domain server) as suport for our database,
> with two instances of SQL Server 2000 (one sensitive and one insensitive)
and
> decided to move the sensitive instance on a Windows 2003 server.
> When I try to make the registration of the instance from Windows 2003
> Server on Enterprise Manager from Windows 2000 Server it fail with time
out
> message.
> I need to make a link server on instance from Windows 2000 but it seems
> Windows 2003 has a security setting that stop me from doing this.
> Any idea would be appreciated.
>
|||Thank you, I'll try your tip. I didn't do this because the firewall option
was unchecked. But it could be active some other way.
"Daniel Joskovski" wrote:
> By default when you install win2k3 all network connections are firewalled so
> I think you must enable tcp port 1433 in your firewall.
> Right click on LAN connection, chose properties then chose advanced tab, on
> services tab click add button and Write name and description of service,
> chose Tcp, and put 1433 in both textboxes.
> Regards,
> Daniel
> "Traian" <Traian@.discussions.microsoft.com> wrote in message
> news:EB5D2A03-5282-472C-A7C2-4A16FE38F964@.microsoft.com...
> and
> out
>
>
Tuesday, March 27, 2012
Failed to Generate User Instance of SQL Server
I have seen many posts on the subject, but I haven't seen a clear answer to the following:
1. Start a new Web Project (VS 2005 Pro). The solution is built.
2. Select App_Data, right click and select Add New Item.
3. In the dialog box, select SQL Database and give it a name.
4. When you select Add, the message "Failed to Generate User Instance of SQL Server ... " appears.
5. I am running SQL Express. What is the correct fix to get this simple process to work?
thanks,
Flavelle
I have been puttering, trying get this supposedly simple thing working for several hours.
1. The problem appears to be directly related to User Instance with SQL Server Express. There may also be issues with the setup of SQL Server Express to work with ASP .Net.
2. I have run the asp_regsql utility against my installation of SQL Server Express. I have reinstalled SQL Server Express, making sure that enable User Instances is set.
3. Is there ANYTHING else that I need to do to SQL Server Express to make it work for the scenario above. I do not have any other versions of SQL Server installed. I do have SSME installed and working.
I need an answer so that I can start to work on a project!
Sorry, but I am hugely frustrated, I am seeing a lot of posts related to this problem, but I am not seeing any answers!
Many thanks,
Flavelle
|||Solved it - but this is not a solution for everyone and does raise some concerns about the viability.
At the time that I installed Visual Studio, I did not have an instance of SQL Express - so I installed the one that was packaged with Visual Studio. I think that this was the November CTP, but I'm not sure. When the release version came out, I uninstalled the SQL Express, then installed the released version. I am now suspecting that there was something in that process that did not go cleanly.
In total frustration, I backed up my data, reformatted the hard drive and did a clean install of everything (like I said, not a solution for everyone). Before I installed Visual Studio, I installed the release version of SQL Express. When I installed Visual Studio, it correctly realized that there was a version of SQL Express, and that it was later. It did not overwrite the installation.
When all of that was done, I repeated the tasks that started this posting, and this time, I did not get the exception.
Weird, and someone may want to do some further investigating, but I'm going to lurch on to the next problem, whenever that rears its ugly head. I think my solution is dependant on the order of the install, with the release version of SQL Express going in prior to Visual Studio. Hope this helps.
Flavelle
Failed to generate user instance and Cached Domain Login....
I am having trouble with the "Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed. " message however I believe my circumstances are different that what I have found in any posts about this subject.
I use a laptop computer for development on my domain at work (I am in admin group on that domain). I have worked for several hours today on a project and logged off my network and then hooked my computer up at home. I log onto the machine again when I get home and log on normally, with a cached domain logon and I am unable access the database. This happened to me yesterday as well and after several hours of reading posts and troubleshooting I decided to reinstall SQL and that fixed the problem.
I don't want to have to reinstall each time I log on my computer at different locations. Most of the posts I read have to do with working on different computers or posting an application and accessing it remotely. I am working on the same machine all the time withouht making any changes to my configuration and am at a loss about how further to troubleshoot this problem.
Any suggestions would be greatly appreciated!
Just wanted to post and update on how I resolved this problem.
It would appear that resinstalling would fix the problem for short time but it would surface again after a few sessions.
I ended up un-installing SQL and then logging on the computers local admin account and installed SQL that way. I am not sure why being logged with an account that was in the admin group for my computer was any different, but at least that took care of the problem.
I will post an update again if this problem starts back up again, otherwise give that a shot if you are having the same problem I was.
|||Well after a few days of successful use, I started having trouble again. I downloaded the SSEUTil.exe from http://www.microsoft.com/downloads/details.aspx?FamilyID=FA87E828-173F-472E-A85C-27ED01CF6B02&displaylang=en.
When I ran this utility I got the same error message "Failed to generate user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed".
I started poking around with the SQL Configuration Manager and went to the properties for the instance of SQL that was running and changed the "log on as option" from "Network Service" to "Local System" and everything seemed to work again.
I hope this thread is helpfule to some besides me :)
|||Setting it to log on as "Local System" worked for me as well, once I told it to not open the database using a "User Instance".
Thanks, this has been bothering me for days.
|||How do you tell your system not to open the database using a "User Instance"?|||To tell it not to generate user instance, go to the advanst property on the login window, a new window should appear. Move down the window untill you find the "User Instance" property, set that to false. I do not know how to do it on websites I would appresiate any help.Failed to generate user instance and Cached Domain Login....
I am having trouble with the "Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed. " message however I believe my circumstances are different that what I have found in any posts about this subject.
I use a laptop computer for development on my domain at work (I am in admin group on that domain). I have worked for several hours today on a project and logged off my network and then hooked my computer up at home. I log onto the machine again when I get home and log on normally, with a cached domain logon and I am unable access the database. This happened to me yesterday as well and after several hours of reading posts and troubleshooting I decided to reinstall SQL and that fixed the problem.
I don't want to have to reinstall each time I log on my computer at different locations. Most of the posts I read have to do with working on different computers or posting an application and accessing it remotely. I am working on the same machine all the time withouht making any changes to my configuration and am at a loss about how further to troubleshoot this problem.
Any suggestions would be greatly appreciated!
Just wanted to post and update on how I resolved this problem.
It would appear that resinstalling would fix the problem for short time but it would surface again after a few sessions.
I ended up un-installing SQL and then logging on the computers local admin account and installed SQL that way. I am not sure why being logged with an account that was in the admin group for my computer was any different, but at least that took care of the problem.
I will post an update again if this problem starts back up again, otherwise give that a shot if you are having the same problem I was.
|||Well after a few days of successful use, I started having trouble again. I downloaded the SSEUTil.exe from http://www.microsoft.com/downloads/details.aspx?FamilyID=FA87E828-173F-472E-A85C-27ED01CF6B02&displaylang=en.
When I ran this utility I got the same error message "Failed to generate user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed".
I started poking around with the SQL Configuration Manager and went to the properties for the instance of SQL that was running and changed the "log on as option" from "Network Service" to "Local System" and everything seemed to work again.
I hope this thread is helpfule to some besides me :)
|||Setting it to log on as "Local System" worked for me as well, once I told it to not open the database using a "User Instance".
Thanks, this has been bothering me for days.
|||How do you tell your system not to open the database using a "User Instance"?|||To tell it not to generate user instance, go to the advanst property on the login window, a new window should appear. Move down the window untill you find the "User Instance" property, set that to false. I do not know how to do it on websites I would appresiate any help.Failed to generate user instance and Cached Domain Login....
I am having trouble with the "Failed to generate a
user instance of SQL Server due to a failure in starting the process for the
user instance. The connection will be closed. " message however I
believe my circumstances are different that what I have found in any posts
about this subject.
I use a laptop computer for development on my domain at work (I am in admin
group on that domain). I have worked for several hours today on a project and
logged off my network and then hooked my computer up at home. I log onto the
machine again when I get home and log on normally, with a cached domain logon
and I am unable access the database. This happened to me yesterday as
well and after several hours of reading posts and troubleshooting I decided to
reinstall SQL and that fixed the problem.
I don't want to have to reinstall each time I log on my computer at different
locations. Most of the posts I read have to do with working on different
computers or posting an application and accessing it remotely. I am working on
the same machine all the time withouht making any changes to my configuration and am at a loss about how further to
troubleshoot this problem.
Any suggestions would be greatly appreciated!
Just wanted to post and update on how I resolved this problem.
It would appear that resinstalling would fix the problem for short time but it would surface again after a few sessions.
I ended up un-installing SQL and then logging on the computers local admin account and installed SQL that way. I am not sure why being logged with an account that was in the admin group for my computer was any different, but at least that took care of the problem.
I will post an update again if this problem starts back up again, otherwise give that a shot if you are having the same problem I was.
|||Well after a few days of successful use, I started having trouble again. I downloaded the SSEUTil.exe from http://www.microsoft.com/downloads/details.aspx?FamilyID=FA87E828-173F-472E-A85C-27ED01CF6B02&displaylang=en.
When I ran this utility I got the same error message "Failed to generate user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed".
I started poking around with the SQL Configuration Manager and went to the properties for the instance of SQL that was running and changed the "log on as option" from "Network Service" to "Local System" and everything seemed to work again.
I hope this thread is helpfule to some besides me :)
|||Setting it to log on as "Local System" worked for me as well, once I told it to not open the database using a "User Instance".
Thanks, this has been bothering me for days.
|||How do you tell your system not to open the database using a "User Instance"?|||To tell it not to generate user instance, go to the advanst property on the login window, a new window should appear. Move down the window untill you find the "User Instance" property, set that to false. I do not know how to do it on websites I would appresiate any help.Failed to generate a user instance SQL Server Express 2005
Hello,
I get the following message after updating to sql server express 2005 advanced.
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
I noticed that in my C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data I have not databases? How do I get them back?
I also had to add back the aspnet to the permissions and the network and network service to the app_data folder.
Can any one help?
Thanks
Tom
Moving this thread over to the SQL Express forum.
-- Robert
|||With User Instances the database files are not created in the old data directories, they are normally installed in the main project output directories for the project. In ASP.Net this is normally the ASP_Data directory. When the application starts it will automaticle attach the database to the database engine and set the permissions.
With your problem have you tried a complete rebuild of the application, Did it work befor you upgraded to Express Advanced. Also you might want to try opening up the file and attaching it to the database engine using the management studio just to make sure it is working fine, you can then detach it and try the application again.
|||Hi Tom,
Did you ever resolve this issue?
You definitely need the databases located in Template Data in order for User Instances to work. If you didn't get this resolved, I would suggest trying to re-run the install. Usually the only reason an installation results in those files going missing is that some SQL process was running at the time of the installation.
If you haven't tried it yet. I'd also recomend moving to SQL SP1 which you can download from http://msdn.microsoft.com/vstudio/express/sql/download/.
Regards,
Mike Wachal
SQL Express team
-
Mark the best posts as Answers!
Failed to generate a user instance of SQL Server??
I use VS2005 & sql2005express to create a website, but it cannot to display data.
When I run it, I got such errors:
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
My web.config file:
<add name="LocalSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|aspnetdb.mdf"/>
When I change the User Instance=True to False, it works, but MSDN says it is not safe.
I searched the past threads, which writes "delete the folder C:\Documents and Settings\yy\Local Settings\Application Data\Microsoft\Sqlserver Data, it will work".
I try, but failed. What should I do??
have u resolved this error, I'm getting the same?Monday, March 26, 2012
Failed to generate a user instance of SQL Server due to a failure in starting the process for th
No wonder Microsoft is giving it away for free. It’s not worth anything. I am very disappointed in this version of SQL server. I decided to start learning VB so I downloaded and installed VB 2005 express edition and SQL 2005 express. I tried to build a personal website using the starter kit. I kept getting the following error message, for which I have seen numerous postings on this forum.
“Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.”
I went out and bought the Standard version of VS 2005 thinking there may be a feature that the free express version is lacking. I uninstalled the express version, cleaned the registry, deleted all the folders it created and installed the Standard edition. Then I tried to create a personal web using the starter kit and it does the same thing again.
I can not create a database file, connect to a database file. I can not create or attach a database on the SQL 2005 express from VS 2005. The SQL server Express seems to be working OK since I can attach to it using Microsoft SQL Server Management Studio Express. There is something about the way VS tries to connect to the database server that is not working. VB does recognize the local computer as a SQL server but can not connect to it.
SQL server is set to accept Shared memory, TCP/IP and named pipes for local clients.
What is causing this?
This is some information on the system I am using:
MS XP (SP2)
Microsoft Visual Studio 2005
Version 8.0.50727.42(RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727
Installed Edition: Standard
Microsoft SQL Server Management Studio Express9.00.1399.00
Microsoft Data Access Components (MDAC)2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer6.0.2900.2180
Microsoft .NET Framework2.0.50727.42
Operating System5.1.2600
I am now to programming but nor computer illiterate. I have been working with MS SQL servers since version 6.5 and have MCSE, Network+, A+ and Security plus certifications. Installing and using VS should not be this problematic. What is wrong with Microsoft?
I got this very frustating message everytime I was trying to create a new SQL Express database from VB Express. All forums seem to point to 2 possible resolutions, NONE of which worked for me:
A) Known bug with Windows XP SP2 when using SQL via RDP (Remote Desktop).
B) Delete C:\Documents and Settings\USERNAME\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS.
The clue for me was all forums relating to solution B seemed to talk about possible authentication problems which gave me a clue. My solution was therefore:
Solution: Modify the SQL Server (SQLExpress) service to use your local or system account and restart the service. This worked for me first time. I'm not sure if this will cause any problems in the future but hey, at least I can now create a database!!
Hope this helps!!
|||As far as the "Failed to generate a user instances..." error, check out the error log for the user instance, it will likely give you more information about what is happening. You will fine the error log at C:\Documents and Settings\<user name>\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS.
User Instances are a new feature in SQL Express that have some special characteristics. You may want to read the white paper that discusses them to get some background. Creating a database from within VS is actually different that creating one in SSMSE because you're working against different instances of SQL Express. VS uses User Instances by default, where SSMSE works against the main instance of Express.
Regards,
Mike Wachal
SQL Express team
-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1
This error is often caused because the parent instance (for whatever reason) can't copy the system databases to the users local isolated storage folders. Sometimes it is because of a previous install of SQL Express has left files in that directory which is why Reen's suggestion sometimes works
Delete C:\Documents and Settings\USERNAME\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS.
the only trick is knowing the USERNAME, if your writing a web app, the user is usually ASPNET which is usually found in
C:\Documents and Settings\COMPUTERNAME\USERNAME\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS
Other times it is a permissions issue which can be solved by giving the SQL service account the necessary permissions.
One thing to remember is that although user instances is the default when working with Visual Studio, it is not mandatory to use them, it is quite possible to attach to databases in the traditional way from SQL Express, to do this you just need to edit the connection string and delete the "user Instance=true". User Instances just make it easier (when it does work) to work with databases as though they were files.
|||This error is simply ridiculous! Not so much because it occurs a lot but that there is insufficient official documentation about this problem. Worst still you will run into this error if you try and copy the official online VS Express tutorial I found. Worse again, when Microsoft ran a seminar at my University this error occurred and they didn’t even know how to deal with it!
This forum thread right here is by far the best documentation of the problem that I have found so far and it’s not very easy to find or thorough.
|||There seem to be so many things that cause this user instance error. Currently I think the following explains why I'm getting it today. Next they will tell us that it only works when there is a full moon!
(Note the mention of SSEUtil not working... I think that's quite interesting)
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=58741&SiteID=1
I think I found the problem, I was not the first one to use the computer the days with the problem. Even SSEUtil gives the same error. When I switched users to the one that signed on first, SSEUtil worked. I tried signing off of the other computer users and restarting the SQL Server. SSEUtil still could not get the server to respond.
It looks like bottom line....If you need to use a sqldatabase with visual basic 2005 express, make sure you signed on the computer first or reboot before you start or return to your database project.
Mike
|||
The post you reference is from before the final release of SQL, so it's hard to say if the information still applies. Why do you think the above explains your situation? What troubleshooting have you done to check this? Have you checked the error logs for both the main instance and the User Instance?
I'd really like to see actual information about this problem as that is the only way to really understand what is happening.
Regards,
Mike Wachal
SQL Express team
Fair enough.
I am 90% sure that when another account has been logged in before mine this error occurs. I will try generating this error when I have time.
When I checked the error log briefly there did not seem to be any relevant information. Additionally when I generated this error the error log did not update. Implying that this error was not logged or maybe I was looking in the wrong place (not both instances)... again I will have to look into this further when I have more time.
I am using VS2005 (not express edition - thanks to my university) and the version of SQL Server that comes with it (Express).
If you browse the web you will find many different "solutions" to this error... I am happy to help where I can
|||When I ran into this problem the first time, I uninstalled the SQLExpress and reinstalled it. I could then access the database via the Visual C# 2005 Express Edition.Later, after I used the SQL management console to open and explore the SQL Express, the problem reoccurred.I uninstalled and reinstalled the SQL Express again, and it works again.
I don’t profess to understand why it works this way, but it did.
|||Apparently you have to be logged in as jking. And you have to have a D: drive.
SQL Express guys, know who that is?
I cannot get the start kits or time tracker kit going. The start kit does not have an aspnet.mdf. The personal.mdf will not attach or allow a login.
I changed the service to login from the local system account, no change.
I opened Personal.mdf in sql management studio and got:
Directory lookup for the file "D:\Documents and Settings\jking\My Documents\Visual Studio 2005\WebSites\WebSite1\App_Data\Personal_log.LDF" failed with the operating system error 21(the device is not ready)... error 5133
Teach me to use jking's code.
|||Login Order Problem ConfirmedOpened VS2005, can refresh database (I am the 1st and only user to log in)… reset computer…
Logged in as user A then switched to user B, opened VS2005, tried to refresh a database…
Timeout Error!
Try again and…
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
Below is the error log. Note that when I generate this error the error log does not get updated so I expect the following to be useless.
Where would I find the ‘main instance’ error log? There is nothing in All Users… not sure where else to look
Anything else?
C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log
2006-04-11 15:30:23.40 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2006-04-11 15:30:23.40 Server (c) 2005 Microsoft Corporation.
2006-04-11 15:30:23.40 Server All rights reserved.
2006-04-11 15:30:23.40 Server Server process ID is 2912.
2006-04-11 15:30:23.40 Server Logging SQL Server messages in file 'C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log'.
2006-04-11 15:30:23.40 Server Registry startup parameters:
2006-04-11 15:30:23.40 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-04-11 15:30:23.40 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-04-11 15:30:23.40 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-04-11 15:30:23.40 Server Command Line Startup Parameters:
2006-04-11 15:30:23.40 Server -d C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\master.mdf
2006-04-11 15:30:23.40 Server -l C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\mastlog.ldf
2006-04-11 15:30:23.40 Server -e C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log
2006-04-11 15:30:23.40 Server -c
2006-04-11 15:30:23.40 Server -S SQLEXPRESS
2006-04-11 15:30:23.40 Server -s AE669D1F-CC06-41
2006-04-11 15:30:23.40 Server -w 60
2006-04-11 15:30:23.42 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2006-04-11 15:30:23.42 Server Detected 2 CPUs. This is an informational message; no user action is required.
2006-04-11 15:30:23.87 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2006-04-11 15:30:23.89 Server Database Mirroring Transport is disabled in the endpoint configuration.
2006-04-11 15:30:23.89 spid4s Starting up database 'master'.
2006-04-11 15:30:23.95 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2006-04-11 15:30:24.00 spid4s SQL Trace ID 1 was started by login "sa".
2006-04-11 15:30:24.03 spid4s Starting up database 'mssqlsystemresource'.
2006-04-11 15:30:24.20 spid7s Starting up database 'model'.
2006-04-11 15:30:24.20 Server Server local connection provider is ready to accept connection on [ \\.\pipe\AE669D1F-CC06-41\tsql\query ].
2006-04-11 15:30:24.20 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2006-04-11 15:30:24.21 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2006-04-11 15:30:24.21 spid4s Server name is 'KEVINS\AE669D1F-CC06-41'. This is an informational message only. No user action is required.
2006-04-11 15:30:24.29 spid4s Starting up database 'msdb'.
2006-04-11 15:30:24.42 spid7s Clearing tempdb database.
2006-04-11 15:30:24.85 spid7s Starting up database 'tempdb'.
2006-04-11 15:30:24.92 spid4s Recovery is complete. This is an informational message only. No user action is required.
2006-04-11 15:30:24.93 spid10s The Service Broker protocol transport is disabled or not configured.
2006-04-11 15:30:24.93 spid10s The Database Mirroring protocol transport is disabled or not configured.
2006-04-11 15:30:24.95 spid10s Service Broker manager has started.
|||
I just wrote this post on Community Starter Kit personal.mdf, commercedb.mdf and aspnetdb.mdf.
ASP.Net 2.0 Community Starter Kit SQL Express Conversion to SQL 2005
Hope it helps
- Caroline
http://bogartcomputing.com
|||
Make user instance as false. It solves the problem...
Data Source=.\SQLEXPRESS;AttachDbFilename=D:\Test\App_Data\test.mdf;Integrated Security=True;User Instance=false
Hope it helps,
Thanks,
Manoj.
|||saggimanoj wrote:
Make user instance as false. It solves the problem...
Data Source=.\SQLEXPRESS;AttachDbFilename=D:\Test\App_Data\test.mdf;Integrated Security=True;User Instance=false
Hope it helps,
Thanks,
Manoj.
Doing that caused other problems for me.
|||
Hi all,
I'd like to say I was able to reproduce this behavior, but I cannot - at least not 100%... My error(s) seems to alternate between "Failed to generate..." and "Timeout expired. The timeout period elapsed prior to the completion of the operation or the server is not responding."
However, this all seems to happen when another user has or establishes a local session on the computer. I am running WinXP Pro SP2 w/most recent patches and have Fast User Switching enabled so that my wife and I can still use the machine when the other is not around.
So here's an example. My wife wakes before me and logs onto the machine and checks the weather. She leaves, eats breakfast and heads out the door. 20 minutes later, her session is "suspended" and Windows returns to the Welcome Screen.
After dinner, I log onto the machine to do some coding, keeping her session suspended so that she doesn't loose any work. I fire up VS2k5 and create a new project. I try and create a new database and, depeneding on the type of project (WinForms or Web Site), I either receive one of the "Timeout" or "Failed to generate..." errors. I log off out of frustration.
Right before my wife goes to bed, she checks the weather again and then logs off and closes her session.
I return, just before bed, I log in and try once more to create my database...And it works.
I have a handful of error log files if and 2 screen shots if this information would assist anyone.
Thanks,
Failed to generate a user instance of SQL Server due to a failure in starting the process for th
No wonder Microsoft is giving it away for free. It’s not worth anything. I am very disappointed in this version of SQL server. I decided to start learning VB so I downloaded and installed VB 2005 express edition and SQL 2005 express. I tried to build a personal website using the starter kit. I kept getting the following error message, for which I have seen numerous postings on this forum.
“Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.”
I went out and bought the Standard version of VS 2005 thinking there may be a feature that the free express version is lacking. I uninstalled the express version, cleaned the registry, deleted all the folders it created and installed the Standard edition. Then I tried to create a personal web using the starter kit and it does the same thing again.
I can not create a database file, connect to a database file. I can not create or attach a database on the SQL 2005 express from VS 2005. The SQL server Express seems to be working OK since I can attach to it using Microsoft SQL Server Management Studio Express. There is something about the way VS tries to connect to the database server that is not working. VB does recognize the local computer as a SQL server but can not connect to it.
SQL server is set to accept Shared memory, TCP/IP and named pipes for local clients.
What is causing this?
This is some information on the system I am using:
MS XP (SP2)
Microsoft Visual Studio 2005
Version 8.0.50727.42(RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727
Installed Edition: Standard
Microsoft SQL Server Management Studio Express9.00.1399.00
Microsoft Data Access Components (MDAC)2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer6.0.2900.2180
Microsoft .NET Framework2.0.50727.42
Operating System5.1.2600
I am now to programming but nor computer illiterate. I have been working with MS SQL servers since version 6.5 and have MCSE, Network+, A+ and Security plus certifications. Installing and using VS should not be this problematic. What is wrong with Microsoft?
I got this very frustating message everytime I was trying to create a new SQL Express database from VB Express. All forums seem to point to 2 possible resolutions, NONE of which worked for me:
A) Known bug with Windows XP SP2 when using SQL via RDP (Remote Desktop).
B) Delete C:\Documents and Settings\USERNAME\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS.
The clue for me was all forums relating to solution B seemed to talk about possible authentication problems which gave me a clue. My solution was therefore:
Solution: Modify the SQL Server (SQLExpress) service to use your local or system account and restart the service. This worked for me first time. I'm not sure if this will cause any problems in the future but hey, at least I can now create a database!!
Hope this helps!!
|||As far as the "Failed to generate a user instances..." error, check out the error log for the user instance, it will likely give you more information about what is happening. You will fine the error log at C:\Documents and Settings\<user name>\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS.
User Instances are a new feature in SQL Express that have some special characteristics. You may want to read the white paper that discusses them to get some background. Creating a database from within VS is actually different that creating one in SSMSE because you're working against different instances of SQL Express. VS uses User Instances by default, where SSMSE works against the main instance of Express.
Regards,
Mike Wachal
SQL Express team
-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1
This error is often caused because the parent instance (for whatever reason) can't copy the system databases to the users local isolated storage folders. Sometimes it is because of a previous install of SQL Express has left files in that directory which is why Reen's suggestion sometimes works
Delete C:\Documents and Settings\USERNAME\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS.
the only trick is knowing the USERNAME, if your writing a web app, the user is usually ASPNET which is usually found in
C:\Documents and Settings\COMPUTERNAME\USERNAME\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS
Other times it is a permissions issue which can be solved by giving the SQL service account the necessary permissions.
One thing to remember is that although user instances is the default when working with Visual Studio, it is not mandatory to use them, it is quite possible to attach to databases in the traditional way from SQL Express, to do this you just need to edit the connection string and delete the "user Instance=true". User Instances just make it easier (when it does work) to work with databases as though they were files.
|||This error is simply ridiculous! Not so much because it occurs a lot but that there is insufficient official documentation about this problem. Worst still you will run into this error if you try and copy the official online VS Express tutorial I found. Worse again, when Microsoft ran a seminar at my University this error occurred and they didn’t even know how to deal with it!
This forum thread right here is by far the best documentation of the problem that I have found so far and it’s not very easy to find or thorough.
|||There seem to be so many things that cause this user instance error. Currently I think the following explains why I'm getting it today. Next they will tell us that it only works when there is a full moon!
(Note the mention of SSEUtil not working... I think that's quite interesting)
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=58741&SiteID=1
I think I found the problem, I was not the first one to use the computer the days with the problem. Even SSEUtil gives the same error. When I switched users to the one that signed on first, SSEUtil worked. I tried signing off of the other computer users and restarting the SQL Server. SSEUtil still could not get the server to respond.
It looks like bottom line....If you need to use a sqldatabase with visual basic 2005 express, make sure you signed on the computer first or reboot before you start or return to your database project.
Mike
|||
The post you reference is from before the final release of SQL, so it's hard to say if the information still applies. Why do you think the above explains your situation? What troubleshooting have you done to check this? Have you checked the error logs for both the main instance and the User Instance?
I'd really like to see actual information about this problem as that is the only way to really understand what is happening.
Regards,
Mike Wachal
SQL Express team
Fair enough.
I am 90% sure that when another account has been logged in before mine this error occurs. I will try generating this error when I have time.
When I checked the error log briefly there did not seem to be any relevant information. Additionally when I generated this error the error log did not update. Implying that this error was not logged or maybe I was looking in the wrong place (not both instances)... again I will have to look into this further when I have more time.
I am using VS2005 (not express edition - thanks to my university) and the version of SQL Server that comes with it (Express).
If you browse the web you will find many different "solutions" to this error... I am happy to help where I can
|||When I ran into this problem the first time, I uninstalled the SQLExpress and reinstalled it. I could then access the database via the Visual C# 2005 Express Edition.Later, after I used the SQL management console to open and explore the SQL Express, the problem reoccurred.I uninstalled and reinstalled the SQL Express again, and it works again.
I don’t profess to understand why it works this way, but it did.
|||Apparently you have to be logged in as jking. And you have to have a D: drive.
SQL Express guys, know who that is?
I cannot get the start kits or time tracker kit going. The start kit does not have an aspnet.mdf. The personal.mdf will not attach or allow a login.
I changed the service to login from the local system account, no change.
I opened Personal.mdf in sql management studio and got:
Directory lookup for the file "D:\Documents and Settings\jking\My Documents\Visual Studio 2005\WebSites\WebSite1\App_Data\Personal_log.LDF" failed with the operating system error 21(the device is not ready)... error 5133
Teach me to use jking's code.
|||Login Order Problem ConfirmedOpened VS2005, can refresh database (I am the 1st and only user to log in)… reset computer…
Logged in as user A then switched to user B, opened VS2005, tried to refresh a database…
Timeout Error!
Try again and…
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
Below is the error log. Note that when I generate this error the error log does not get updated so I expect the following to be useless.
Where would I find the ‘main instance’ error log? There is nothing in All Users… not sure where else to look
Anything else?
C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log
2006-04-11 15:30:23.40 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2006-04-11 15:30:23.40 Server (c) 2005 Microsoft Corporation.
2006-04-11 15:30:23.40 Server All rights reserved.
2006-04-11 15:30:23.40 Server Server process ID is 2912.
2006-04-11 15:30:23.40 Server Logging SQL Server messages in file 'C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log'.
2006-04-11 15:30:23.40 Server Registry startup parameters:
2006-04-11 15:30:23.40 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-04-11 15:30:23.40 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-04-11 15:30:23.40 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-04-11 15:30:23.40 Server Command Line Startup Parameters:
2006-04-11 15:30:23.40 Server -d C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\master.mdf
2006-04-11 15:30:23.40 Server -l C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\mastlog.ldf
2006-04-11 15:30:23.40 Server -e C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log
2006-04-11 15:30:23.40 Server -c
2006-04-11 15:30:23.40 Server -S SQLEXPRESS
2006-04-11 15:30:23.40 Server -s AE669D1F-CC06-41
2006-04-11 15:30:23.40 Server -w 60
2006-04-11 15:30:23.42 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2006-04-11 15:30:23.42 Server Detected 2 CPUs. This is an informational message; no user action is required.
2006-04-11 15:30:23.87 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2006-04-11 15:30:23.89 Server Database Mirroring Transport is disabled in the endpoint configuration.
2006-04-11 15:30:23.89 spid4s Starting up database 'master'.
2006-04-11 15:30:23.95 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2006-04-11 15:30:24.00 spid4s SQL Trace ID 1 was started by login "sa".
2006-04-11 15:30:24.03 spid4s Starting up database 'mssqlsystemresource'.
2006-04-11 15:30:24.20 spid7s Starting up database 'model'.
2006-04-11 15:30:24.20 Server Server local connection provider is ready to accept connection on [ \\.\pipe\AE669D1F-CC06-41\tsql\query ].
2006-04-11 15:30:24.20 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2006-04-11 15:30:24.21 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2006-04-11 15:30:24.21 spid4s Server name is 'KEVINS\AE669D1F-CC06-41'. This is an informational message only. No user action is required.
2006-04-11 15:30:24.29 spid4s Starting up database 'msdb'.
2006-04-11 15:30:24.42 spid7s Clearing tempdb database.
2006-04-11 15:30:24.85 spid7s Starting up database 'tempdb'.
2006-04-11 15:30:24.92 spid4s Recovery is complete. This is an informational message only. No user action is required.
2006-04-11 15:30:24.93 spid10s The Service Broker protocol transport is disabled or not configured.
2006-04-11 15:30:24.93 spid10s The Database Mirroring protocol transport is disabled or not configured.
2006-04-11 15:30:24.95 spid10s Service Broker manager has started.
|||
I just wrote this post on Community Starter Kit personal.mdf, commercedb.mdf and aspnetdb.mdf.
ASP.Net 2.0 Community Starter Kit SQL Express Conversion to SQL 2005
Hope it helps
- Caroline
http://bogartcomputing.com
|||
Make user instance as false. It solves the problem...
Data Source=.\SQLEXPRESS;AttachDbFilename=D:\Test\App_Data\test.mdf;Integrated Security=True;User Instance=false
Hope it helps,
Thanks,
Manoj.
|||Make user instance as false. It solves the problem...
Data Source=.\SQLEXPRESS;AttachDbFilename=D:\Test\App_Data\test.mdf;Integrated Security=True;User Instance=false
Hope it helps,
Thanks,
Manoj.
Doing that caused other problems for me.
|||
Hi all,
I'd like to say I was able to reproduce this behavior, but I cannot - at least not 100%... My error(s) seems to alternate between "Failed to generate..." and "Timeout expired. The timeout period elapsed prior to the completion of the operation or the server is not responding."
However, this all seems to happen when another user has or establishes a local session on the computer. I am running WinXP Pro SP2 w/most recent patches and have Fast User Switching enabled so that my wife and I can still use the machine when the other is not around.
So here's an example. My wife wakes before me and logs onto the machine and checks the weather. She leaves, eats breakfast and heads out the door. 20 minutes later, her session is "suspended" and Windows returns to the Welcome Screen.
After dinner, I log onto the machine to do some coding, keeping her session suspended so that she doesn't loose any work. I fire up VS2k5 and create a new project. I try and create a new database and, depeneding on the type of project (WinForms or Web Site), I either receive one of the "Timeout" or "Failed to generate..." errors. I log off out of frustration.
Right before my wife goes to bed, she checks the weather again and then logs off and closes her session.
I return, just before bed, I log in and try once more to create my database...And it works.
I have a handful of error log files if and 2 screen shots if this information would assist anyone.
Thanks,
Failed to generate a user instance of SQL Server due to a failure in starting the process for th
No wonder Microsoft is giving it away for free. It’s not worth anything. I am very disappointed in this version of SQL server. I decided to start learning VB so I downloaded and installed VB 2005 express edition and SQL 2005 express. I tried to build a personal website using the starter kit. I kept getting the following error message, for which I have seen numerous postings on this forum.
“Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.”
I went out and bought the Standard version of VS 2005 thinking there may be a feature that the free express version is lacking. I uninstalled the express version, cleaned the registry, deleted all the folders it created and installed the Standard edition. Then I tried to create a personal web using the starter kit and it does the same thing again.
I can not create a database file, connect to a database file. I can not create or attach a database on the SQL 2005 express from VS 2005. The SQL server Express seems to be working OK since I can attach to it using Microsoft SQL Server Management Studio Express. There is something about the way VS tries to connect to the database server that is not working. VB does recognize the local computer as a SQL server but can not connect to it.
SQL server is set to accept Shared memory, TCP/IP and named pipes for local clients.
What is causing this?
This is some information on the system I am using:
MS XP (SP2)
Microsoft Visual Studio 2005
Version 8.0.50727.42(RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727
Installed Edition: Standard
Microsoft SQL Server Management Studio Express9.00.1399.00
Microsoft Data Access Components (MDAC)2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer6.0.2900.2180
Microsoft .NET Framework2.0.50727.42
Operating System5.1.2600
I am now to programming but nor computer illiterate. I have been working with MS SQL servers since version 6.5 and have MCSE, Network+, A+ and Security plus certifications. Installing and using VS should not be this problematic. What is wrong with Microsoft?
I got this very frustating message everytime I was trying to create a new SQL Express database from VB Express. All forums seem to point to 2 possible resolutions, NONE of which worked for me:
A) Known bug with Windows XP SP2 when using SQL via RDP (Remote Desktop).
B) Delete C:\Documents and Settings\USERNAME\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS.
The clue for me was all forums relating to solution B seemed to talk about possible authentication problems which gave me a clue. My solution was therefore:
Solution: Modify the SQL Server (SQLExpress) service to use your local or system account and restart the service. This worked for me first time. I'm not sure if this will cause any problems in the future but hey, at least I can now create a database!!
Hope this helps!!
|||As far as the "Failed to generate a user instances..." error, check out the error log for the user instance, it will likely give you more information about what is happening. You will fine the error log at C:\Documents and Settings\<user name>\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS.
User Instances are a new feature in SQL Express that have some special characteristics. You may want to read the white paper that discusses them to get some background. Creating a database from within VS is actually different that creating one in SSMSE because you're working against different instances of SQL Express. VS uses User Instances by default, where SSMSE works against the main instance of Express.
Regards,
Mike Wachal
SQL Express team
-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1
This error is often caused because the parent instance (for whatever reason) can't copy the system databases to the users local isolated storage folders. Sometimes it is because of a previous install of SQL Express has left files in that directory which is why Reen's suggestion sometimes works
Delete C:\Documents and Settings\USERNAME\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS.
the only trick is knowing the USERNAME, if your writing a web app, the user is usually ASPNET which is usually found in
C:\Documents and Settings\COMPUTERNAME\USERNAME\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS
Other times it is a permissions issue which can be solved by giving the SQL service account the necessary permissions.
One thing to remember is that although user instances is the default when working with Visual Studio, it is not mandatory to use them, it is quite possible to attach to databases in the traditional way from SQL Express, to do this you just need to edit the connection string and delete the "user Instance=true". User Instances just make it easier (when it does work) to work with databases as though they were files.
|||This error is simply ridiculous! Not so much because it occurs a lot but that there is insufficient official documentation about this problem. Worst still you will run into this error if you try and copy the official online VS Express tutorial I found. Worse again, when Microsoft ran a seminar at my University this error occurred and they didn’t even know how to deal with it!
This forum thread right here is by far the best documentation of the problem that I have found so far and it’s not very easy to find or thorough.
|||There seem to be so many things that cause this user instance error. Currently I think the following explains why I'm getting it today. Next they will tell us that it only works when there is a full moon!
(Note the mention of SSEUtil not working... I think that's quite interesting)
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=58741&SiteID=1
I think I found the problem, I was not the first one to use the computer the days with the problem. Even SSEUtil gives the same error. When I switched users to the one that signed on first, SSEUtil worked. I tried signing off of the other computer users and restarting the SQL Server. SSEUtil still could not get the server to respond.
It looks like bottom line....If you need to use a sqldatabase with visual basic 2005 express, make sure you signed on the computer first or reboot before you start or return to your database project.
Mike
|||
The post you reference is from before the final release of SQL, so it's hard to say if the information still applies. Why do you think the above explains your situation? What troubleshooting have you done to check this? Have you checked the error logs for both the main instance and the User Instance?
I'd really like to see actual information about this problem as that is the only way to really understand what is happening.
Regards,
Mike Wachal
SQL Express team
Fair enough.
I am 90% sure that when another account has been logged in before mine this error occurs. I will try generating this error when I have time.
When I checked the error log briefly there did not seem to be any relevant information. Additionally when I generated this error the error log did not update. Implying that this error was not logged or maybe I was looking in the wrong place (not both instances)... again I will have to look into this further when I have more time.
I am using VS2005 (not express edition - thanks to my university) and the version of SQL Server that comes with it (Express).
If you browse the web you will find many different "solutions" to this error... I am happy to help where I can
|||When I ran into this problem the first time, I uninstalled the SQLExpress and reinstalled it. I could then access the database via the Visual C# 2005 Express Edition.Later, after I used the SQL management console to open and explore the SQL Express, the problem reoccurred.I uninstalled and reinstalled the SQL Express again, and it works again.
I don’t profess to understand why it works this way, but it did.
|||Apparently you have to be logged in as jking. And you have to have a D: drive.
SQL Express guys, know who that is?
I cannot get the start kits or time tracker kit going. The start kit does not have an aspnet.mdf. The personal.mdf will not attach or allow a login.
I changed the service to login from the local system account, no change.
I opened Personal.mdf in sql management studio and got:
Directory lookup for the file "D:\Documents and Settings\jking\My Documents\Visual Studio 2005\WebSites\WebSite1\App_Data\Personal_log.LDF" failed with the operating system error 21(the device is not ready)... error 5133
Teach me to use jking's code.
|||Login Order Problem ConfirmedOpened VS2005, can refresh database (I am the 1st and only user to log in)… reset computer…
Logged in as user A then switched to user B, opened VS2005, tried to refresh a database…
Timeout Error!
Try again and…
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
Below is the error log. Note that when I generate this error the error log does not get updated so I expect the following to be useless.
Where would I find the ‘main instance’ error log? There is nothing in All Users… not sure where else to look
Anything else?
C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log
2006-04-11 15:30:23.40 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2006-04-11 15:30:23.40 Server (c) 2005 Microsoft Corporation.
2006-04-11 15:30:23.40 Server All rights reserved.
2006-04-11 15:30:23.40 Server Server process ID is 2912.
2006-04-11 15:30:23.40 Server Logging SQL Server messages in file 'C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log'.
2006-04-11 15:30:23.40 Server Registry startup parameters:
2006-04-11 15:30:23.40 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-04-11 15:30:23.40 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-04-11 15:30:23.40 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-04-11 15:30:23.40 Server Command Line Startup Parameters:
2006-04-11 15:30:23.40 Server -d C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\master.mdf
2006-04-11 15:30:23.40 Server -l C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\mastlog.ldf
2006-04-11 15:30:23.40 Server -e C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log
2006-04-11 15:30:23.40 Server -c
2006-04-11 15:30:23.40 Server -S SQLEXPRESS
2006-04-11 15:30:23.40 Server -s AE669D1F-CC06-41
2006-04-11 15:30:23.40 Server -w 60
2006-04-11 15:30:23.42 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2006-04-11 15:30:23.42 Server Detected 2 CPUs. This is an informational message; no user action is required.
2006-04-11 15:30:23.87 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2006-04-11 15:30:23.89 Server Database Mirroring Transport is disabled in the endpoint configuration.
2006-04-11 15:30:23.89 spid4s Starting up database 'master'.
2006-04-11 15:30:23.95 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2006-04-11 15:30:24.00 spid4s SQL Trace ID 1 was started by login "sa".
2006-04-11 15:30:24.03 spid4s Starting up database 'mssqlsystemresource'.
2006-04-11 15:30:24.20 spid7s Starting up database 'model'.
2006-04-11 15:30:24.20 Server Server local connection provider is ready to accept connection on [ \\.\pipe\AE669D1F-CC06-41\tsql\query ].
2006-04-11 15:30:24.20 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2006-04-11 15:30:24.21 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2006-04-11 15:30:24.21 spid4s Server name is 'KEVINS\AE669D1F-CC06-41'. This is an informational message only. No user action is required.
2006-04-11 15:30:24.29 spid4s Starting up database 'msdb'.
2006-04-11 15:30:24.42 spid7s Clearing tempdb database.
2006-04-11 15:30:24.85 spid7s Starting up database 'tempdb'.
2006-04-11 15:30:24.92 spid4s Recovery is complete. This is an informational message only. No user action is required.
2006-04-11 15:30:24.93 spid10s The Service Broker protocol transport is disabled or not configured.
2006-04-11 15:30:24.93 spid10s The Database Mirroring protocol transport is disabled or not configured.
2006-04-11 15:30:24.95 spid10s Service Broker manager has started.
|||
I just wrote this post on Community Starter Kit personal.mdf, commercedb.mdf and aspnetdb.mdf.
ASP.Net 2.0 Community Starter Kit SQL Express Conversion to SQL 2005
Hope it helps
- Caroline
http://bogartcomputing.com
|||
Make user instance as false. It solves the problem...
Data Source=.\SQLEXPRESS;AttachDbFilename=D:\Test\App_Data\test.mdf;Integrated Security=True;User Instance=false
Hope it helps,
Thanks,
Manoj.
|||Make user instance as false. It solves the problem...
Data Source=.\SQLEXPRESS;AttachDbFilename=D:\Test\App_Data\test.mdf;Integrated Security=True;User Instance=false
Hope it helps,
Thanks,
Manoj.
Doing that caused other problems for me.
|||
Hi all,
I'd like to say I was able to reproduce this behavior, but I cannot - at least not 100%... My error(s) seems to alternate between "Failed to generate..." and "Timeout expired. The timeout period elapsed prior to the completion of the operation or the server is not responding."
However, this all seems to happen when another user has or establishes a local session on the computer. I am running WinXP Pro SP2 w/most recent patches and have Fast User Switching enabled so that my wife and I can still use the machine when the other is not around.
So here's an example. My wife wakes before me and logs onto the machine and checks the weather. She leaves, eats breakfast and heads out the door. 20 minutes later, her session is "suspended" and Windows returns to the Welcome Screen.
After dinner, I log onto the machine to do some coding, keeping her session suspended so that she doesn't loose any work. I fire up VS2k5 and create a new project. I try and create a new database and, depeneding on the type of project (WinForms or Web Site), I either receive one of the "Timeout" or "Failed to generate..." errors. I log off out of frustration.
Right before my wife goes to bed, she checks the weather again and then logs off and closes her session.
I return, just before bed, I log in and try once more to create my database...And it works.
I have a handful of error log files if and 2 screen shots if this information would assist anyone.
Thanks,
Failed to generate a user instance of SQL Server due to a failure in starting the process for th
No wonder Microsoft is giving it away for free. It’s not worth anything. I am very disappointed in this version of SQL server. I decided to start learning VB so I downloaded and installed VB 2005 express edition and SQL 2005 express. I tried to build a personal website using the starter kit. I kept getting the following error message, for which I have seen numerous postings on this forum.
“Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.”
I went out and bought the Standard version of VS 2005 thinking there may be a feature that the free express version is lacking. I uninstalled the express version, cleaned the registry, deleted all the folders it created and installed the Standard edition. Then I tried to create a personal web using the starter kit and it does the same thing again.
I can not create a database file, connect to a database file. I can not create or attach a database on the SQL 2005 express from VS 2005. The SQL server Express seems to be working OK since I can attach to it using Microsoft SQL Server Management Studio Express. There is something about the way VS tries to connect to the database server that is not working. VB does recognize the local computer as a SQL server but can not connect to it.
SQL server is set to accept Shared memory, TCP/IP and named pipes for local clients.
What is causing this?
This is some information on the system I am using:
MS XP (SP2)
Microsoft Visual Studio 2005
Version 8.0.50727.42(RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727
Installed Edition: Standard
Microsoft SQL Server Management Studio Express9.00.1399.00
Microsoft Data Access Components (MDAC)2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer6.0.2900.2180
Microsoft .NET Framework2.0.50727.42
Operating System5.1.2600
I am now to programming but nor computer illiterate. I have been working with MS SQL servers since version 6.5 and have MCSE, Network+, A+ and Security plus certifications. Installing and using VS should not be this problematic. What is wrong with Microsoft?
I got this very frustating message everytime I was trying to create a new SQL Express database from VB Express. All forums seem to point to 2 possible resolutions, NONE of which worked for me:
A) Known bug with Windows XP SP2 when using SQL via RDP (Remote Desktop).
B) Delete C:\Documents and Settings\USERNAME\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS.
The clue for me was all forums relating to solution B seemed to talk about possible authentication problems which gave me a clue. My solution was therefore:
Solution: Modify the SQL Server (SQLExpress) service to use your local or system account and restart the service. This worked for me first time. I'm not sure if this will cause any problems in the future but hey, at least I can now create a database!!
Hope this helps!!
|||As far as the "Failed to generate a user instances..." error, check out the error log for the user instance, it will likely give you more information about what is happening. You will fine the error log at C:\Documents and Settings\<user name>\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS.
User Instances are a new feature in SQL Express that have some special characteristics. You may want to read the white paper that discusses them to get some background. Creating a database from within VS is actually different that creating one in SSMSE because you're working against different instances of SQL Express. VS uses User Instances by default, where SSMSE works against the main instance of Express.
Regards,
Mike Wachal
SQL Express team
-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1
This error is often caused because the parent instance (for whatever reason) can't copy the system databases to the users local isolated storage folders. Sometimes it is because of a previous install of SQL Express has left files in that directory which is why Reen's suggestion sometimes works
Delete C:\Documents and Settings\USERNAME\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS.
the only trick is knowing the USERNAME, if your writing a web app, the user is usually ASPNET which is usually found in
C:\Documents and Settings\COMPUTERNAME\USERNAME\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS
Other times it is a permissions issue which can be solved by giving the SQL service account the necessary permissions.
One thing to remember is that although user instances is the default when working with Visual Studio, it is not mandatory to use them, it is quite possible to attach to databases in the traditional way from SQL Express, to do this you just need to edit the connection string and delete the "user Instance=true". User Instances just make it easier (when it does work) to work with databases as though they were files.
|||This error is simply ridiculous! Not so much because it occurs a lot but that there is insufficient official documentation about this problem. Worst still you will run into this error if you try and copy the official online VS Express tutorial I found. Worse again, when Microsoft ran a seminar at my University this error occurred and they didn’t even know how to deal with it!
This forum thread right here is by far the best documentation of the problem that I have found so far and it’s not very easy to find or thorough.
|||There seem to be so many things that cause this user instance error. Currently I think the following explains why I'm getting it today. Next they will tell us that it only works when there is a full moon!
(Note the mention of SSEUtil not working... I think that's quite interesting)
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=58741&SiteID=1
I think I found the problem, I was not the first one to use the computer the days with the problem. Even SSEUtil gives the same error. When I switched users to the one that signed on first, SSEUtil worked. I tried signing off of the other computer users and restarting the SQL Server. SSEUtil still could not get the server to respond.
It looks like bottom line....If you need to use a sqldatabase with visual basic 2005 express, make sure you signed on the computer first or reboot before you start or return to your database project.
Mike
|||
The post you reference is from before the final release of SQL, so it's hard to say if the information still applies. Why do you think the above explains your situation? What troubleshooting have you done to check this? Have you checked the error logs for both the main instance and the User Instance?
I'd really like to see actual information about this problem as that is the only way to really understand what is happening.
Regards,
Mike Wachal
SQL Express team
Fair enough.
I am 90% sure that when another account has been logged in before mine this error occurs. I will try generating this error when I have time.
When I checked the error log briefly there did not seem to be any relevant information. Additionally when I generated this error the error log did not update. Implying that this error was not logged or maybe I was looking in the wrong place (not both instances)... again I will have to look into this further when I have more time.
I am using VS2005 (not express edition - thanks to my university) and the version of SQL Server that comes with it (Express).
If you browse the web you will find many different "solutions" to this error... I am happy to help where I can
|||When I ran into this problem the first time, I uninstalled the SQLExpress and reinstalled it. I could then access the database via the Visual C# 2005 Express Edition.Later, after I used the SQL management console to open and explore the SQL Express, the problem reoccurred.I uninstalled and reinstalled the SQL Express again, and it works again.
I don’t profess to understand why it works this way, but it did.
|||Apparently you have to be logged in as jking. And you have to have a D: drive.
SQL Express guys, know who that is?
I cannot get the start kits or time tracker kit going. The start kit does not have an aspnet.mdf. The personal.mdf will not attach or allow a login.
I changed the service to login from the local system account, no change.
I opened Personal.mdf in sql management studio and got:
Directory lookup for the file "D:\Documents and Settings\jking\My Documents\Visual Studio 2005\WebSites\WebSite1\App_Data\Personal_log.LDF" failed with the operating system error 21(the device is not ready)... error 5133
Teach me to use jking's code.
|||Login Order Problem ConfirmedOpened VS2005, can refresh database (I am the 1st and only user to log in)… reset computer…
Logged in as user A then switched to user B, opened VS2005, tried to refresh a database…
Timeout Error!
Try again and…
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
Below is the error log. Note that when I generate this error the error log does not get updated so I expect the following to be useless.
Where would I find the ‘main instance’ error log? There is nothing in All Users… not sure where else to look
Anything else?
C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log
2006-04-11 15:30:23.40 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2006-04-11 15:30:23.40 Server (c) 2005 Microsoft Corporation.
2006-04-11 15:30:23.40 Server All rights reserved.
2006-04-11 15:30:23.40 Server Server process ID is 2912.
2006-04-11 15:30:23.40 Server Logging SQL Server messages in file 'C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log'.
2006-04-11 15:30:23.40 Server Registry startup parameters:
2006-04-11 15:30:23.40 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-04-11 15:30:23.40 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-04-11 15:30:23.40 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-04-11 15:30:23.40 Server Command Line Startup Parameters:
2006-04-11 15:30:23.40 Server -d C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\master.mdf
2006-04-11 15:30:23.40 Server -l C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\mastlog.ldf
2006-04-11 15:30:23.40 Server -e C:\Documents and Settings\Kevin\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log
2006-04-11 15:30:23.40 Server -c
2006-04-11 15:30:23.40 Server -S SQLEXPRESS
2006-04-11 15:30:23.40 Server -s AE669D1F-CC06-41
2006-04-11 15:30:23.40 Server -w 60
2006-04-11 15:30:23.42 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2006-04-11 15:30:23.42 Server Detected 2 CPUs. This is an informational message; no user action is required.
2006-04-11 15:30:23.87 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2006-04-11 15:30:23.89 Server Database Mirroring Transport is disabled in the endpoint configuration.
2006-04-11 15:30:23.89 spid4s Starting up database 'master'.
2006-04-11 15:30:23.95 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2006-04-11 15:30:24.00 spid4s SQL Trace ID 1 was started by login "sa".
2006-04-11 15:30:24.03 spid4s Starting up database 'mssqlsystemresource'.
2006-04-11 15:30:24.20 spid7s Starting up database 'model'.
2006-04-11 15:30:24.20 Server Server local connection provider is ready to accept connection on [ \\.\pipe\AE669D1F-CC06-41\tsql\query ].
2006-04-11 15:30:24.20 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2006-04-11 15:30:24.21 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2006-04-11 15:30:24.21 spid4s Server name is 'KEVINS\AE669D1F-CC06-41'. This is an informational message only. No user action is required.
2006-04-11 15:30:24.29 spid4s Starting up database 'msdb'.
2006-04-11 15:30:24.42 spid7s Clearing tempdb database.
2006-04-11 15:30:24.85 spid7s Starting up database 'tempdb'.
2006-04-11 15:30:24.92 spid4s Recovery is complete. This is an informational message only. No user action is required.
2006-04-11 15:30:24.93 spid10s The Service Broker protocol transport is disabled or not configured.
2006-04-11 15:30:24.93 spid10s The Database Mirroring protocol transport is disabled or not configured.
2006-04-11 15:30:24.95 spid10s Service Broker manager has started.
|||
I just wrote this post on Community Starter Kit personal.mdf, commercedb.mdf and aspnetdb.mdf.
ASP.Net 2.0 Community Starter Kit SQL Express Conversion to SQL 2005
Hope it helps
- Caroline
http://bogartcomputing.com
|||
Make user instance as false. It solves the problem...
Data Source=.\SQLEXPRESS;AttachDbFilename=D:\Test\App_Data\test.mdf;Integrated Security=True;User Instance=false
Hope it helps,
Thanks,
Manoj.
|||Make user instance as false. It solves the problem...
Data Source=.\SQLEXPRESS;AttachDbFilename=D:\Test\App_Data\test.mdf;Integrated Security=True;User Instance=false
Hope it helps,
Thanks,
Manoj.
Doing that caused other problems for me.
|||
Hi all,
I'd like to say I was able to reproduce this behavior, but I cannot - at least not 100%... My error(s) seems to alternate between "Failed to generate..." and "Timeout expired. The timeout period elapsed prior to the completion of the operation or the server is not responding."
However, this all seems to happen when another user has or establishes a local session on the computer. I am running WinXP Pro SP2 w/most recent patches and have Fast User Switching enabled so that my wife and I can still use the machine when the other is not around.
So here's an example. My wife wakes before me and logs onto the machine and checks the weather. She leaves, eats breakfast and heads out the door. 20 minutes later, her session is "suspended" and Windows returns to the Welcome Screen.
After dinner, I log onto the machine to do some coding, keeping her session suspended so that she doesn't loose any work. I fire up VS2k5 and create a new project. I try and create a new database and, depeneding on the type of project (WinForms or Web Site), I either receive one of the "Timeout" or "Failed to generate..." errors. I log off out of frustration.
Right before my wife goes to bed, she checks the weather again and then logs off and closes her session.
I return, just before bed, I log in and try once more to create my database...And it works.
I have a handful of error log files if and 2 screen shots if this information would assist anyone.
Thanks,
Subscribe to:
Posts (Atom)