Need help urgently.
I have on win 2000 machine a default SQL Server (local) & a named SQL Server
instance (for separate web machine).
After installing the MS04-011 Patch last nite, the named SQL Server fails to
startup on reboot or manual. The default server on the other hand is runnin
g. But I cannot use the default server as it requires access within the loca
l machine only.
I tried uninstalling the patch, but it still cannot get the SQL server runni
ng again.
HOW CAN I RECOVER THE SQL Server Instance?
Additional info: On logon, following error massage:
"NtUninstall Q8877565\WinSys.cer" not found
before and after the uninstall of the patch.What error do you get when you start it? Is there anything in he SQL Server
errorlog when it fails?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thank Rand for responding.
The Error is simply Login Failed. Service Manager shows the instance is stop
ped, while the Default Instance (Local) is started. Click start, and return
Login Failure again.
Any idea what's wrong and how I may recover the Instance?
Almon|||Error listing end at the last restart after patch install. That is, never re
start again.
Almon
Showing posts with label local. Show all posts
Showing posts with label local. Show all posts
Friday, March 30, 2012
named server failed logon after installing MS04-011 patch
Need help urgently
I have on win 2000 machine a default SQL Server (local) & a named SQL Server instance (for separate web machine)
After installing the MS04-011 Patch last nite, the named SQL Server fails to startup on reboot or manual. The default server on the other hand is running. But I cannot use the default server as it requires access within the local machine only
I tried uninstalling the patch, but it still cannot get the SQL server running again.
HOW CAN I RECOVER THE SQL Server Instance'
Additional info: On logon, following error massage
"NtUninstall Q8877565\WinSys.cer" not foun
before and after the uninstall of the patch.What error do you get when you start it? Is there anything in he SQL Server
errorlog when it fails?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thank Rand for responding
The Error is simply Login Failed. Service Manager shows the instance is stopped, while the Default Instance (Local) is started. Click start, and return Login Failure again
Any idea what's wrong and how I may recover the Instance
Almo|||Error listing end at the last restart after patch install. That is, never restart again
Almo
I have on win 2000 machine a default SQL Server (local) & a named SQL Server instance (for separate web machine)
After installing the MS04-011 Patch last nite, the named SQL Server fails to startup on reboot or manual. The default server on the other hand is running. But I cannot use the default server as it requires access within the local machine only
I tried uninstalling the patch, but it still cannot get the SQL server running again.
HOW CAN I RECOVER THE SQL Server Instance'
Additional info: On logon, following error massage
"NtUninstall Q8877565\WinSys.cer" not foun
before and after the uninstall of the patch.What error do you get when you start it? Is there anything in he SQL Server
errorlog when it fails?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thank Rand for responding
The Error is simply Login Failed. Service Manager shows the instance is stopped, while the Default Instance (Local) is started. Click start, and return Login Failure again
Any idea what's wrong and how I may recover the Instance
Almo|||Error listing end at the last restart after patch install. That is, never restart again
Almo
named server failed logon after installing MS04-011 patch
Need help urgently.
I have on win 2000 machine a default SQL Server (local) & a named SQL Server instance (for separate web machine).
After installing the MS04-011 Patch last nite, the named SQL Server fails to startup on reboot or manual. The default server on the other hand is running. But I cannot use the default server as it requires access within the local machine only.
I tried uninstalling the patch, but it still cannot get the SQL server running again.
HOW CAN I RECOVER THE SQL Server Instance?
Additional info: On logon, following error massage:
"NtUninstall Q8877565\WinSys.cer" not found
before and after the uninstall of the patch.
What error do you get when you start it? Is there anything in he SQL Server
errorlog when it fails?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thank Rand for responding.
The Error is simply Login Failed. Service Manager shows the instance is stopped, while the Default Instance (Local) is started. Click start, and return Login Failure again.
Any idea what's wrong and how I may recover the Instance?
Almon
|||Error listing end at the last restart after patch install. That is, never restart again.
Almon
sql
I have on win 2000 machine a default SQL Server (local) & a named SQL Server instance (for separate web machine).
After installing the MS04-011 Patch last nite, the named SQL Server fails to startup on reboot or manual. The default server on the other hand is running. But I cannot use the default server as it requires access within the local machine only.
I tried uninstalling the patch, but it still cannot get the SQL server running again.
HOW CAN I RECOVER THE SQL Server Instance?
Additional info: On logon, following error massage:
"NtUninstall Q8877565\WinSys.cer" not found
before and after the uninstall of the patch.
What error do you get when you start it? Is there anything in he SQL Server
errorlog when it fails?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thank Rand for responding.
The Error is simply Login Failed. Service Manager shows the instance is stopped, while the Default Instance (Local) is started. Click start, and return Login Failure again.
Any idea what's wrong and how I may recover the Instance?
Almon
|||Error listing end at the last restart after patch install. That is, never restart again.
Almon
sql
Wednesday, March 28, 2012
Named Pipers Provider, error 40, ok from local, error to remote - help
Hi.
I am new to sql server so please bear with me.
Here is the problem.
I am using VWD express to connect to a sql server 2005 db on my local
machine. The site and the sql server are local and everything is fine.
No problems.
I have a sql server hosting plan to host the db. (my local is SQL
Server 2005 and the hosted is Sql Server 2000).
I use the LOCAL VWD website to access the HOSTED sql server and it
connects with no problem. I changed data in the remote version of the
db as a double-check that I am accessing the remote db and not the
local db.
When I go ahead and upload the web site to my web host, different from
the sql host (long story), I get this error (provider: Named Pipes
Provider, error: 40 - Could not open a connection to SQL Server).
Any ideas why this error is happening. My web host verifies that my
connection string is fine, and that if I can connect with my local
machine then there should be no problem and the problems is on the
hosting end.
Thanks in advance,
RanginaldOk. Problem solved. I was using a web host with multiple hosted
domains and I think I probably had some kind of IIS app directrory
problem. I moved the site to its own hosting and all was fine with no
changes needed.
Thanks anyway. Hope this tidbit helps someone.
Rangy
Ranginald wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald|||Do you have to connect with named pipes? If not, change the connection string
to connect with TCP/IP (set Network Library=dbmssocn). Assuming that the SQL
connectivity components are properly installed on the web server and you can
ping the database server from the web server, I'd try a few things.
1. Find out the IP address and the TCP port that the SQL instance listens on.
2. Change the connection string to the IP address followed by a comma and
then the TCP port (e.g. set Server=169.12.35.51,5002). If this does not work,
you may have a problem with accessing the port. (if it's the default instance
using the default port, you don't need to test with the port number specified
explicitly).
3. Change the IP to the server name in the Server property of the connection
string, and try again. If this doesn't work, you may have a problem with
resolving the server to the IP address. Try the fully qualified domain name
instead.
If you can connect with TCP/IP, but not with names pipes, you may have a
problem with the ports used by the named pipes being blocked.
Linchi
"Ranginald" wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald
>|||How would I find out the TCP port that the SQL instance listens on?
Thanks
Linchi Shea wrote:
> Do you have to connect with named pipes? If not, change the connection string
> to connect with TCP/IP (set Network Library=dbmssocn). Assuming that the SQL
> connectivity components are properly installed on the web server and you can
> ping the database server from the web server, I'd try a few things.
> 1. Find out the IP address and the TCP port that the SQL instance listens on.
> 2. Change the connection string to the IP address followed by a comma and
> then the TCP port (e.g. set Server=169.12.35.51,5002). If this does not work,
> you may have a problem with accessing the port. (if it's the default instance
> using the default port, you don't need to test with the port number specified
> explicitly).
> 3. Change the IP to the server name in the Server property of the connection
> string, and try again. If this doesn't work, you may have a problem with
> resolving the server to the IP address. Try the fully qualified domain name
> instead.
> If you can connect with TCP/IP, but not with names pipes, you may have a
> problem with the ports used by the named pipes being blocked.
> Linchi
> "Ranginald" wrote:
> > Hi.
> >
> > I am new to sql server so please bear with me.
> > Here is the problem.
> >
> > I am using VWD express to connect to a sql server 2005 db on my local
> > machine. The site and the sql server are local and everything is fine.
> > No problems.
> >
> > I have a sql server hosting plan to host the db. (my local is SQL
> > Server 2005 and the hosted is Sql Server 2000).
> >
> > I use the LOCAL VWD website to access the HOSTED sql server and it
> > connects with no problem. I changed data in the remote version of the
> > db as a double-check that I am accessing the remote db and not the
> > local db.
> >
> > When I go ahead and upload the web site to my web host, different from
> > the sql host (long story), I get this error (provider: Named Pipes
> > Provider, error: 40 - Could not open a connection to SQL Server).
> >
> > Any ideas why this error is happening. My web host verifies that my
> > connection string is fine, and that if I can connect with my local
> > machine then there should be no problem and the problems is on the
> > hosting end.
> >
> > Thanks in advance,
> > Ranginald
> >
> >sql
I am new to sql server so please bear with me.
Here is the problem.
I am using VWD express to connect to a sql server 2005 db on my local
machine. The site and the sql server are local and everything is fine.
No problems.
I have a sql server hosting plan to host the db. (my local is SQL
Server 2005 and the hosted is Sql Server 2000).
I use the LOCAL VWD website to access the HOSTED sql server and it
connects with no problem. I changed data in the remote version of the
db as a double-check that I am accessing the remote db and not the
local db.
When I go ahead and upload the web site to my web host, different from
the sql host (long story), I get this error (provider: Named Pipes
Provider, error: 40 - Could not open a connection to SQL Server).
Any ideas why this error is happening. My web host verifies that my
connection string is fine, and that if I can connect with my local
machine then there should be no problem and the problems is on the
hosting end.
Thanks in advance,
RanginaldOk. Problem solved. I was using a web host with multiple hosted
domains and I think I probably had some kind of IIS app directrory
problem. I moved the site to its own hosting and all was fine with no
changes needed.
Thanks anyway. Hope this tidbit helps someone.
Rangy
Ranginald wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald|||Do you have to connect with named pipes? If not, change the connection string
to connect with TCP/IP (set Network Library=dbmssocn). Assuming that the SQL
connectivity components are properly installed on the web server and you can
ping the database server from the web server, I'd try a few things.
1. Find out the IP address and the TCP port that the SQL instance listens on.
2. Change the connection string to the IP address followed by a comma and
then the TCP port (e.g. set Server=169.12.35.51,5002). If this does not work,
you may have a problem with accessing the port. (if it's the default instance
using the default port, you don't need to test with the port number specified
explicitly).
3. Change the IP to the server name in the Server property of the connection
string, and try again. If this doesn't work, you may have a problem with
resolving the server to the IP address. Try the fully qualified domain name
instead.
If you can connect with TCP/IP, but not with names pipes, you may have a
problem with the ports used by the named pipes being blocked.
Linchi
"Ranginald" wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald
>|||How would I find out the TCP port that the SQL instance listens on?
Thanks
Linchi Shea wrote:
> Do you have to connect with named pipes? If not, change the connection string
> to connect with TCP/IP (set Network Library=dbmssocn). Assuming that the SQL
> connectivity components are properly installed on the web server and you can
> ping the database server from the web server, I'd try a few things.
> 1. Find out the IP address and the TCP port that the SQL instance listens on.
> 2. Change the connection string to the IP address followed by a comma and
> then the TCP port (e.g. set Server=169.12.35.51,5002). If this does not work,
> you may have a problem with accessing the port. (if it's the default instance
> using the default port, you don't need to test with the port number specified
> explicitly).
> 3. Change the IP to the server name in the Server property of the connection
> string, and try again. If this doesn't work, you may have a problem with
> resolving the server to the IP address. Try the fully qualified domain name
> instead.
> If you can connect with TCP/IP, but not with names pipes, you may have a
> problem with the ports used by the named pipes being blocked.
> Linchi
> "Ranginald" wrote:
> > Hi.
> >
> > I am new to sql server so please bear with me.
> > Here is the problem.
> >
> > I am using VWD express to connect to a sql server 2005 db on my local
> > machine. The site and the sql server are local and everything is fine.
> > No problems.
> >
> > I have a sql server hosting plan to host the db. (my local is SQL
> > Server 2005 and the hosted is Sql Server 2000).
> >
> > I use the LOCAL VWD website to access the HOSTED sql server and it
> > connects with no problem. I changed data in the remote version of the
> > db as a double-check that I am accessing the remote db and not the
> > local db.
> >
> > When I go ahead and upload the web site to my web host, different from
> > the sql host (long story), I get this error (provider: Named Pipes
> > Provider, error: 40 - Could not open a connection to SQL Server).
> >
> > Any ideas why this error is happening. My web host verifies that my
> > connection string is fine, and that if I can connect with my local
> > machine then there should be no problem and the problems is on the
> > hosting end.
> >
> > Thanks in advance,
> > Ranginald
> >
> >sql
Named Pipers Provider, error 40, ok from local, error to remote - help
Hi.
I am new to sql server so please bear with me.
Here is the problem.
I am using VWD express to connect to a sql server 2005 db on my local
machine. The site and the sql server are local and everything is fine.
No problems.
I have a sql server hosting plan to host the db. (my local is SQL
Server 2005 and the hosted is Sql Server 2000).
I use the LOCAL VWD website to access the HOSTED sql server and it
connects with no problem. I changed data in the remote version of the
db as a double-check that I am accessing the remote db and not the
local db.
When I go ahead and upload the web site to my web host, different from
the sql host (long story), I get this error (provider: Named Pipes
Provider, error: 40 - Could not open a connection to SQL Server).
Any ideas why this error is happening. My web host verifies that my
connection string is fine, and that if I can connect with my local
machine then there should be no problem and the problems is on the
hosting end.
Thanks in advance,
RanginaldOk. Problem solved. I was using a web host with multiple hosted
domains and I think I probably had some kind of IIS app directrory
problem. I moved the site to its own hosting and all was fine with no
changes needed.
Thanks anyway. Hope this tidbit helps someone.
Rangy
Ranginald wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald
I am new to sql server so please bear with me.
Here is the problem.
I am using VWD express to connect to a sql server 2005 db on my local
machine. The site and the sql server are local and everything is fine.
No problems.
I have a sql server hosting plan to host the db. (my local is SQL
Server 2005 and the hosted is Sql Server 2000).
I use the LOCAL VWD website to access the HOSTED sql server and it
connects with no problem. I changed data in the remote version of the
db as a double-check that I am accessing the remote db and not the
local db.
When I go ahead and upload the web site to my web host, different from
the sql host (long story), I get this error (provider: Named Pipes
Provider, error: 40 - Could not open a connection to SQL Server).
Any ideas why this error is happening. My web host verifies that my
connection string is fine, and that if I can connect with my local
machine then there should be no problem and the problems is on the
hosting end.
Thanks in advance,
RanginaldOk. Problem solved. I was using a web host with multiple hosted
domains and I think I probably had some kind of IIS app directrory
problem. I moved the site to its own hosting and all was fine with no
changes needed.
Thanks anyway. Hope this tidbit helps someone.
Rangy
Ranginald wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald
Monday, March 26, 2012
Named Instance Not Visible local instance visible but does not exist?!?!
I have installed a named instance of MSDE on 4 machines with no problems.
Some had preexisting versions of local which were uninstalled no problems.
On this machine the local instance has been uninstalled. The names instance
installs fine however when you try to connect the named instances are not
visible but the now non existing local instance is visible. Connecting to
ether by manually typing in computername\instancename does not work. I have
removed folders registry values ect with no luck. Any Ideas?
Shane Lim
hi Shane,
"Shane Lim" <gslim@.spatialdynamics.com> ha scritto nel messaggio
news:%23opqoD84EHA.2180@.TK2MSFTNGP10.phx.gbl
> I have installed a named instance of MSDE on 4 machines with no
> problems. Some had preexisting versions of local which were
> uninstalled no problems. On this machine the local instance has been
> uninstalled. The names instance installs fine however when you try to
> connect the named instances are not visible but the now non existing
> local instance is visible. Connecting to ether by manually typing in
> computername\instancename does not work. I have removed folders
> registry values ect with no luck. Any Ideas?
> Shane Lim
what (SQL Server) service name is available in the Control
Panel->management->Services applet?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I only have the MSQL&Instancename and the SQLAGENT$instancename.
They are both set to log in with the localmachine administrator.
When I try to conntect with query analyzer it doesn't show up in the
list but just the computername does. When I type in the
computername/instancename it says connecting then after a bit I get
undable to connect to server computername\instancename:
Server:Msg17,level16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]Sql Server does not exist
or Access is denied.
Same thing when I just click on the computername that is in the list
of available servers after I click the refresh button.
If I uninstall everything then the computername is not available. But
once I reinstall an instance its back.
I even removed all the SQL server Registry enteries under local
machine > software > microsoft still no luck.
On Fri, 17 Dec 2004 12:16:37 +0100, "Andrea Montanari"
<andrea.sqlDMO@.virgilio.it> wrote:
>hi Shane,
>"Shane Lim" <gslim@.spatialdynamics.com> ha scritto nel messaggio
>news:%23opqoD84EHA.2180@.TK2MSFTNGP10.phx.gbl
>what (SQL Server) service name is available in the Control
>Panel->management->Services applet?
|||hi Shane,
"Shane Lim" <gslim@.blizzardice.com> ha scritto nel messaggio
news:fs66s09089a0igajttiku8q93r7stnrj4h@.4ax.com
> ...
> Server:Msg17,level16, State 1
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]Sql Server does not exist
> or Access is denied.
please have a look at
http://support.microsoft.com/default...06&Product=sql
for potential causes of this problem..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Some had preexisting versions of local which were uninstalled no problems.
On this machine the local instance has been uninstalled. The names instance
installs fine however when you try to connect the named instances are not
visible but the now non existing local instance is visible. Connecting to
ether by manually typing in computername\instancename does not work. I have
removed folders registry values ect with no luck. Any Ideas?
Shane Lim
hi Shane,
"Shane Lim" <gslim@.spatialdynamics.com> ha scritto nel messaggio
news:%23opqoD84EHA.2180@.TK2MSFTNGP10.phx.gbl
> I have installed a named instance of MSDE on 4 machines with no
> problems. Some had preexisting versions of local which were
> uninstalled no problems. On this machine the local instance has been
> uninstalled. The names instance installs fine however when you try to
> connect the named instances are not visible but the now non existing
> local instance is visible. Connecting to ether by manually typing in
> computername\instancename does not work. I have removed folders
> registry values ect with no luck. Any Ideas?
> Shane Lim
what (SQL Server) service name is available in the Control
Panel->management->Services applet?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I only have the MSQL&Instancename and the SQLAGENT$instancename.
They are both set to log in with the localmachine administrator.
When I try to conntect with query analyzer it doesn't show up in the
list but just the computername does. When I type in the
computername/instancename it says connecting then after a bit I get
undable to connect to server computername\instancename:
Server:Msg17,level16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]Sql Server does not exist
or Access is denied.
Same thing when I just click on the computername that is in the list
of available servers after I click the refresh button.
If I uninstall everything then the computername is not available. But
once I reinstall an instance its back.
I even removed all the SQL server Registry enteries under local
machine > software > microsoft still no luck.
On Fri, 17 Dec 2004 12:16:37 +0100, "Andrea Montanari"
<andrea.sqlDMO@.virgilio.it> wrote:
>hi Shane,
>"Shane Lim" <gslim@.spatialdynamics.com> ha scritto nel messaggio
>news:%23opqoD84EHA.2180@.TK2MSFTNGP10.phx.gbl
>what (SQL Server) service name is available in the Control
>Panel->management->Services applet?
|||hi Shane,
"Shane Lim" <gslim@.blizzardice.com> ha scritto nel messaggio
news:fs66s09089a0igajttiku8q93r7stnrj4h@.4ax.com
> ...
> Server:Msg17,level16, State 1
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]Sql Server does not exist
> or Access is denied.
please have a look at
http://support.microsoft.com/default...06&Product=sql
for potential causes of this problem..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Monday, March 12, 2012
Mysterious Access Denied Error
Yesterday afternoon I lost access to my local MSDE 2000 sp3(a?)
instance. Usinig NT or SQL authentication I get an 'access denied'
error when I try to connect. This happened suddenly with no changes
to the server on my part. I've tinkered with the Client Network
Utility settings, from Multiprotocol only, every combination of Multi
protocol, TCP/IP, and named pipes. I've tried connecting with my
network machine name, using (local), and using my IP address (both
127.0.0.1 and my network IP). I've tried connecting from Query
Analyzer on other computers. Of course I've rebooted as well, all to
no avail.
instance. Usinig NT or SQL authentication I get an 'access denied'
error when I try to connect. This happened suddenly with no changes
to the server on my part. I've tinkered with the Client Network
Utility settings, from Multiprotocol only, every combination of Multi
protocol, TCP/IP, and named pipes. I've tried connecting with my
network machine name, using (local), and using my IP address (both
127.0.0.1 and my network IP). I've tried connecting from Query
Analyzer on other computers. Of course I've rebooted as well, all to
no avail.
I know that there were network changes being made, but my domain login
(which I normally use to connec to my SQL Server as a sysadmin) is
still in the local administrators group on my machine and I haven't
noticed any problems accessing anything else.
Any ideas?MarcosECasa@.yahoo.com (Marcos) wrote in message news:<cf4137bb.0402100934.3c1cc6de@.posting.google.com>...
> Yesterday afternoon I lost access to my local MSDE 2000 sp3(a?)
> instance. Usinig NT or SQL authentication I get an 'access denied'
> error when I try to connect. This happened suddenly with no changes
> to the server on my part. I've tinkered with the Client Network
> Utility settings, from Multiprotocol only, every combination of Multi
> protocol, TCP/IP, and named pipes. I've tried connecting with my
> network machine name, using (local), and using my IP address (both
> 127.0.0.1 and my network IP). I've tried connecting from Query
> Analyzer on other computers. Of course I've rebooted as well, all to
> no avail.
> I know that there were network changes being made, but my domain login
> (which I normally use to connec to my SQL Server as a sysadmin) is
> still in the local administrators group on my machine and I haven't
> noticed any problems accessing anything else.
> Any ideas?
At the risk of asking a silly question, have you checked that the
service is actually running, using NET START for example? If the
service is stopped, then you get the error "SQL Server does not exist
or access denied", whereas if your login is incorrect (security
issue), you would normally get a "Login failed" error instead.
Simon
Monday, February 20, 2012
My package does not take the values configured in the configuration file.
Hi all,
I created a simple file system task to copy a file from one location to another on my local system.
I used variables to specify the source and destination paths and now in my configuration file if I configure the values to something else also the package is taking the initial default values and not the values specified in the configuration file.
Can anyone throw some light on this.
Thanks in advance.
first of all check that u are using configutaion file in your package correclty
second check that variable is being mapped (present) in your configuration
these are all i can assume from ur explained scenario
write back to me if u find ne luck
regards,
Anas
|||Also, look at the execution log of the package; a warningis generated each time a configuration does not take place. If you are executing it via BIDS, go to the progress tab; otherwise enable package logging.MY GOD SOMEONE IS INTERESTED IN THIS FEATURE
Hi Everyone
As most of you do, I am eagerly awaiting the ability to synchronize my sql mobile database on the hand held to a local sql express database on my local machine
I know users in Microsoft have pointed out to us that we are getting things for free.
At the same time, Microsoft is getting our patience for free and at a cost to us developers.
Its nearly April and as one article says Microsoft will release a fix for this inadequacy
Microsoft...we are happy to pay for this. Palm offers it so what is the big deal. Its not the
reinvention of the wheel. We would have liked that instead of the server synchronization
that bypasses the local sql express database
I as many others are happy to pay
Please let us know when you will be addressing this problem.
I would appreciate the feedback and frustration of other developers. Maybe this will show them we are really running out of time with our clients
Regards
Touraj
Can you point to do the article that says Microsoft will release a fix for this as I am curious?|||Still, even if someone from Microsoft hasnt said this rather than a prominent person in the MVP area, it doesnt defeat the purpose of the Topic.
We need this as our clients are screaming for this functionality.
Please just answer this simple question. WHEN?
Touraj
|||I agree that this needs to be addressed and a schedule would be helpful. I don't see why the merge/snapshot publication capability exists in MSDE 2000 but not in SQL 2005. The "free" argument breaks down when you realize that the earlier version of the database runtime could do this.|||Hi Skip
thanks for replying
for a second i thought i was the only person interested in this feature and thought maybe i had missed something...that was until my client who is a multinational screamed at me again on the phone
Anyone....can anyone from Microsoft please tell us SOMETHING
and not ignore us. We are the customers. Please tell us anything so that we know you guys actually do read our opinions
Darren Shaffer...i really respect you....can you say anything...
Touraj
|||Appreciate your feedback. The requirement for syncing SQL Mobile with SQL Express has been raised earlier. The issue is not that both the products are free but given the time and resources that the SQL Mobile team has can all the requirements be handled effectively. There are quite a few requirements on the plate of the team and the requirements need to be prioritized so that the maximum value is generated given the constraints. The following helps in moving things up in the priority of the Product Team:
1) The criticality of the requirement - How big is the deployment? What will happen if the feature is not made available? What is the future growth rate of the application
2) No of Applications that are affected by not having the feature - How many of the SQL Mobile Application Developer community is affected by not having this feature
3) Customer scenarios - What are the customer business scenarios that are not being solved by not having this feature
Regards
Ambrish
|||This isn't the whole picture by the way.MSDE indeed supports merge replication, it can be configured as distributor and can make publications. I've spent quite some time making scripts to configure newly installed MSDE instance for my needs and I was quite happy with the results - MSDE made me a snapshot on given schedule.
Then it came to synchronizing with ppc... First issue is that you can't install sqlce server tools with no SQL Server installed - it just doesn't seem to be able to locate the presence of MSDE. For testing purposes I've installed SQL Server and sqlce server tools, configured IIS with it (though you can make a virtual folder with sqlce server agent and set all access rights manually). I was able to browse the site with sqlce server agent from ppc and run the agent, but when it came to synchronizing, same error appeared over and over "29045: Initializing SQL Server Reconciler has failed" on MSDE. Switching to SQL Server solves the problem - merge replication works fine, but I need same functionality with MSDE. Official documentation states that it can be done, but it doesn't points to HOW it can be done.
|||
I appreciate your feedback
I also appreciate your priortities may be different than the simple user out there.
But as a company director of a growing mobile application business I can safely say that our business is being impacted by this gap in functionality
1) The functionality of Local Sync between a hand held and SQL Express is CRITICAL
This is irrespective of the size of the project/deployment. Customers and their internal IT department are staggered and laughing at us and Microsoft when they find out its not available.
Remember this is something that is made freely available in palm desktop and should be offered.
The growth rate of our applications will soon cease to exist under the SQL mobile platform if this isnt resolved. Customers do not want devices synching with their servers via IIS.
Eg When you are dealing with Mining companies do you think there is a server out in the mine or the office. NO
There is a rugged laptop running a .NET application for which the user needs to synch information to and from his hand held. This lack of functionality has now cost us one major tender and a whole industry. So what do we do.
I wouldnt even touch Appforge. They at least offer local synch for Palm DB and Access but their scalability is poor
So where does that leave us. Very frustrated because the business is being hurt by our loyalty. So we as well as many other vendors who we have met at exhibitions are deciding to leave if this isnt addressed quick
2) Again 100% of the application developer community. I can safely say this as I have a hand on the pulse of this matter. I think without going into technical aspects, simply from a user/customer point of view this is the sole reason that we dump your technology and decide to use another one.
This is mission critical. One reason I am passionate is that you have 99% of what we need
This 1% is what is causing the 99% to be useless. I cant say it more clearer than that
3) Once again..,.I can give you 100 scenarios.
You are asking us to accept
"a user having to synch a hand held with a server. the process would leave the SQL Express out of synch as it does not partake in that process unless you trigger another synch between SQL Express and SQL Server"
Besides it being a completely poor design we cant accomplish this in scenarios like mobile sales forces, mining, telecommunications and so on when the Server isnt there to act as the middle man. I just cant understand why i even have to explain this to you guys seeing it is so obvious.
This is where you will beat IBM who is currently buying up and looking at industry specific solutions.
With Microsoft our business will soon fail to operate using your technology. Forget about being industry specific and creating solutions. They convenience of mobility is made useless if you are restricted in such a way
You can call me and I can discuss it with more factual details which I will not post here
Suffice to say that losing our company will not be a once off loss in loyatly. We are an example of the widespread dismay and frustration with SQL Mobile
Touraj
|||I'm with Touraj on this matter. For SQL Mobile direct merging with a lightweight desktop DB such as SQL Express (or MSDE) is needed very much to develop an easy-to-deploy lightweight applications|||Thanks Zheka
I am surprised no one else is adding their thoughts to this topic
Can someone from Microsoft tell us...do we need to organise a petition
or what are the formal process to get this escalated
|||Touraj,
By way of encouragement, I can assure you that Microsoft has heard your feedback - there have been several internal discussions I have participated in on the topic of providing merge replication with a lightweight database on the server/PC. We're talked about SQL Mobile server tools for MSDE, peer to peer SQL Mobile to SQL Mobile replication, and some other options as well.
To give you some perspective on this issue, what SQL Express is lacking is more than just a set of server tools for SQL Mobile replication. There are some major, integral components missing from SQL Express which would be needed to support merge replication, including a SQL Agent, a Distribution Database and capability, Replication Monitor, and the ability to define publications and serve as a publisher to name a few. So given that, in my opinion, Microsoft is not likely to come out with a way to bolt all of that on to SQL Express as it exists today - it would effectively be the same as bringing SQL Express up to SQL Server 2005 Standard Edition.
So the real problem is there is no MSDE-equivalent that supports merge replication available with the 2005 set of dev tools. In my opinion (and this is only my opinion), Microsoft lost money on MSDE because an awful lot of people used it in pseudo production environments with 5 or fewer concurrent connections. So retiring it does encourage adoption of SQL Server 2005 standard or better edition, which is an improvement in revenue for the company.
I guess what I am saying is that I don't believe relief is coming in the next few days or weeks based on how large the effort would be to solve this problem (not just technically, but from a marketing, documentation, and distribution standpoint). So you are going to need to consider an alternate option while this issue is being addressed. Here are some options that other people are evaluating or have working now:
1. use web services and roll your own data sychronization between SQL Mobile and SQL Express (this would be my choice in your situation unless you have multiple mobile users changing the same data between synchronization events)
2. use SQL Server 2005 Standard Edition on the server if budget permits
3. use a third party synch tool - I just saw a note from someone at IntelliSync claiming that their Data Synch product has the ability to synchronize SQL Mobile to SQL Express. I have not personally tested that nor do I know what it costs, I'm just passing along that they have made the claim.
4. if your application has a "batch-mindset", meaning you populate a SQL Mobile Database, put it on device, work with it all day, and then copy it back to a server and extract the data, you can use a programmatic approach to synchronizing the data. Tools from www.primeworks.pt are excellent for this.
I will continue to emphasize to Microsoft in my internal discussions with them how important the issue is and if a solution becomes finalized, I'll communicate that here and in the public newsgroup.
-Darren
|||Dear Darren
My sincere thanks for your detailed response. I think you should be running the development division at Microsoft because it is real shame and eye opener when an external consultant is answering these type of questions and we are being treated like fools by Microsoft employees who run you through the same time wasting exercise and questions
I thankyou for your answers and advice. But the question remains why arent we as customers getting these answers from a Microsoft person. Absolutely ridiculous
Regards
Touraj
|||to be honest I think you are pretty much telling to good guys at Microsoft to do all the work for you - this is really not the way to go, nor will it ever happen. Microsoft has done HELL OF ALOT for developers and customers and yet they still get negitivity - outragous in my honest opinion.
putting the differences aside....
you should really handle this in "your" own way - in other words, your own mechinism. This is EASILY achieved. Use WebServices, this is what I had done on several projects of my own.
It doesnt take much time and you will be benefiting from improving your skills, using the technology more and can customize it the way you wish to - that's what it's all about.
my 10 cents ;-)
Subscribe to:
Posts (Atom)