I'm using VS2005 pro to develop one windows form and one Mobile5.0 app ,
they are simple apps and just connect to SQL server to get data. The SQL
servers include Win2K + SQL2K, Win2K3 + SQL2K5 std and Win2K3 + SQL2K5
Express.
All works fine until one day I updated Win2K3 patches to the sql server via
windows update.
The mobile 5.0 app can not connect the SQL 2005 express any more, it will
get error message:
"Can not find specific sql server SERVERNAME\SQLEXPRESS", I didn't change
any codes
or settings. But it still can connect to SQL2000 or SQL 2005 std.
The Windows app is able to connect to SQL2000/SQL2005 std/SQL 2005 express
without
any problem.
Any clue? thanks in advance!Apparently, that's not a supported configuration. I'd seen that some
people had tried it and gotten it to work, so maybe MS did something
active to turn it off.|||I don't know why it wouldn't be supported. I assume you are using SQLClient
to connect to SQL Express? Do you get an error message on the client? Are
there any errors in the SQL Express error log?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"rick" <rickkozak@.hotmail.com> wrote in message
news:1149164611.354005.100770@.y43g2000cwc.googlegroups.com...
> Apparently, that's not a supported configuration. I'd seen that some
> people had tried it and gotten it to work, so maybe MS did something
> active to turn it off.
>|||Yes, I used the System.Data.SQLClient in the Mobile 5.0 app.
The problem here is it works for SQL 2005 Express in the begining.
But it's failed after applying windows 2003 patches.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> glsD:OXJ020chGHA.3756@.TK2MSFTNGP02.
phx.gbl...
>I don't know why it wouldn't be supported. I assume you are using
>SQLClient to connect to SQL Express? Do you get an error message on the
>client? Are there any errors in the SQL Express error log?
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "rick" <rickkozak@.hotmail.com> wrote in message
> news:1149164611.354005.100770@.y43g2000cwc.googlegroups.com...
>|||Sorry, if "failed" is all you're willing to tell us, I don't think we can be
of much help. Depending on which patches you installed, some network or
security setting may have changed.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"RedHair" <redhair@.ms40.url.com.tw> wrote in message
news:u5ZPZihhGHA.4388@.TK2MSFTNGP05.phx.gbl...
> Yes, I used the System.Data.SQLClient in the Mobile 5.0 app.
> The problem here is it works for SQL 2005 Express in the begining.
> But it's failed after applying windows 2003 patches.
>
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com>
> glsD:OXJ020chGHA.3756@.TK2MSFTNGP02.phx.gbl...
>|||In my orginal post , I have mentioned the error msg is
"Specified SQL server not found: ServerName\SQLEXPRESS"
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:OKyb8alhGHA.3584@.TK2MSFTNGP04.phx.gbl...
> Sorry, if "failed" is all you're willing to tell us, I don't think we can
> be of much help. Depending on which patches you installed, some network
> or security setting may have changed.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "RedHair" <redhair@.ms40.url.com.tw> wrote in message
> news:u5ZPZihhGHA.4388@.TK2MSFTNGP05.phx.gbl...
>
Showing posts with label pro. Show all posts
Showing posts with label pro. Show all posts
Friday, March 23, 2012
Mobile 5.0 app can not connect to SQL 2005 Express
I'm using VS2005 pro to develop one windows form and one Mobile5.0 app ,
they are simple apps and just connect to SQL server to get data. The SQL
servers include Win2K + SQL2K, Win2K3 + SQL2K5 std and Win2K3 + SQL2K5
Express.
All works fine until one day I updated Win2K3 patches to the sql server via
windows update.
The mobile 5.0 app can not connect the SQL 2005 express any more, it will
get error message:
"Can not find specific sql server SERVERNAME\SQLEXPRESS", I didn't change
any codes
or settings. But it still can connect to SQL2000 or SQL 2005 std.
The Windows app is able to connect to SQL2000/SQL2005 std/SQL 2005 express
without
any problem.
Any clue? thanks in advance!Apparently, that's not a supported configuration. I'd seen that some
people had tried it and gotten it to work, so maybe MS did something
active to turn it off.|||I don't know why it wouldn't be supported. I assume you are using SQLClient
to connect to SQL Express? Do you get an error message on the client? Are
there any errors in the SQL Express error log?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"rick" <rickkozak@.hotmail.com> wrote in message
news:1149164611.354005.100770@.y43g2000cwc.googlegroups.com...
> Apparently, that's not a supported configuration. I'd seen that some
> people had tried it and gotten it to work, so maybe MS did something
> active to turn it off.
>|||Yes, I used the System.Data.SQLClient in the Mobile 5.0 app.
The problem here is it works for SQL 2005 Express in the begining.
But it's failed after applying windows 2003 patches.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> glsD:OXJ020chGHA.3756@.TK2M
SFTNGP02.phx.gbl...
>I don't know why it wouldn't be supported. I assume you are using
>SQLClient to connect to SQL Express? Do you get an error message on the
>client? Are there any errors in the SQL Express error log?
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "rick" <rickkozak@.hotmail.com> wrote in message
> news:1149164611.354005.100770@.y43g2000cwc.googlegroups.com...
>|||Sorry, if "failed" is all you're willing to tell us, I don't think we can be
of much help. Depending on which patches you installed, some network or
security setting may have changed.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"RedHair" <redhair@.ms40.url.com.tw> wrote in message
news:u5ZPZihhGHA.4388@.TK2MSFTNGP05.phx.gbl...
> Yes, I used the System.Data.SQLClient in the Mobile 5.0 app.
> The problem here is it works for SQL 2005 Express in the begining.
> But it's failed after applying windows 2003 patches.
>
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com>
> glsD:OXJ020chGHA.3756@.TK2MSFTNGP02.phx.gbl...
>|||In my orginal post , I have mentioned the error msg is
"Specified SQL server not found: ServerName\SQLEXPRESS"
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:OKyb8alhGHA.3584@.TK2MSFTNGP04.phx.gbl...
> Sorry, if "failed" is all you're willing to tell us, I don't think we can
> be of much help. Depending on which patches you installed, some network
> or security setting may have changed.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "RedHair" <redhair@.ms40.url.com.tw> wrote in message
> news:u5ZPZihhGHA.4388@.TK2MSFTNGP05.phx.gbl...
>
they are simple apps and just connect to SQL server to get data. The SQL
servers include Win2K + SQL2K, Win2K3 + SQL2K5 std and Win2K3 + SQL2K5
Express.
All works fine until one day I updated Win2K3 patches to the sql server via
windows update.
The mobile 5.0 app can not connect the SQL 2005 express any more, it will
get error message:
"Can not find specific sql server SERVERNAME\SQLEXPRESS", I didn't change
any codes
or settings. But it still can connect to SQL2000 or SQL 2005 std.
The Windows app is able to connect to SQL2000/SQL2005 std/SQL 2005 express
without
any problem.
Any clue? thanks in advance!Apparently, that's not a supported configuration. I'd seen that some
people had tried it and gotten it to work, so maybe MS did something
active to turn it off.|||I don't know why it wouldn't be supported. I assume you are using SQLClient
to connect to SQL Express? Do you get an error message on the client? Are
there any errors in the SQL Express error log?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"rick" <rickkozak@.hotmail.com> wrote in message
news:1149164611.354005.100770@.y43g2000cwc.googlegroups.com...
> Apparently, that's not a supported configuration. I'd seen that some
> people had tried it and gotten it to work, so maybe MS did something
> active to turn it off.
>|||Yes, I used the System.Data.SQLClient in the Mobile 5.0 app.
The problem here is it works for SQL 2005 Express in the begining.
But it's failed after applying windows 2003 patches.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> glsD:OXJ020chGHA.3756@.TK2M
SFTNGP02.phx.gbl...
>I don't know why it wouldn't be supported. I assume you are using
>SQLClient to connect to SQL Express? Do you get an error message on the
>client? Are there any errors in the SQL Express error log?
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "rick" <rickkozak@.hotmail.com> wrote in message
> news:1149164611.354005.100770@.y43g2000cwc.googlegroups.com...
>|||Sorry, if "failed" is all you're willing to tell us, I don't think we can be
of much help. Depending on which patches you installed, some network or
security setting may have changed.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"RedHair" <redhair@.ms40.url.com.tw> wrote in message
news:u5ZPZihhGHA.4388@.TK2MSFTNGP05.phx.gbl...
> Yes, I used the System.Data.SQLClient in the Mobile 5.0 app.
> The problem here is it works for SQL 2005 Express in the begining.
> But it's failed after applying windows 2003 patches.
>
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com>
> glsD:OXJ020chGHA.3756@.TK2MSFTNGP02.phx.gbl...
>|||In my orginal post , I have mentioned the error msg is
"Specified SQL server not found: ServerName\SQLEXPRESS"
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:OKyb8alhGHA.3584@.TK2MSFTNGP04.phx.gbl...
> Sorry, if "failed" is all you're willing to tell us, I don't think we can
> be of much help. Depending on which patches you installed, some network
> or security setting may have changed.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "RedHair" <redhair@.ms40.url.com.tw> wrote in message
> news:u5ZPZihhGHA.4388@.TK2MSFTNGP05.phx.gbl...
>
MMC Can't open SQL Server Enterprise Manager.msc
Hi All,
I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
error:
MMC cannot open the file c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
the files does not exist, is not an MMC console, or was created by a later
version of MMC. This may also be because you do not have sufficied access
rights to the file.
...when trying to run Enterprise Manager. I have tried re-installing the
server and client tools, and SP3a, but still the same error.
I have administrator access to the PC, but strangely, I can run enterprise
manager if logged on as the local administrator. I can also run SQL Server
Enterprise Manager.msc if I rename it to anything else, and it seems to work
all right.
Shall I just carry on using the new SQL Server Enterprise Manager 2? It
seems like a very odd issue.
Thanks in advance.
RyanRyan,
Can you rename it to SQLEM.msc? Does that work? Then just create a
shortcut on your desktop or Start Menu, and all should be well.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Ryan Breakspear wrote:
> Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be becau
se
> the files does not exist, is not an MMC console, or was created by a later
> version of MMC. This may also be because you do not have sufficied access
> rights to the file.
> ...when trying to run Enterprise Manager. I have tried re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run enterprise
> manager if logged on as the local administrator. I can also run SQL Serve
r
> Enterprise Manager.msc if I rename it to anything else, and it seems to wo
rk
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2? It
> seems like a very odd issue.
> Thanks in advance.
> Ryan
>|||Yep, I can rename it to anything. I can run it fine renamed as something
else, I just wondered why the problem, and if there was a solution.
Thanks for your reply.
Ryan
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:edplxoLcEHA.1248@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Ryan,
> Can you rename it to SQLEM.msc? Does that work? Then just create a
> shortcut on your desktop or Start Menu, and all should be well.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Ryan Breakspear wrote:
because[vbcol=seagreen]
later[vbcol=seagreen]
access[vbcol=seagreen]
the[vbcol=seagreen]
enterprise[vbcol=seagreen]
Server[vbcol=seagreen]
work[vbcol=seagreen]|||I have the exact same settings, and the exact same problem. Wish I had
found this workaround before re-installing everything... Still would
like to know what is causing this though...
Cheers - Craig
Ryan Breakspear wrote:
> *Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting
> the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
> because
> the files does not exist, is not an MMC console, or was created by a
> later
> version of MMC. This may also be because you do not have sufficied
> access
> rights to the file.
> ....when trying to run Enterprise Manager. I have tried
> re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run
> enterprise
> manager if logged on as the local administrator. I can also run SQL
> Server
> Enterprise Manager.msc if I rename it to anything else, and it seems
> to work
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2?
> It
> seems like a very odd issue.
> Thanks in advance.
> Ryan *
cjeff
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message888314.html|||I have been trying to fix this problem for some time. The fact that it
worked for you when you renamed it tipped me off to the source of the
problem. There is a cached version of the MMC file in the C:\Documents and
Settings\<username>\Application Data\Microsoft\MMC folder.
The problem is that on my system that cached file was corrupted.
Once I deleted the cached file, I was able to open SQL EntMgr with no proble
m.
"cjeff" wrote:
> I have the exact same settings, and the exact same problem. Wish I had
> found this workaround before re-installing everything... Still would
> like to know what is causing this though...
> Cheers - Craig
> Ryan Breakspear wrote:
>
> --
> cjeff
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message888314.html
>
I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
error:
MMC cannot open the file c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
the files does not exist, is not an MMC console, or was created by a later
version of MMC. This may also be because you do not have sufficied access
rights to the file.
...when trying to run Enterprise Manager. I have tried re-installing the
server and client tools, and SP3a, but still the same error.
I have administrator access to the PC, but strangely, I can run enterprise
manager if logged on as the local administrator. I can also run SQL Server
Enterprise Manager.msc if I rename it to anything else, and it seems to work
all right.
Shall I just carry on using the new SQL Server Enterprise Manager 2? It
seems like a very odd issue.
Thanks in advance.
RyanRyan,
Can you rename it to SQLEM.msc? Does that work? Then just create a
shortcut on your desktop or Start Menu, and all should be well.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Ryan Breakspear wrote:
> Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be becau
se
> the files does not exist, is not an MMC console, or was created by a later
> version of MMC. This may also be because you do not have sufficied access
> rights to the file.
> ...when trying to run Enterprise Manager. I have tried re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run enterprise
> manager if logged on as the local administrator. I can also run SQL Serve
r
> Enterprise Manager.msc if I rename it to anything else, and it seems to wo
rk
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2? It
> seems like a very odd issue.
> Thanks in advance.
> Ryan
>|||Yep, I can rename it to anything. I can run it fine renamed as something
else, I just wondered why the problem, and if there was a solution.
Thanks for your reply.
Ryan
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:edplxoLcEHA.1248@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Ryan,
> Can you rename it to SQLEM.msc? Does that work? Then just create a
> shortcut on your desktop or Start Menu, and all should be well.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Ryan Breakspear wrote:
because[vbcol=seagreen]
later[vbcol=seagreen]
access[vbcol=seagreen]
the[vbcol=seagreen]
enterprise[vbcol=seagreen]
Server[vbcol=seagreen]
work[vbcol=seagreen]|||I have the exact same settings, and the exact same problem. Wish I had
found this workaround before re-installing everything... Still would
like to know what is causing this though...
Cheers - Craig
Ryan Breakspear wrote:
> *Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting
> the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
> because
> the files does not exist, is not an MMC console, or was created by a
> later
> version of MMC. This may also be because you do not have sufficied
> access
> rights to the file.
> ....when trying to run Enterprise Manager. I have tried
> re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run
> enterprise
> manager if logged on as the local administrator. I can also run SQL
> Server
> Enterprise Manager.msc if I rename it to anything else, and it seems
> to work
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2?
> It
> seems like a very odd issue.
> Thanks in advance.
> Ryan *
cjeff
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message888314.html|||I have been trying to fix this problem for some time. The fact that it
worked for you when you renamed it tipped me off to the source of the
problem. There is a cached version of the MMC file in the C:\Documents and
Settings\<username>\Application Data\Microsoft\MMC folder.
The problem is that on my system that cached file was corrupted.
Once I deleted the cached file, I was able to open SQL EntMgr with no proble
m.
"cjeff" wrote:
> I have the exact same settings, and the exact same problem. Wish I had
> found this workaround before re-installing everything... Still would
> like to know what is causing this though...
> Cheers - Craig
> Ryan Breakspear wrote:
>
> --
> cjeff
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message888314.html
>
Wednesday, March 21, 2012
MMC Can't open SQL Server Enterprise Manager.msc
Hi All,
I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
error:
MMC cannot open the file c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
the files does not exist, is not an MMC console, or was created by a later
version of MMC. This may also be because you do not have sufficied access
rights to the file.
...when trying to run Enterprise Manager. I have tried re-installing the
server and client tools, and SP3a, but still the same error.
I have administrator access to the PC, but strangely, I can run enterprise
manager if logged on as the local administrator. I can also run SQL Server
Enterprise Manager.msc if I rename it to anything else, and it seems to work
all right.
Shall I just carry on using the new SQL Server Enterprise Manager 2? It
seems like a very odd issue.
Thanks in advance.
Ryan
Ryan,
Can you rename it to SQLEM.msc? Does that work? Then just create a
shortcut on your desktop or Start Menu, and all should be well.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Ryan Breakspear wrote:
> Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
> the files does not exist, is not an MMC console, or was created by a later
> version of MMC. This may also be because you do not have sufficied access
> rights to the file.
> ...when trying to run Enterprise Manager. I have tried re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run enterprise
> manager if logged on as the local administrator. I can also run SQL Server
> Enterprise Manager.msc if I rename it to anything else, and it seems to work
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2? It
> seems like a very odd issue.
> Thanks in advance.
> Ryan
>
|||Yep, I can rename it to anything. I can run it fine renamed as something
else, I just wondered why the problem, and if there was a solution.
Thanks for your reply.
Ryan
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:edplxoLcEHA.1248@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Ryan,
> Can you rename it to SQLEM.msc? Does that work? Then just create a
> shortcut on your desktop or Start Menu, and all should be well.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Ryan Breakspear wrote:
because[vbcol=seagreen]
later[vbcol=seagreen]
access[vbcol=seagreen]
the[vbcol=seagreen]
enterprise[vbcol=seagreen]
Server[vbcol=seagreen]
work[vbcol=seagreen]
|||I have the exact same settings, and the exact same problem. Wish I had found this workaround before re-installing everything... Still would like to know what is causing this though...
Cheers - Craig
Originally posted by Ryan Breakspear
Hi All,
I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
error:
MMC cannot open the file c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
the files does not exist, is not an MMC console, or was created by a later
version of MMC. This may also be because you do not have sufficied access
rights to the file.
....when trying to run Enterprise Manager. I have tried re-installing the
server and client tools, and SP3a, but still the same error.
I have administrator access to the PC, but strangely, I can run enterprise
manager if logged on as the local administrator. I can also run SQL Server
Enterprise Manager.msc if I rename it to anything else, and it seems to work
all right.
Shall I just carry on using the new SQL Server Enterprise Manager 2? It
seems like a very odd issue.
Thanks in advance.
Ryan
worked for you when you renamed it tipped me off to the source of the
problem. There is a cached version of the MMC file in the C:\Documents and
Settings\<username>\Application Data\Microsoft\MMC folder.
The problem is that on my system that cached file was corrupted.
Once I deleted the cached file, I was able to open SQL EntMgr with no problem.
"cjeff" wrote:
> I have the exact same settings, and the exact same problem. Wish I had
> found this workaround before re-installing everything... Still would
> like to know what is causing this though...
> Cheers - Craig
> Ryan Breakspear wrote:
>
> --
> cjeff
> Posted via http://www.mcse.ms
> View this thread: http://www.mcse.ms/message888314.html
>
I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
error:
MMC cannot open the file c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
the files does not exist, is not an MMC console, or was created by a later
version of MMC. This may also be because you do not have sufficied access
rights to the file.
...when trying to run Enterprise Manager. I have tried re-installing the
server and client tools, and SP3a, but still the same error.
I have administrator access to the PC, but strangely, I can run enterprise
manager if logged on as the local administrator. I can also run SQL Server
Enterprise Manager.msc if I rename it to anything else, and it seems to work
all right.
Shall I just carry on using the new SQL Server Enterprise Manager 2? It
seems like a very odd issue.
Thanks in advance.
Ryan
Ryan,
Can you rename it to SQLEM.msc? Does that work? Then just create a
shortcut on your desktop or Start Menu, and all should be well.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Ryan Breakspear wrote:
> Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
> the files does not exist, is not an MMC console, or was created by a later
> version of MMC. This may also be because you do not have sufficied access
> rights to the file.
> ...when trying to run Enterprise Manager. I have tried re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run enterprise
> manager if logged on as the local administrator. I can also run SQL Server
> Enterprise Manager.msc if I rename it to anything else, and it seems to work
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2? It
> seems like a very odd issue.
> Thanks in advance.
> Ryan
>
|||Yep, I can rename it to anything. I can run it fine renamed as something
else, I just wondered why the problem, and if there was a solution.
Thanks for your reply.
Ryan
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:edplxoLcEHA.1248@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Ryan,
> Can you rename it to SQLEM.msc? Does that work? Then just create a
> shortcut on your desktop or Start Menu, and all should be well.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Ryan Breakspear wrote:
because[vbcol=seagreen]
later[vbcol=seagreen]
access[vbcol=seagreen]
the[vbcol=seagreen]
enterprise[vbcol=seagreen]
Server[vbcol=seagreen]
work[vbcol=seagreen]
|||I have the exact same settings, and the exact same problem. Wish I had found this workaround before re-installing everything... Still would like to know what is causing this though...
Cheers - Craig
Quote:
Hi All,
I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
error:
MMC cannot open the file c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
the files does not exist, is not an MMC console, or was created by a later
version of MMC. This may also be because you do not have sufficied access
rights to the file.
....when trying to run Enterprise Manager. I have tried re-installing the
server and client tools, and SP3a, but still the same error.
I have administrator access to the PC, but strangely, I can run enterprise
manager if logged on as the local administrator. I can also run SQL Server
Enterprise Manager.msc if I rename it to anything else, and it seems to work
all right.
Shall I just carry on using the new SQL Server Enterprise Manager 2? It
seems like a very odd issue.
Thanks in advance.
Ryan
worked for you when you renamed it tipped me off to the source of the
problem. There is a cached version of the MMC file in the C:\Documents and
Settings\<username>\Application Data\Microsoft\MMC folder.
The problem is that on my system that cached file was corrupted.
Once I deleted the cached file, I was able to open SQL EntMgr with no problem.
"cjeff" wrote:
> I have the exact same settings, and the exact same problem. Wish I had
> found this workaround before re-installing everything... Still would
> like to know what is causing this though...
> Cheers - Craig
> Ryan Breakspear wrote:
>
> --
> cjeff
> Posted via http://www.mcse.ms
> View this thread: http://www.mcse.ms/message888314.html
>
MMC Can't open SQL Server Enterprise Manager.msc
Hi All,
I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
error:
MMC cannot open the file c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
the files does not exist, is not an MMC console, or was created by a later
version of MMC. This may also be because you do not have sufficied access
rights to the file.
...when trying to run Enterprise Manager. I have tried re-installing the
server and client tools, and SP3a, but still the same error.
I have administrator access to the PC, but strangely, I can run enterprise
manager if logged on as the local administrator. I can also run SQL Server
Enterprise Manager.msc if I rename it to anything else, and it seems to work
all right.
Shall I just carry on using the new SQL Server Enterprise Manager 2? It
seems like a very odd issue.
Thanks in advance.
RyanRyan,
Can you rename it to SQLEM.msc? Does that work? Then just create a
shortcut on your desktop or Start Menu, and all should be well.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Ryan Breakspear wrote:
> Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
> the files does not exist, is not an MMC console, or was created by a later
> version of MMC. This may also be because you do not have sufficied access
> rights to the file.
> ...when trying to run Enterprise Manager. I have tried re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run enterprise
> manager if logged on as the local administrator. I can also run SQL Server
> Enterprise Manager.msc if I rename it to anything else, and it seems to work
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2? It
> seems like a very odd issue.
> Thanks in advance.
> Ryan
>|||Yep, I can rename it to anything. I can run it fine renamed as something
else, I just wondered why the problem, and if there was a solution.
Thanks for your reply.
Ryan
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:edplxoLcEHA.1248@.TK2MSFTNGP11.phx.gbl...
> Ryan,
> Can you rename it to SQLEM.msc? Does that work? Then just create a
> shortcut on your desktop or Start Menu, and all should be well.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Ryan Breakspear wrote:
> > Hi All,
> >
> > I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
> > error:
> >
> > MMC cannot open the file c:\Program Files\Microsoft SQL
> > Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
because
> > the files does not exist, is not an MMC console, or was created by a
later
> > version of MMC. This may also be because you do not have sufficied
access
> > rights to the file.
> >
> > ...when trying to run Enterprise Manager. I have tried re-installing
the
> > server and client tools, and SP3a, but still the same error.
> >
> > I have administrator access to the PC, but strangely, I can run
enterprise
> > manager if logged on as the local administrator. I can also run SQL
Server
> > Enterprise Manager.msc if I rename it to anything else, and it seems to
work
> > all right.
> >
> > Shall I just carry on using the new SQL Server Enterprise Manager 2? It
> > seems like a very odd issue.
> >
> > Thanks in advance.
> >
> > Ryan
> >
> >|||I have the exact same settings, and the exact same problem. Wish I had
found this workaround before re-installing everything... Still would
like to know what is causing this though...
Cheers - Craig
Ryan Breakspear wrote:
> *Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting
> the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
> because
> the files does not exist, is not an MMC console, or was created by a
> later
> version of MMC. This may also be because you do not have sufficied
> access
> rights to the file.
> ....when trying to run Enterprise Manager. I have tried
> re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run
> enterprise
> manager if logged on as the local administrator. I can also run SQL
> Server
> Enterprise Manager.msc if I rename it to anything else, and it seems
> to work
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2?
> It
> seems like a very odd issue.
> Thanks in advance.
> Ryan *
cjeff
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message888314.html|||I have been trying to fix this problem for some time. The fact that it
worked for you when you renamed it tipped me off to the source of the
problem. There is a cached version of the MMC file in the C:\Documents and
Settings\<username>\Application Data\Microsoft\MMC folder.
The problem is that on my system that cached file was corrupted.
Once I deleted the cached file, I was able to open SQL EntMgr with no problem.
"cjeff" wrote:
> I have the exact same settings, and the exact same problem. Wish I had
> found this workaround before re-installing everything... Still would
> like to know what is causing this though...
> Cheers - Craig
> Ryan Breakspear wrote:
> > *Hi All,
> >
> > I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting
> > the
> > error:
> >
> > MMC cannot open the file c:\Program Files\Microsoft SQL
> > Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
> > because
> > the files does not exist, is not an MMC console, or was created by a
> > later
> > version of MMC. This may also be because you do not have sufficied
> > access
> > rights to the file.
> >
> > ....when trying to run Enterprise Manager. I have tried
> > re-installing the
> > server and client tools, and SP3a, but still the same error.
> >
> > I have administrator access to the PC, but strangely, I can run
> > enterprise
> > manager if logged on as the local administrator. I can also run SQL
> > Server
> > Enterprise Manager.msc if I rename it to anything else, and it seems
> > to work
> > all right.
> >
> > Shall I just carry on using the new SQL Server Enterprise Manager 2?
> > It
> > seems like a very odd issue.
> >
> > Thanks in advance.
> >
> > Ryan *
>
> --
> cjeff
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message888314.html
>
I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
error:
MMC cannot open the file c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
the files does not exist, is not an MMC console, or was created by a later
version of MMC. This may also be because you do not have sufficied access
rights to the file.
...when trying to run Enterprise Manager. I have tried re-installing the
server and client tools, and SP3a, but still the same error.
I have administrator access to the PC, but strangely, I can run enterprise
manager if logged on as the local administrator. I can also run SQL Server
Enterprise Manager.msc if I rename it to anything else, and it seems to work
all right.
Shall I just carry on using the new SQL Server Enterprise Manager 2? It
seems like a very odd issue.
Thanks in advance.
RyanRyan,
Can you rename it to SQLEM.msc? Does that work? Then just create a
shortcut on your desktop or Start Menu, and all should be well.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Ryan Breakspear wrote:
> Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
> the files does not exist, is not an MMC console, or was created by a later
> version of MMC. This may also be because you do not have sufficied access
> rights to the file.
> ...when trying to run Enterprise Manager. I have tried re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run enterprise
> manager if logged on as the local administrator. I can also run SQL Server
> Enterprise Manager.msc if I rename it to anything else, and it seems to work
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2? It
> seems like a very odd issue.
> Thanks in advance.
> Ryan
>|||Yep, I can rename it to anything. I can run it fine renamed as something
else, I just wondered why the problem, and if there was a solution.
Thanks for your reply.
Ryan
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:edplxoLcEHA.1248@.TK2MSFTNGP11.phx.gbl...
> Ryan,
> Can you rename it to SQLEM.msc? Does that work? Then just create a
> shortcut on your desktop or Start Menu, and all should be well.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Ryan Breakspear wrote:
> > Hi All,
> >
> > I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
> > error:
> >
> > MMC cannot open the file c:\Program Files\Microsoft SQL
> > Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
because
> > the files does not exist, is not an MMC console, or was created by a
later
> > version of MMC. This may also be because you do not have sufficied
access
> > rights to the file.
> >
> > ...when trying to run Enterprise Manager. I have tried re-installing
the
> > server and client tools, and SP3a, but still the same error.
> >
> > I have administrator access to the PC, but strangely, I can run
enterprise
> > manager if logged on as the local administrator. I can also run SQL
Server
> > Enterprise Manager.msc if I rename it to anything else, and it seems to
work
> > all right.
> >
> > Shall I just carry on using the new SQL Server Enterprise Manager 2? It
> > seems like a very odd issue.
> >
> > Thanks in advance.
> >
> > Ryan
> >
> >|||I have the exact same settings, and the exact same problem. Wish I had
found this workaround before re-installing everything... Still would
like to know what is causing this though...
Cheers - Craig
Ryan Breakspear wrote:
> *Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting
> the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
> because
> the files does not exist, is not an MMC console, or was created by a
> later
> version of MMC. This may also be because you do not have sufficied
> access
> rights to the file.
> ....when trying to run Enterprise Manager. I have tried
> re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run
> enterprise
> manager if logged on as the local administrator. I can also run SQL
> Server
> Enterprise Manager.msc if I rename it to anything else, and it seems
> to work
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2?
> It
> seems like a very odd issue.
> Thanks in advance.
> Ryan *
cjeff
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message888314.html|||I have been trying to fix this problem for some time. The fact that it
worked for you when you renamed it tipped me off to the source of the
problem. There is a cached version of the MMC file in the C:\Documents and
Settings\<username>\Application Data\Microsoft\MMC folder.
The problem is that on my system that cached file was corrupted.
Once I deleted the cached file, I was able to open SQL EntMgr with no problem.
"cjeff" wrote:
> I have the exact same settings, and the exact same problem. Wish I had
> found this workaround before re-installing everything... Still would
> like to know what is causing this though...
> Cheers - Craig
> Ryan Breakspear wrote:
> > *Hi All,
> >
> > I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting
> > the
> > error:
> >
> > MMC cannot open the file c:\Program Files\Microsoft SQL
> > Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
> > because
> > the files does not exist, is not an MMC console, or was created by a
> > later
> > version of MMC. This may also be because you do not have sufficied
> > access
> > rights to the file.
> >
> > ....when trying to run Enterprise Manager. I have tried
> > re-installing the
> > server and client tools, and SP3a, but still the same error.
> >
> > I have administrator access to the PC, but strangely, I can run
> > enterprise
> > manager if logged on as the local administrator. I can also run SQL
> > Server
> > Enterprise Manager.msc if I rename it to anything else, and it seems
> > to work
> > all right.
> >
> > Shall I just carry on using the new SQL Server Enterprise Manager 2?
> > It
> > seems like a very odd issue.
> >
> > Thanks in advance.
> >
> > Ryan *
>
> --
> cjeff
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message888314.html
>
mixed mode does not work
I have recently set the security mode to Mixed mode for SQL2005 running on
Win XP Pro SP-2. I want to be able to access the database from other
machines using the sa password. This I can do but I am no longer able to
use the WinNT authen. for local access. What gives?
ThanksLarry - I have only seen this when the user's windows password has
expiredbut they are still logged on in windows and try to access sql
server - any chance this is the case?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||I don't think that is it. But you may be on the right track. I often use a
cached profile, I.e. I am not connected to my domain but still use a Domain
login. If that is the case, SQL server would not be able to validate my
authentication while I am not connected to the server. Of course, I can
test this when I am in the office or possible while I have a VPN open to the
Domain server.
Thanks,
Larry
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ODg6C67OHHA.4172@.TK2MSFTNGP03.phx.gbl...
> Larry - I have only seen this when the user's windows password has
> expiredbut they are still logged on in windows and try to access sql
> server - any chance this is the case?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
Win XP Pro SP-2. I want to be able to access the database from other
machines using the sa password. This I can do but I am no longer able to
use the WinNT authen. for local access. What gives?
ThanksLarry - I have only seen this when the user's windows password has
expiredbut they are still logged on in windows and try to access sql
server - any chance this is the case?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||I don't think that is it. But you may be on the right track. I often use a
cached profile, I.e. I am not connected to my domain but still use a Domain
login. If that is the case, SQL server would not be able to validate my
authentication while I am not connected to the server. Of course, I can
test this when I am in the office or possible while I have a VPN open to the
Domain server.
Thanks,
Larry
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ODg6C67OHHA.4172@.TK2MSFTNGP03.phx.gbl...
> Larry - I have only seen this when the user's windows password has
> expiredbut they are still logged on in windows and try to access sql
> server - any chance this is the case?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
mixed mode does not work
I have recently set the security mode to Mixed mode for SQL2005 running on
Win XP Pro SP-2. I want to be able to access the database from other
machines using the sa password. This I can do but I am no longer able to
use the WinNT authen. for local access. What gives?
ThanksLarry - I have only seen this when the user's windows password has
expiredbut they are still logged on in windows and try to access sql
server - any chance this is the case?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||I don't think that is it. But you may be on the right track. I often use a
cached profile, I.e. I am not connected to my domain but still use a Domain
login. If that is the case, SQL server would not be able to validate my
authentication while I am not connected to the server. Of course, I can
test this when I am in the office or possible while I have a VPN open to the
Domain server.
Thanks,
Larry
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ODg6C67OHHA.4172@.TK2MSFTNGP03.phx.gbl...
> Larry - I have only seen this when the user's windows password has
> expiredbut they are still logged on in windows and try to access sql
> server - any chance this is the case?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
Win XP Pro SP-2. I want to be able to access the database from other
machines using the sa password. This I can do but I am no longer able to
use the WinNT authen. for local access. What gives?
ThanksLarry - I have only seen this when the user's windows password has
expiredbut they are still logged on in windows and try to access sql
server - any chance this is the case?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||I don't think that is it. But you may be on the right track. I often use a
cached profile, I.e. I am not connected to my domain but still use a Domain
login. If that is the case, SQL server would not be able to validate my
authentication while I am not connected to the server. Of course, I can
test this when I am in the office or possible while I have a VPN open to the
Domain server.
Thanks,
Larry
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ODg6C67OHHA.4172@.TK2MSFTNGP03.phx.gbl...
> Larry - I have only seen this when the user's windows password has
> expiredbut they are still logged on in windows and try to access sql
> server - any chance this is the case?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
mixed mode does not work
I have recently set the security mode to Mixed mode for SQL2005 running on
Win XP Pro SP-2. I want to be able to access the database from other
machines using the sa password. This I can do but I am no longer able to
use the WinNT authen. for local access. What gives?
Thanks
Larry - I have only seen this when the user's windows password has
expiredbut they are still logged on in windows and try to access sql
server - any chance this is the case?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||I don't think that is it. But you may be on the right track. I often use a
cached profile, I.e. I am not connected to my domain but still use a Domain
login. If that is the case, SQL server would not be able to validate my
authentication while I am not connected to the server. Of course, I can
test this when I am in the office or possible while I have a VPN open to the
Domain server.
Thanks,
Larry
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ODg6C67OHHA.4172@.TK2MSFTNGP03.phx.gbl...
> Larry - I have only seen this when the user's windows password has
> expiredbut they are still logged on in windows and try to access sql
> server - any chance this is the case?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
Win XP Pro SP-2. I want to be able to access the database from other
machines using the sa password. This I can do but I am no longer able to
use the WinNT authen. for local access. What gives?
Thanks
Larry - I have only seen this when the user's windows password has
expiredbut they are still logged on in windows and try to access sql
server - any chance this is the case?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||I don't think that is it. But you may be on the right track. I often use a
cached profile, I.e. I am not connected to my domain but still use a Domain
login. If that is the case, SQL server would not be able to validate my
authentication while I am not connected to the server. Of course, I can
test this when I am in the office or possible while I have a VPN open to the
Domain server.
Thanks,
Larry
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ODg6C67OHHA.4172@.TK2MSFTNGP03.phx.gbl...
> Larry - I have only seen this when the user's windows password has
> expiredbut they are still logged on in windows and try to access sql
> server - any chance this is the case?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
Monday, February 20, 2012
Missing DLL during installation - reposted from SQL Express forum
XP PRO SP2
I downloaded and installed SQL Server 2005 Express with Advanced Services (9.0.3042.0). The installation appeared to complete successfully and I looked at various options of Management Studio. After exiting, rebooting, and restarting Management Studio, I got the message, (paraphrased) Management Studio failed to initiate - terminating. After using Add/Remove to remove all installed components, I reran the installation. I got two error messages indicating that xpstar90.dll is missing. Did not see these messages during the first install.
Log SQL0003_mycomputername_SQL contains these errors:
Error Code: 17750
MSI (s) (94!58) [18:24:53:031]: Product: Microsoft SQL Server 2005 -- Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Could not load the DLL xpstar90.dll, or one of the DLLs it references. Reason: 2(The system cannot find the file specified.).. Refer to the server error logs and Setup logs for detailed error information.
Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Could not load the DLL xpstar90.dll, or one of the DLLs it references. Reason: 2(The system cannot find the file specified.).. Refer to the server error logs and Setup logs for detailed error information.
SQL_ERROR (-1) in OdbcStatement::execute_batch
sqlstate=42000, level=16, state=1, native_error=17750, msg=[Microsoft][SQL Native Client][SQL Server]Could not load the DLL xpstar90.dll, or one of the DLLs it references. Reason: 2(The system cannot find the file specified.).
sqlstate=42000, level=16, state=1, native_error=14658, msg=[Microsoft][SQL Native Client][SQL Server]Failed to retrieve SQLPath for syssubsystems population.
Error Code: 0x80074556 (17750)
Windows Error Text: Source File Name: lib\odbc_statement.h
Compiler Timestamp: Wed Jun 14 16:28:15 2006
Function Name: OdbcStatement::execute_batch@.sysdbupg.sql@.113
Source Line Number: 91
Log SQL0003_mycomputername_Core reported:
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 17750
Aborting queue processing as nested installer has completed
Message pump returning: 17750
Log SQL003_mycomputername_Core(Local) reported:
Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchMSDE2000" failed due to a precondition.
Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run:
Action: "UninstallForSQLAction" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchLibertySql" failed due to a precondition.
Skipped: UninstallForRS2000Action
Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis:
Action: "UninstallForRS2000Action" will be skipped due to the following condition:
Condition "Action: InstallRSAction was skipped." returned true.
Error: Action "ExposeVistaClusteredResources" failed during execution. Error information reported during run:
Action: "ExposeVistaClusteredResources" will be marked as failed due to the following condition:
Condition "The Clustered SQL Server instance that hosts is installed." returned false.
Running: ReportChainingResults at: 2007/8/11 18:27:5
Error: Action "ReportChainingResults" threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 17750
Error Code: 0x80074556 (17750)
Windows Error Text: Source File Name: sqlchaining\sqlchainingactions.cpp
Compiler Timestamp: Thu Nov 16 20:31:57 2006
Function Name: sqls::ReportChainingResults:erform
Source Line Number: 3521
- Context --
sqls::HostSetupPackageInstallerSynch
stCommit
sqls::HighlyAvailablePackage:reInstall
led due to cancel code received from cancel source: 29539
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_DCHJL761_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0003.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2007/8/11 18:29:5
Message pump returning: 17750
No other log contained a related error message.
A third attempt to install resulted in a Failure to create database files.
Hi,
Sql Server 205 Express SP2 will NOT Install, the datbase services section fails -> Can not start service. I believe a previous botched installation and registry settings are preventing a sucessfull re-install. I have not found a solution yet. The machine is WIndows XP SP2.
I am getting almost the same error in the logs.
Running: ReportChainingResults at: 2007/8/13 19:25:44
Error: Action "ReportChainingResults" threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 3
Error Code: 0x80070003 (3)
Windows Error Text: The system cannot find the path specified.
Source File Name: sqlchaining\sqlchainingactions.cpp
Compiler Timestamp: Thu Nov 16 20:31:57 2006
Function Name: sqls::ReportChainingResults:
erform
Source Line Number: 3521
- Context --
sqls::HostSetupPackageInstallerSynch:ostCommit
sqls::HighlyAvailablePackage:reInstall
led due to cancel code received from cancel source: 29539
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_IBM-D5CDBD4C907_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0002.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2007/8/13 19:28:42
Message pump returning: 3
Actually, there was a error message box that flashed at some point. After finally trapping it so the message could be read, It said something about the .NET 2.0 components being corrupt ot not installed.
Removing the .NET 2.0 Framework and all SqlServer components, rebooting and then re-installing fixed the issue!
Missing DLL during installation - reposted from SQL Express forum
XP PRO SP2
I downloaded and installed SQL Server 2005 Express with Advanced Services (9.0.3042.0). The installation appeared to complete successfully and I looked at various options of Management Studio. After exiting, rebooting, and restarting Management Studio, I got the message, (paraphrased) Management Studio failed to initiate - terminating. After using Add/Remove to remove all installed components, I reran the installation. I got two error messages indicating that xpstar90.dll is missing. Did not see these messages during the first install.
Log SQL0003_mycomputername_SQL contains these errors:
Error Code: 17750
MSI (s) (94!58) [18:24:53:031]: Product: Microsoft SQL Server 2005 -- Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Could not load the DLL xpstar90.dll, or one of the DLLs it references. Reason: 2(The system cannot find the file specified.).. Refer to the server error logs and Setup logs for detailed error information.
Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Could not load the DLL xpstar90.dll, or one of the DLLs it references. Reason: 2(The system cannot find the file specified.).. Refer to the server error logs and Setup logs for detailed error information.
SQL_ERROR (-1) in OdbcStatement::execute_batch
sqlstate=42000, level=16, state=1, native_error=17750, msg=[Microsoft][SQL Native Client][SQL Server]Could not load the DLL xpstar90.dll, or one of the DLLs it references. Reason: 2(The system cannot find the file specified.).
sqlstate=42000, level=16, state=1, native_error=14658, msg=[Microsoft][SQL Native Client][SQL Server]Failed to retrieve SQLPath for syssubsystems population.
Error Code: 0x80074556 (17750)
Windows Error Text: Source File Name: lib\odbc_statement.h
Compiler Timestamp: Wed Jun 14 16:28:15 2006
Function Name: OdbcStatement::execute_batch@.sysdbupg.sql@.113
Source Line Number: 91
Log SQL0003_mycomputername_Core reported:
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 17750
Aborting queue processing as nested installer has completed
Message pump returning: 17750
Log SQL003_mycomputername_Core(Local) reported:
Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchMSDE2000" failed due to a precondition.
Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run:
Action: "UninstallForSQLAction" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchLibertySql" failed due to a precondition.
Skipped: UninstallForRS2000Action
Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis:
Action: "UninstallForRS2000Action" will be skipped due to the following condition:
Condition "Action: InstallRSAction was skipped." returned true.
Error: Action "ExposeVistaClusteredResources" failed during execution. Error information reported during run:
Action: "ExposeVistaClusteredResources" will be marked as failed due to the following condition:
Condition "The Clustered SQL Server instance that hosts is installed." returned false.
Running: ReportChainingResults at: 2007/8/11 18:27:5
Error: Action "ReportChainingResults" threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 17750
Error Code: 0x80074556 (17750)
Windows Error Text: Source File Name: sqlchaining\sqlchainingactions.cpp
Compiler Timestamp: Thu Nov 16 20:31:57 2006
Function Name: sqls::ReportChainingResults:erform
Source Line Number: 3521
- Context --
sqls::HostSetupPackageInstallerSynchstCommit
sqls::HighlyAvailablePackage:reInstall
led due to cancel code received from cancel source: 29539
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_DCHJL761_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0003.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2007/8/11 18:29:5
Message pump returning: 17750
No other log contained a related error message.
A third attempt to install resulted in a Failure to create database files.
Hi,
Sql Server 205 Express SP2 will NOT Install, the datbase services section fails -> Can not start service. I believe a previous botched installation and registry settings are preventing a sucessfull re-install. I have not found a solution yet. The machine is WIndows XP SP2.
I am getting almost the same error in the logs.
Running: ReportChainingResults at: 2007/8/13 19:25:44
Error: Action "ReportChainingResults" threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 3
Error Code: 0x80070003 (3)
Windows Error Text: The system cannot find the path specified.
Source File Name: sqlchaining\sqlchainingactions.cpp
Compiler Timestamp: Thu Nov 16 20:31:57 2006
Function Name: sqls::ReportChainingResults:erform
Source Line Number: 3521
- Context --
sqls::HostSetupPackageInstallerSynch:ostCommit
sqls::HighlyAvailablePackage:reInstall
led due to cancel code received from cancel source: 29539
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_IBM-D5CDBD4C907_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0002.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2007/8/13 19:28:42
Message pump returning: 3
Actually, there was a error message box that flashed at some point. After finally trapping it so the message could be read, It said something about the .NET 2.0 components being corrupt ot not installed.
Removing the .NET 2.0 Framework and all SqlServer components, rebooting and then re-installing fixed the issue!
Missing DLL during installation - reposted from SQL Express forum
XP PRO SP2
I downloaded and installed SQL Server 2005 Express with Advanced Services (9.0.3042.0). The installation appeared to complete successfully and I looked at various options of Management Studio. After exiting, rebooting, and restarting Management Studio, I got the message, (paraphrased) Management Studio failed to initiate - terminating. After using Add/Remove to remove all installed components, I reran the installation. I got two error messages indicating that xpstar90.dll is missing. Did not see these messages during the first install.
Log SQL0003_mycomputername_SQL contains these errors:
Error Code: 17750
MSI (s) (94!58) [18:24:53:031]: Product: Microsoft SQL Server 2005 -- Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Could not load the DLL xpstar90.dll, or one of the DLLs it references. Reason: 2(The system cannot find the file specified.).. Refer to the server error logs and Setup logs for detailed error information.
Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Could not load the DLL xpstar90.dll, or one of the DLLs it references. Reason: 2(The system cannot find the file specified.).. Refer to the server error logs and Setup logs for detailed error information.
SQL_ERROR (-1) in OdbcStatement::execute_batch
sqlstate=42000, level=16, state=1, native_error=17750, msg=[Microsoft][SQL Native Client][SQL Server]Could not load the DLL xpstar90.dll, or one of the DLLs it references. Reason: 2(The system cannot find the file specified.).
sqlstate=42000, level=16, state=1, native_error=14658, msg=[Microsoft][SQL Native Client][SQL Server]Failed to retrieve SQLPath for syssubsystems population.
Error Code: 0x80074556 (17750)
Windows Error Text: Source File Name: lib\odbc_statement.h
Compiler Timestamp: Wed Jun 14 16:28:15 2006
Function Name: OdbcStatement::execute_batch@.sysdbupg.sql@.113
Source Line Number: 91
Log SQL0003_mycomputername_Core reported:
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 17750
Aborting queue processing as nested installer has completed
Message pump returning: 17750
Log SQL003_mycomputername_Core(Local) reported:
Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchMSDE2000" failed due to a precondition.
Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run:
Action: "UninstallForSQLAction" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchLibertySql" failed due to a precondition.
Skipped: UninstallForRS2000Action
Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis:
Action: "UninstallForRS2000Action" will be skipped due to the following condition:
Condition "Action: InstallRSAction was skipped." returned true.
Error: Action "ExposeVistaClusteredResources" failed during execution. Error information reported during run:
Action: "ExposeVistaClusteredResources" will be marked as failed due to the following condition:
Condition "The Clustered SQL Server instance that hosts is installed." returned false.
Running: ReportChainingResults at: 2007/8/11 18:27:5
Error: Action "ReportChainingResults" threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 17750
Error Code: 0x80074556 (17750)
Windows Error Text: Source File Name: sqlchaining\sqlchainingactions.cpp
Compiler Timestamp: Thu Nov 16 20:31:57 2006
Function Name: sqls::ReportChainingResults:erform
Source Line Number: 3521
- Context --
sqls::HostSetupPackageInstallerSynchstCommit
sqls::HighlyAvailablePackage:reInstall
led due to cancel code received from cancel source: 29539
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_DCHJL761_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0003.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2007/8/11 18:29:5
Message pump returning: 17750
No other log contained a related error message.
A third attempt to install resulted in a Failure to create database files.
Hi,
Sql Server 205 Express SP2 will NOT Install, the datbase services section fails -> Can not start service. I believe a previous botched installation and registry settings are preventing a sucessfull re-install. I have not found a solution yet. The machine is WIndows XP SP2.
I am getting almost the same error in the logs.
Running: ReportChainingResults at: 2007/8/13 19:25:44
Error: Action "ReportChainingResults" threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 3
Error Code: 0x80070003 (3)
Windows Error Text: The system cannot find the path specified.
Source File Name: sqlchaining\sqlchainingactions.cpp
Compiler Timestamp: Thu Nov 16 20:31:57 2006
Function Name: sqls::ReportChainingResults:erform
Source Line Number: 3521
- Context --
sqls::HostSetupPackageInstallerSynch:ostCommit
sqls::HighlyAvailablePackage:reInstall
led due to cancel code received from cancel source: 29539
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_IBM-D5CDBD4C907_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0002.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2007/8/13 19:28:42
Message pump returning: 3
Actually, there was a error message box that flashed at some point. After finally trapping it so the message could be read, It said something about the .NET 2.0 components being corrupt ot not installed.
Removing the .NET 2.0 Framework and all SqlServer components, rebooting and then re-installing fixed the issue!
Missing DLL during installation
XP PRO SP2
I downloaded and installed SQL Server 2005 Express with Advanced Services (9.0.3042.0). The installation appeared to complete successfully and I looked at various options of Management Studio. After exiting, rebooting, and restarting Management Studio, I got the message, (paraphrased) Management Studio failed to initiate - terminating. After using Add/Remove to remove all installed components, I reran the installation. I got two error messages indicating that xpstar90.dll is missing. Did not see these messages during the first install.
Log SQL0003_mycomputername_SQL contains these errors:
Error Code: 17750
MSI (s) (94!58) [18:24:53:031]: Product: Microsoft SQL Server 2005 -- Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Could not load the DLL xpstar90.dll, or one of the DLLs it references. Reason: 2(The system cannot find the file specified.).. Refer to the server error logs and Setup logs for detailed error information.
Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Could not load the DLL xpstar90.dll, or one of the DLLs it references. Reason: 2(The system cannot find the file specified.).. Refer to the server error logs and Setup logs for detailed error information.
SQL_ERROR (-1) in OdbcStatement::execute_batch
sqlstate=42000, level=16, state=1, native_error=17750, msg=[Microsoft][SQL Native Client][SQL Server]Could not load the DLL xpstar90.dll, or one of the DLLs it references. Reason: 2(The system cannot find the file specified.).
sqlstate=42000, level=16, state=1, native_error=14658, msg=[Microsoft][SQL Native Client][SQL Server]Failed to retrieve SQLPath for syssubsystems population.
Error Code: 0x80074556 (17750)
Windows Error Text: Source File Name: lib\odbc_statement.h
Compiler Timestamp: Wed Jun 14 16:28:15 2006
Function Name: OdbcStatement::execute_batch@.sysdbupg.sql@.113
Source Line Number: 91
Log SQL0003_mycomputername_Core reported:
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 17750
Aborting queue processing as nested installer has completed
Message pump returning: 17750
Log SQL003_mycomputername_Core(Local) reported:
Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchMSDE2000" failed due to a precondition.
Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run:
Action: "UninstallForSQLAction" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchLibertySql" failed due to a precondition.
Skipped: UninstallForRS2000Action
Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis:
Action: "UninstallForRS2000Action" will be skipped due to the following condition:
Condition "Action: InstallRSAction was skipped." returned true.
Error: Action "ExposeVistaClusteredResources" failed during execution. Error information reported during run:
Action: "ExposeVistaClusteredResources" will be marked as failed due to the following condition:
Condition "The Clustered SQL Server instance that hosts is installed." returned false.
Running: ReportChainingResults at: 2007/8/11 18:27:5
Error: Action "ReportChainingResults" threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 17750
Error Code: 0x80074556 (17750)
Windows Error Text: Source File Name: sqlchaining\sqlchainingactions.cpp
Compiler Timestamp: Thu Nov 16 20:31:57 2006
Function Name: sqls::ReportChainingResults:erform
Source Line Number: 3521
- Context --
sqls::HostSetupPackageInstallerSynch:ostCommit
sqls::HighlyAvailablePackage:reInstall
led due to cancel code received from cancel source: 29539
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_DCHJL761_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0003.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2007/8/11 18:29:5
Message pump returning: 17750
No other log contained a related error message.
A third attempt to install resulted in a Failure to create database files.
I see that I should have posted this in the SQL Express Setup and Upgrade forum. I've reposted there.
Subscribe to:
Posts (Atom)