If I establish a remove connection to a server with pcAnywhere, will I be
able to connect to SQL Server on that server programatically or with
Enterprise Manager?
Thanks for any help,
WayneM
To the best of my knowledge PCAnywhere is not like a VPN in that it allows
connections from your PC to the remote one. It simply allows you to control
the remote desktop as if you were there. So if you run EM on the remote
server via PCAnywhere then sure. But I don't think you can run EM from your
machine against the remote one if that is the only connection.
Andrew J. Kelly SQL MVP
"WayneM" <WayneM@.discussions.microsoft.com> wrote in message
news:1D919B19-5C5A-4242-B826-961BD215FE18@.microsoft.com...
> If I establish a remove connection to a server with pcAnywhere, will I be
> able to connect to SQL Server on that server programatically or with
> Enterprise Manager?
> Thanks for any help,
> WayneM
|||Just want to add.
Usually, though, before you can use software like pcAnywhere, RAdmin,
RemoteDesktop, and so on, you would have to establish some kind of 'trusted'
network connection first. Often, that would be VPN. So because of that, you
should be able to run your EM or any SQL Server client from your remote PC.
But I'm just speaking from my experience with the environments I have worked
with, and yours may differ.
Linchi
"WayneM" wrote:
> If I establish a remove connection to a server with pcAnywhere, will I be
> able to connect to SQL Server on that server programatically or with
> Enterprise Manager?
> Thanks for any help,
> WayneM
|||Good point Linchi.
Andrew J. Kelly SQL MVP
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:C40DA762-A8ED-4F2F-B292-0A1FF804074E@.microsoft.com...[vbcol=seagreen]
> Just want to add.
> Usually, though, before you can use software like pcAnywhere, RAdmin,
> RemoteDesktop, and so on, you would have to establish some kind of
> 'trusted'
> network connection first. Often, that would be VPN. So because of that,
> you
> should be able to run your EM or any SQL Server client from your remote
> PC.
> But I'm just speaking from my experience with the environments I have
> worked
> with, and yours may differ.
> Linchi
> "WayneM" wrote:
Showing posts with label connection. Show all posts
Showing posts with label connection. Show all posts
Thursday, March 8, 2012
Can SQL Server Connect with pcAnywhere?
If I establish a remove connection to a server with pcAnywhere, will I be
able to connect to SQL Server on that server programatically or with
Enterprise Manager?
Thanks for any help,
WayneMTo the best of my knowledge PCAnywhere is not like a VPN in that it allows
connections from your PC to the remote one. It simply allows you to control
the remote desktop as if you were there. So if you run EM on the remote
server via PCAnywhere then sure. But I don't think you can run EM from your
machine against the remote one if that is the only connection.
Andrew J. Kelly SQL MVP
"WayneM" <WayneM@.discussions.microsoft.com> wrote in message
news:1D919B19-5C5A-4242-B826-961BD215FE18@.microsoft.com...
> If I establish a remove connection to a server with pcAnywhere, will I be
> able to connect to SQL Server on that server programatically or with
> Enterprise Manager?
> Thanks for any help,
> WayneM|||Just want to add.
Usually, though, before you can use software like pcAnywhere, RAdmin,
RemoteDesktop, and so on, you would have to establish some kind of 'trusted'
network connection first. Often, that would be VPN. So because of that, you
should be able to run your EM or any SQL Server client from your remote PC.
But I'm just speaking from my experience with the environments I have worked
with, and yours may differ.
Linchi
"WayneM" wrote:
> If I establish a remove connection to a server with pcAnywhere, will I be
> able to connect to SQL Server on that server programatically or with
> Enterprise Manager?
> Thanks for any help,
> WayneM|||Good point Linchi.
Andrew J. Kelly SQL MVP
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:C40DA762-A8ED-4F2F-B292-0A1FF804074E@.microsoft.com...[vbcol=seagreen]
> Just want to add.
> Usually, though, before you can use software like pcAnywhere, RAdmin,
> RemoteDesktop, and so on, you would have to establish some kind of
> 'trusted'
> network connection first. Often, that would be VPN. So because of that,
> you
> should be able to run your EM or any SQL Server client from your remote
> PC.
> But I'm just speaking from my experience with the environments I have
> worked
> with, and yours may differ.
> Linchi
> "WayneM" wrote:
>
able to connect to SQL Server on that server programatically or with
Enterprise Manager?
Thanks for any help,
WayneMTo the best of my knowledge PCAnywhere is not like a VPN in that it allows
connections from your PC to the remote one. It simply allows you to control
the remote desktop as if you were there. So if you run EM on the remote
server via PCAnywhere then sure. But I don't think you can run EM from your
machine against the remote one if that is the only connection.
Andrew J. Kelly SQL MVP
"WayneM" <WayneM@.discussions.microsoft.com> wrote in message
news:1D919B19-5C5A-4242-B826-961BD215FE18@.microsoft.com...
> If I establish a remove connection to a server with pcAnywhere, will I be
> able to connect to SQL Server on that server programatically or with
> Enterprise Manager?
> Thanks for any help,
> WayneM|||Just want to add.
Usually, though, before you can use software like pcAnywhere, RAdmin,
RemoteDesktop, and so on, you would have to establish some kind of 'trusted'
network connection first. Often, that would be VPN. So because of that, you
should be able to run your EM or any SQL Server client from your remote PC.
But I'm just speaking from my experience with the environments I have worked
with, and yours may differ.
Linchi
"WayneM" wrote:
> If I establish a remove connection to a server with pcAnywhere, will I be
> able to connect to SQL Server on that server programatically or with
> Enterprise Manager?
> Thanks for any help,
> WayneM|||Good point Linchi.
Andrew J. Kelly SQL MVP
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:C40DA762-A8ED-4F2F-B292-0A1FF804074E@.microsoft.com...[vbcol=seagreen]
> Just want to add.
> Usually, though, before you can use software like pcAnywhere, RAdmin,
> RemoteDesktop, and so on, you would have to establish some kind of
> 'trusted'
> network connection first. Often, that would be VPN. So because of that,
> you
> should be able to run your EM or any SQL Server client from your remote
> PC.
> But I'm just speaking from my experience with the environments I have
> worked
> with, and yours may differ.
> Linchi
> "WayneM" wrote:
>
Wednesday, March 7, 2012
Can SQL Reporting write to a WebDAV sharepoint?
We have a sharepoint <\\ces\cesgypdav> that is a WebDAV connection, not an actual fileshare. A SSRS Subscription fails on file write ... "Failure writing file <name here > : The network path was not found" ... to this path.
Can SQL Reporting write to a WebDAV sharepoint?
WebDAV issue is known, need to 'work around'.This helps: http://sqljunkies.com/WebLog/tpagel/archive/2005/12/23/17682.aspx
Tuesday, February 14, 2012
Can only log into a MSDE ODBC Connection as Administrator
When trying to log into a ODBC connection as a power user on a network we
receive the following error:
Connection failed:
SQLState:'01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibbect ()),
Connection failed:
SQLState:'08001'
SQL server Error:178
[microsoft][odbc sql server driver][dbnetlib]sql server does not exist or
access denied.
Change the user to Administrator and they are able to login.
Did you add logins for other users who aren't members of the
local admin group on the box where MSDE is installed? It
sounds like they may not have logins setup in MSDE.
By default, members of the local admins group will have
access. For other users, you need to add logins.
-Sue
On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:
>When trying to log into a ODBC connection as a power user on a network we
>receive the following error:
>Connection failed:
>SQLState:'01000'
>SQL Server Error: 53
>[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibbect ()),
>Connection failed:
>SQLState:'08001'
>SQL server Error:178
>[microsoft][odbc sql server driver][dbnetlib]sql server does not exist or
>access denied.
>Change the user to Administrator and they are able to login.
|||Sue,
Yes I did add them to the system as a user. Then created an MSDE Group.
The Group has the following rights:
GROUP EVERYONE - Read to Program Files
MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
FOLDER
USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED WE
GET THE FOLLOWING ERROR:
AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
I APPRECIATE YOUR HELP.
"Sue Hoegemeier" wrote:
> Did you add logins for other users who aren't members of the
> local admin group on the box where MSDE is installed? It
> sounds like they may not have logins setup in MSDE.
> By default, members of the local admins group will have
> access. For other users, you need to add logins.
> -Sue
> On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>
|||No need to yell. Using caps is considered yelling in
newsgroups.
By adding the users as logins in SQL Server, that doesn't
have anything to do with adding them to groups on the box
where MSDE is running.
How exactly are you trying to connect? I think something is
missing here as mapping drives is not necessary, giving
users full control on MSDE folders, etc is generally not
necessary either.
-Sue
On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue,
>Yes I did add them to the system as a user. Then created an MSDE Group.
>The Group has the following rights:
> GROUP EVERYONE - Read to Program Files
> MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
>CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
>FOLDER
>USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
>PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
>APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
>NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
>ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED WE
>GET THE FOLLOWING ERROR:
>AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
>WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
>CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
>I APPRECIATE YOUR HELP.
>
>"Sue Hoegemeier" wrote:
|||I apologize I did not know that caps were yelling, I am happy for the help.
Since we are testing this on our network, I am logging into our domain where
both systems reside. The MSDE is running on an XP workstation and we have
other workstations attempting to log into it. When we go into the ODBC setup
we can see the MSDE instance but cannot log on to it.
Bonnie
"Sue Hoegemeier" wrote:
> No need to yell. Using caps is considered yelling in
> newsgroups.
> By adding the users as logins in SQL Server, that doesn't
> have anything to do with adding them to groups on the box
> where MSDE is running.
> How exactly are you trying to connect? I think something is
> missing here as mapping drives is not necessary, giving
> users full control on MSDE folders, etc is generally not
> necessary either.
> -Sue
> On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>
|||No problem...figured you just didn't know about the caps
thing. Anyway, check the event logs on the XP workstation
where MSDE is running to see if there are any security
errors. Make sure the MSDE instance is listening on TCP/IP
and that the clients are configure to connect with TCP/IP.
You would probably want to start by running through the
following article - it's long but connectivity issues aren't
real easy to resolve as it can be so many different things.
Potential causes of the "SQL Server does not exist or access
denied" error message
http://support.microsoft.com/?id=328306
-Sue
On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I apologize I did not know that caps were yelling, I am happy for the help.
>Since we are testing this on our network, I am logging into our domain where
>both systems reside. The MSDE is running on an XP workstation and we have
>other workstations attempting to log into it. When we go into the ODBC setup
>we can see the MSDE instance but cannot log on to it.
>Bonnie
>
>"Sue Hoegemeier" wrote:
|||Sue,
We found out we were using the wrong port for MSDE. MSDE was listening on
Port 1143. We were using the SQL default of 1443 Thank you for your help. I
have another question now that this one is resolved. I'll start a new
thread. Thank you again for your help.
"Sue Hoegemeier" wrote:
> No problem...figured you just didn't know about the caps
> thing. Anyway, check the event logs on the XP workstation
> where MSDE is running to see if there are any security
> errors. Make sure the MSDE instance is listening on TCP/IP
> and that the clients are configure to connect with TCP/IP.
> You would probably want to start by running through the
> following article - it's long but connectivity issues aren't
> real easy to resolve as it can be so many different things.
> Potential causes of the "SQL Server does not exist or access
> denied" error message
> http://support.microsoft.com/?id=328306
> -Sue
> On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>
receive the following error:
Connection failed:
SQLState:'01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibbect ()),
Connection failed:
SQLState:'08001'
SQL server Error:178
[microsoft][odbc sql server driver][dbnetlib]sql server does not exist or
access denied.
Change the user to Administrator and they are able to login.
Did you add logins for other users who aren't members of the
local admin group on the box where MSDE is installed? It
sounds like they may not have logins setup in MSDE.
By default, members of the local admins group will have
access. For other users, you need to add logins.
-Sue
On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:
>When trying to log into a ODBC connection as a power user on a network we
>receive the following error:
>Connection failed:
>SQLState:'01000'
>SQL Server Error: 53
>[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibbect ()),
>Connection failed:
>SQLState:'08001'
>SQL server Error:178
>[microsoft][odbc sql server driver][dbnetlib]sql server does not exist or
>access denied.
>Change the user to Administrator and they are able to login.
|||Sue,
Yes I did add them to the system as a user. Then created an MSDE Group.
The Group has the following rights:
GROUP EVERYONE - Read to Program Files
MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
FOLDER
USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED WE
GET THE FOLLOWING ERROR:
AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
I APPRECIATE YOUR HELP.
"Sue Hoegemeier" wrote:
> Did you add logins for other users who aren't members of the
> local admin group on the box where MSDE is installed? It
> sounds like they may not have logins setup in MSDE.
> By default, members of the local admins group will have
> access. For other users, you need to add logins.
> -Sue
> On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>
|||No need to yell. Using caps is considered yelling in
newsgroups.
By adding the users as logins in SQL Server, that doesn't
have anything to do with adding them to groups on the box
where MSDE is running.
How exactly are you trying to connect? I think something is
missing here as mapping drives is not necessary, giving
users full control on MSDE folders, etc is generally not
necessary either.
-Sue
On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue,
>Yes I did add them to the system as a user. Then created an MSDE Group.
>The Group has the following rights:
> GROUP EVERYONE - Read to Program Files
> MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
>CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
>FOLDER
>USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
>PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
>APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
>NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
>ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED WE
>GET THE FOLLOWING ERROR:
>AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
>WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
>CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
>I APPRECIATE YOUR HELP.
>
>"Sue Hoegemeier" wrote:
|||I apologize I did not know that caps were yelling, I am happy for the help.
Since we are testing this on our network, I am logging into our domain where
both systems reside. The MSDE is running on an XP workstation and we have
other workstations attempting to log into it. When we go into the ODBC setup
we can see the MSDE instance but cannot log on to it.
Bonnie
"Sue Hoegemeier" wrote:
> No need to yell. Using caps is considered yelling in
> newsgroups.
> By adding the users as logins in SQL Server, that doesn't
> have anything to do with adding them to groups on the box
> where MSDE is running.
> How exactly are you trying to connect? I think something is
> missing here as mapping drives is not necessary, giving
> users full control on MSDE folders, etc is generally not
> necessary either.
> -Sue
> On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>
|||No problem...figured you just didn't know about the caps
thing. Anyway, check the event logs on the XP workstation
where MSDE is running to see if there are any security
errors. Make sure the MSDE instance is listening on TCP/IP
and that the clients are configure to connect with TCP/IP.
You would probably want to start by running through the
following article - it's long but connectivity issues aren't
real easy to resolve as it can be so many different things.
Potential causes of the "SQL Server does not exist or access
denied" error message
http://support.microsoft.com/?id=328306
-Sue
On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I apologize I did not know that caps were yelling, I am happy for the help.
>Since we are testing this on our network, I am logging into our domain where
>both systems reside. The MSDE is running on an XP workstation and we have
>other workstations attempting to log into it. When we go into the ODBC setup
>we can see the MSDE instance but cannot log on to it.
>Bonnie
>
>"Sue Hoegemeier" wrote:
|||Sue,
We found out we were using the wrong port for MSDE. MSDE was listening on
Port 1143. We were using the SQL default of 1443 Thank you for your help. I
have another question now that this one is resolved. I'll start a new
thread. Thank you again for your help.
"Sue Hoegemeier" wrote:
> No problem...figured you just didn't know about the caps
> thing. Anyway, check the event logs on the XP workstation
> where MSDE is running to see if there are any security
> errors. Make sure the MSDE instance is listening on TCP/IP
> and that the clients are configure to connect with TCP/IP.
> You would probably want to start by running through the
> following article - it's long but connectivity issues aren't
> real easy to resolve as it can be so many different things.
> Potential causes of the "SQL Server does not exist or access
> denied" error message
> http://support.microsoft.com/?id=328306
> -Sue
> On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>
Can only log into a MSDE ODBC Connection as Administrator
When trying to log into a ODBC connection as a power user on a network we
receive the following error:
Connection failed:
SQLState:'01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibbe
ct ()),
Connection failed:
SQLState:'08001'
SQL server Error:178
[microsoft][odbc sql server driver][dbnetlib]sql server does not
exist or
access denied.
Change the user to Administrator and they are able to login.Did you add logins for other users who aren't members of the
local admin group on the box where MSDE is installed? It
sounds like they may not have logins setup in MSDE.
By default, members of the local admins group will have
access. For other users, you need to add logins.
-Sue
On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:
>When trying to log into a ODBC connection as a power user on a network we
>receive the following error:
>Connection failed:
>SQLState:'01000'
>SQL Server Error: 53
>[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibb
ect ()),
>Connection failed:
>SQLState:'08001'
>SQL server Error:178
>[microsoft][odbc sql server driver][dbnetlib]sql server does no
t exist or
>access denied.
>Change the user to Administrator and they are able to login.|||Sue,
Yes I did add them to the system as a user. Then created an MSDE Group.
The Group has the following rights:
GROUP EVERYONE - Read to Program Files
MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
FOLDER
USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED WE
GET THE FOLLOWING ERROR:
AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
I APPRECIATE YOUR HELP.
"Sue Hoegemeier" wrote:
> Did you add logins for other users who aren't members of the
> local admin group on the box where MSDE is installed? It
> sounds like they may not have logins setup in MSDE.
> By default, members of the local admins group will have
> access. For other users, you need to add logins.
> -Sue
> On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>|||No need to yell. Using caps is considered yelling in
newsgroups.
By adding the users as logins in SQL Server, that doesn't
have anything to do with adding them to groups on the box
where MSDE is running.
How exactly are you trying to connect? I think something is
missing here as mapping drives is not necessary, giving
users full control on MSDE folders, etc is generally not
necessary either.
-Sue
On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue,
>Yes I did add them to the system as a user. Then created an MSDE Group.
>The Group has the following rights:
> GROUP EVERYONE - Read to Program Files
> MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
>CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
>FOLDER
>USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
>PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
>APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
>NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
>ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED W
E
>GET THE FOLLOWING ERROR:
>AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
>WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
>CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
>I APPRECIATE YOUR HELP.
>
>"Sue Hoegemeier" wrote:
>|||I apologize I did not know that caps were yelling, I am happy for the help.
Since we are testing this on our network, I am logging into our domain where
both systems reside. The MSDE is running on an XP workstation and we have
other workstations attempting to log into it. When we go into the ODBC setu
p
we can see the MSDE instance but cannot log on to it.
Bonnie
"Sue Hoegemeier" wrote:
> No need to yell. Using caps is considered yelling in
> newsgroups.
> By adding the users as logins in SQL Server, that doesn't
> have anything to do with adding them to groups on the box
> where MSDE is running.
> How exactly are you trying to connect? I think something is
> missing here as mapping drives is not necessary, giving
> users full control on MSDE folders, etc is generally not
> necessary either.
> -Sue
> On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>|||No problem...figured you just didn't know about the caps
thing. Anyway, check the event logs on the XP workstation
where MSDE is running to see if there are any security
errors. Make sure the MSDE instance is listening on TCP/IP
and that the clients are configure to connect with TCP/IP.
You would probably want to start by running through the
following article - it's long but connectivity issues aren't
real easy to resolve as it can be so many different things.
Potential causes of the "SQL Server does not exist or access
denied" error message
http://support.microsoft.com/?id=328306
-Sue
On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I apologize I did not know that caps were yelling, I am happy for the help.
>Since we are testing this on our network, I am logging into our domain wher
e
>both systems reside. The MSDE is running on an XP workstation and we have
>other workstations attempting to log into it. When we go into the ODBC set
up
>we can see the MSDE instance but cannot log on to it.
>Bonnie
>
>"Sue Hoegemeier" wrote:
>|||Sue,
We found out we were using the wrong port for MSDE. MSDE was listening on
Port 1143. We were using the SQL default of 1443 Thank you for your help.
I
have another question now that this one is resolved. I'll start a new
thread. Thank you again for your help.
"Sue Hoegemeier" wrote:
> No problem...figured you just didn't know about the caps
> thing. Anyway, check the event logs on the XP workstation
> where MSDE is running to see if there are any security
> errors. Make sure the MSDE instance is listening on TCP/IP
> and that the clients are configure to connect with TCP/IP.
> You would probably want to start by running through the
> following article - it's long but connectivity issues aren't
> real easy to resolve as it can be so many different things.
> Potential causes of the "SQL Server does not exist or access
> denied" error message
> http://support.microsoft.com/?id=328306
> -Sue
> On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>
receive the following error:
Connection failed:
SQLState:'01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibbe
ct ()),
Connection failed:
SQLState:'08001'
SQL server Error:178
[microsoft][odbc sql server driver][dbnetlib]sql server does not
exist or
access denied.
Change the user to Administrator and they are able to login.Did you add logins for other users who aren't members of the
local admin group on the box where MSDE is installed? It
sounds like they may not have logins setup in MSDE.
By default, members of the local admins group will have
access. For other users, you need to add logins.
-Sue
On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:
>When trying to log into a ODBC connection as a power user on a network we
>receive the following error:
>Connection failed:
>SQLState:'01000'
>SQL Server Error: 53
>[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibb
ect ()),
>Connection failed:
>SQLState:'08001'
>SQL server Error:178
>[microsoft][odbc sql server driver][dbnetlib]sql server does no
t exist or
>access denied.
>Change the user to Administrator and they are able to login.|||Sue,
Yes I did add them to the system as a user. Then created an MSDE Group.
The Group has the following rights:
GROUP EVERYONE - Read to Program Files
MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
FOLDER
USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED WE
GET THE FOLLOWING ERROR:
AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
I APPRECIATE YOUR HELP.
"Sue Hoegemeier" wrote:
> Did you add logins for other users who aren't members of the
> local admin group on the box where MSDE is installed? It
> sounds like they may not have logins setup in MSDE.
> By default, members of the local admins group will have
> access. For other users, you need to add logins.
> -Sue
> On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>|||No need to yell. Using caps is considered yelling in
newsgroups.
By adding the users as logins in SQL Server, that doesn't
have anything to do with adding them to groups on the box
where MSDE is running.
How exactly are you trying to connect? I think something is
missing here as mapping drives is not necessary, giving
users full control on MSDE folders, etc is generally not
necessary either.
-Sue
On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue,
>Yes I did add them to the system as a user. Then created an MSDE Group.
>The Group has the following rights:
> GROUP EVERYONE - Read to Program Files
> MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
>CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
>FOLDER
>USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
>PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
>APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
>NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
>ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED W
E
>GET THE FOLLOWING ERROR:
>AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
>WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
>CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
>I APPRECIATE YOUR HELP.
>
>"Sue Hoegemeier" wrote:
>|||I apologize I did not know that caps were yelling, I am happy for the help.
Since we are testing this on our network, I am logging into our domain where
both systems reside. The MSDE is running on an XP workstation and we have
other workstations attempting to log into it. When we go into the ODBC setu
p
we can see the MSDE instance but cannot log on to it.
Bonnie
"Sue Hoegemeier" wrote:
> No need to yell. Using caps is considered yelling in
> newsgroups.
> By adding the users as logins in SQL Server, that doesn't
> have anything to do with adding them to groups on the box
> where MSDE is running.
> How exactly are you trying to connect? I think something is
> missing here as mapping drives is not necessary, giving
> users full control on MSDE folders, etc is generally not
> necessary either.
> -Sue
> On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>|||No problem...figured you just didn't know about the caps
thing. Anyway, check the event logs on the XP workstation
where MSDE is running to see if there are any security
errors. Make sure the MSDE instance is listening on TCP/IP
and that the clients are configure to connect with TCP/IP.
You would probably want to start by running through the
following article - it's long but connectivity issues aren't
real easy to resolve as it can be so many different things.
Potential causes of the "SQL Server does not exist or access
denied" error message
http://support.microsoft.com/?id=328306
-Sue
On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I apologize I did not know that caps were yelling, I am happy for the help.
>Since we are testing this on our network, I am logging into our domain wher
e
>both systems reside. The MSDE is running on an XP workstation and we have
>other workstations attempting to log into it. When we go into the ODBC set
up
>we can see the MSDE instance but cannot log on to it.
>Bonnie
>
>"Sue Hoegemeier" wrote:
>|||Sue,
We found out we were using the wrong port for MSDE. MSDE was listening on
Port 1143. We were using the SQL default of 1443 Thank you for your help.
I
have another question now that this one is resolved. I'll start a new
thread. Thank you again for your help.
"Sue Hoegemeier" wrote:
> No problem...figured you just didn't know about the caps
> thing. Anyway, check the event logs on the XP workstation
> where MSDE is running to see if there are any security
> errors. Make sure the MSDE instance is listening on TCP/IP
> and that the clients are configure to connect with TCP/IP.
> You would probably want to start by running through the
> following article - it's long but connectivity issues aren't
> real easy to resolve as it can be so many different things.
> Potential causes of the "SQL Server does not exist or access
> denied" error message
> http://support.microsoft.com/?id=328306
> -Sue
> On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>
Sunday, February 12, 2012
Can not see any server in the available servers list
I successfully installed SQL Server 2005 Express edition in my pc. I ran Visual Basic 6 and used and Ado object to build a connection string to access the server but, I could not see any server in the comobox list.
I always get connection failure messages say that the server does not exitst!!!
Any help please.
Thanks
The installation process does not leave the server open to 'outside' connections. You will have to manually 'open' the server. Here are some useful resources:
Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
Configuration -Connect to SQL Express from "downlevel clients"
http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx
Configuration -Connect to SQL Express and ‘Stay Connected’
http://betav.com/blog/billva/2006/06/getting_and_staying_connected.html
Friday, February 10, 2012
can not login my database when published to IIS
hi,
i am tring to use the 'xcopy' way to deploy my web site, this is the connection string i am using:
"Data Source=.\SQLEXPRESS;INITIAL CATALOG=;AttachDbFilename='|DataDirectory|\HotStage.mdf';Integrated Security=True;User Instance=True"
it works when in debug mode, but after i depoly it to my XP's IIS, it can not login the database, the error message is :
Cannot Login to the default user database. Login Failed. Login Failed for user xxx\ASPNET
'xxx' is my computer.
i think this problem is cause of improper setting of security, but i really do not know how to set it in this situation, because the database is attached to the db system dynamically.
plz someone help, thx
when you use userinstance in sql server express, once the applicaiton is connected to the database you can not connect to the database using SSMO Express. If you donot want to use userinstance change the connection string . "AttachDbFilename='|DataDirectory|\HotStage.mdf' " this is the part where u are attaching the db in connection string. change it if not needed
refer :
http://blogs.msdn.com/sqlexpress/archive/2006/11/22/connecting-to-sql-express-user-instances-in-management-studio.aspx
Madhu
|||hi,
yes, after i remove the 'User Instanct' clause, and did some permission adjustment, i do connected to my database.
but now i have another strange problem... it says my database is read-only
i have set that folder to hava 'write' permission in IIS.
any idea about this?
can not login my database when published to IIS
hi,
i am tring to use the 'xcopy' way to deploy my web site, this is the connection string i am using:
"Data Source=.\SQLEXPRESS;INITIAL CATALOG=;AttachDbFilename='|DataDirectory|\HotStage.mdf';Integrated Security=True;User Instance=True"
it works when in debug mode, but after i depoly it to my XP's IIS, it can not login the database, the error message is :
Cannot Login to the default user database. Login Failed. Login Failed for user xxx\ASPNET
'xxx' is my computer.
i think this problem is cause of improper setting of security, but i really do not know how to set it in this situation, because the database is attached to the db system dynamically.
plz someone help, thx
when you use userinstance in sql server express, once the applicaiton is connected to the database you can not connect to the database using SSMO Express. If you donot want to use userinstance change the connection string . "AttachDbFilename='|DataDirectory|\HotStage.mdf' " this is the part where u are attaching the db in connection string. change it if not needed
refer :
http://blogs.msdn.com/sqlexpress/archive/2006/11/22/connecting-to-sql-express-user-instances-in-management-studio.aspx
Madhu
|||hi,
yes, after i remove the 'User Instanct' clause, and did some permission adjustment, i do connected to my database.
but now i have another strange problem... it says my database is read-only
i have set that folder to hava 'write' permission in IIS.
any idea about this?
Subscribe to:
Posts (Atom)