ODBC driver problem occurs on table create

Hi all!

I get the following error when trying to create a table:
[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen (Connect()).

I use the same connection for table updates and selects and never have a problem. This only happens on table create. It also only happens on one machine (Win2K with SQL server 2000 Enterprise Edition). I've run this app without getting this problem on at least ten other machines (mostly WinXP, but also a few Win2K).

Any ideas?

nscdDoes the account that you're using have permissions on that SQL Server to create new tables?|||Yes it does.

I've also changed it so that I connect using the sa account, but still get the same problem.

Cheers

nscd|||Hi all

Further investigation has revealed that my client's machine was fairly out of date and installing the latest MDAC patch from MS resolved the problem.

Cheers

nscd

ODBC connections

I have been asked to develop some security software that includes detection
of what ODBC connections to SQL Server databases exist. I think that it is
not useful, at least for security purposes, to determine what ODBC
connections exist for a database. Am I wrong?
One reason it is not useful is that a connection can be created dynamicly
anytime. I know that, since I do it. The person asking for this project is
not familiar with such things but I have already explained this much to him.
I don't know about SQL Server security enough to be sure, but it is my
understanding that it has it's own security that is much more effective than
attempts to prevent access by limiting ODBC connections.
I am not asking what other solutions exist; if I am correct in what I say
here, then I will pursue the other solutions myself and when necessary in
another thread.>I have been asked to develop some security software that includes detection
>of what ODBC connections to SQL Server databases exist. I think that it is
>not useful, at least for security purposes, to determine what ODBC
>connections exist for a database. Am I wrong?
You are correct. The person requesting this may not be familiar with SQL
Server data access architecture and now it relates to security. ODBC is
just one data access API of many. There are also others, such as OLE DB,
SQL Native Client. It does not makes sense to me that one would care, at
least from a security perspective, which API is used to connect to SQL
Server. All APIs can access SQL Server without a pre-configured DSN.

> I don't know about SQL Server security enough to be sure, but it is my
> understanding that it has it's own security that is much more effective
> than attempts to prevent access by limiting ODBC connections.
Absolutely. SQL Server security is the primary place security needs to be
implemented. Logins, database users and object permissions all provide
various levels of security. Given a login with appropriate permissions, one
could write a simple VBScript using Notepad to access and manipulate
database data.
Hope this helps.
Dan Guzman
SQL Server MVP
"Sam Hobbs" <samuel@.social.rr.com_change_social_to_socal> wrote in message
news:%23GT8ACP%23FHA.3340@.TK2MSFTNGP12.phx.gbl...
>I have been asked to develop some security software that includes detection
>of what ODBC connections to SQL Server databases exist. I think that it is
>not useful, at least for security purposes, to determine what ODBC
>connections exist for a database. Am I wrong?
> One reason it is not useful is that a connection can be created dynamicly
> anytime. I know that, since I do it. The person asking for this project is
> not familiar with such things but I have already explained this much to
> him.
> I don't know about SQL Server security enough to be sure, but it is my
> understanding that it has it's own security that is much more effective
> than attempts to prevent access by limiting ODBC connections.
> I am not asking what other solutions exist; if I am correct in what I say
> here, then I will pursue the other solutions myself and when necessary in
> another thread.
>|||Yes, Dan, that definitely helps; thank you.

ODBC connection failure

After upgrading to Windows 2003 Server, I can no longer
access SQL Server via ODBC. It says the SQL Server
doesn't exist or access denied. None of the settings have
changed after the upgrade.
Is there a fix to this?
Thanks in advance.(a) stop using ODBC, it's been deprecated. OLEDB is much preferred.
(b) SQL Server authentication? Windows authentication? What is the
username you are using? What kind of account is it? Have you tried a
different authentication method and/or a different user?
(c) http://support.microsoft.com/?kbid=328306
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:19b9c01c44d6d$b0030b20$a401280a@.phx
.gbl...
> After upgrading to Windows 2003 Server, I can no longer
> access SQL Server via ODBC. It says the SQL Server
> doesn't exist or access denied. None of the settings have
> changed after the upgrade.
> Is there a fix to this?
> Thanks in advance.|||How would I switch to the OLEDB method? It's SQL Server
auth., and also tried different methods and users.
Also, I found that the ODBC Driver versions are different
on the client machines. Would I need to update the
clients to the new version?

>--Original Message--
>(a) stop using ODBC, it's been deprecated. OLEDB is much
preferred.
>(b) SQL Server authentication? Windows authentication?
What is the
>username you are using? What kind of account is it?
Have you tried a
>different authentication method and/or a different user?
>(c) http://support.microsoft.com/?kbid=328306
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"Mike" <anonymous@.discussions.microsoft.com> wrote in
message
> news:19b9c01c44d6d$b0030b20$a401280a@.phx
.gbl...
have[vbcol=seagreen]
>
>.
>|||> How would I switch to the OLEDB method?
That really depends... what application/language are you using for the
client applications?

> Also, I found that the ODBC Driver versions are different
> on the client machines. Would I need to update the
> clients to the new version?
Yes, apply the latest MDAC all around. You should try to avoid mismatched
versions between client and server.
85d0506396c&DisplayLang=en" target="_blank">http://www.microsoft.com/downloads/...&DisplayLang=en
http://www.aspfaq.com/
(Reverse address to reply.)|||Installing the MDAC results in the same SQL Server does
not exist error.
All of the clients are using Windows XP Pro to connect to
the SQL Server.

>--Original Message--
>That really depends... what application/language are you
using for the
>client applications?
>
different[vbcol=seagreen]
>Yes, apply the latest MDAC all around. You should try to
avoid mismatched
>versions between client and server.
>http://www.microsoft.com/downloads/details.aspx?
FamilyID=6c050fe3-c795-4b7d-b037-
185d0506396c&DisplayLang=en
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)|||> All of the clients are using Windows XP Pro to connect to
> the SQL Server.
That's the operating system, but it doesn't tell me anything about the
application that is attempting to make a connection. Are you trying to
connect from Excel, notepad, ColdFusion, Query Analyzer, the ODBC control
panel applet, ... ?
Have you gone through http://support.microsoft.com/?kbid=328306 ?
http://www.aspfaq.com/
(Reverse address to reply.)|||I'm trying to connect from the ODBC Control Panel.
Yes, I have through the 328306 article and haven't found
any resolutions.
Would the easiest thing to do be revert back to Windows
2000 when this all worked correctly?

>--Original Message--
to[vbcol=seagreen]
>That's the operating system, but it doesn't tell me
anything about the
>application that is attempting to make a connection. Are
you trying to
>connect from Excel, notepad, ColdFusion, Query Analyzer,
the ODBC control
>panel applet, ... ?
>Have you gone through http://support.microsoft.com/?
kbid=328306 ?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>|||> I'm trying to connect from the ODBC Control Panel.
Why? And then what are you going to do with it once you've connected?
Typically this is used to create a DSN for some other application, like an
ASP page or VB app. In which case, you are much better off connecting
through OLEDB. I can't tell you how to do that until you provide more
information.

> Yes, I have through the 328306 article and haven't found
> any resolutions.
Can you tell us what you tried, with regard to each article listed at that
link? I'm guessing you didn't inspect every single article listed there,
since it has been less than an hour, and you'd have to be Number 5 from
Short Circuit to have read all of the content already.

> Would the easiest thing to do be revert back to Windows
> 2000 when this all worked correctly?
No, that's silly. Windows XP is not to blame; you have a configuration
issue, that's all. If you tell us everything you tried regarding 328306,
you will leave the remaining potential options.
http://www.aspfaq.com/
(Reverse address to reply.)|||I need the DSN to run Crystal Reports.
As for KB #328306, I tried everything under the Server-
Related Causes. The protocols are all ok, port 1433 is
the same on each machine, and tried giving the server a
new alias.
As for the Client/App-Related Causes, the protocols don't
change, no network adaptor issues, not worried about MDAC
connections, and Named Pipes don't apply.
There was nothing applicable under the Network Causes as
everything is run locally.

>--Original Message--
>Why? And then what are you going to do with it once
you've connected?
>Typically this is used to create a DSN for some other
application, like an
>ASP page or VB app. In which case, you are much better
off connecting
>through OLEDB. I can't tell you how to do that until you
provide more
>information.
>
>Can you tell us what you tried, with regard to each
article listed at that
>link? I'm guessing you didn't inspect every single
article listed there,
>since it has been less than an hour, and you'd have to be
Number 5 from
>Short Circuit to have read all of the content already.
>
>No, that's silly. Windows XP is not to blame; you have a
configuration
>issue, that's all. If you tell us everything you tried
regarding 328306,
>you will leave the remaining potential options.
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>|||So what name are you using to refer to the local server? Have you tried
"LOCALHOST", "(LOCAL)", "127.0.0.1", the actual server name, the actual IP
address?
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:199ec01c44d7f$b2851cf0$a301280a@.phx
.gbl...[vbcol=seagreen]
> I need the DSN to run Crystal Reports.
> As for KB #328306, I tried everything under the Server-
> Related Causes. The protocols are all ok, port 1433 is
> the same on each machine, and tried giving the server a
> new alias.
> As for the Client/App-Related Causes, the protocols don't
> change, no network adaptor issues, not worried about MDAC
> connections, and Named Pipes don't apply.
> There was nothing applicable under the Network Causes as
> everything is run locally.
>
> you've connected?
> application, like an
> off connecting
> provide more
> article listed at that
> article listed there,
> Number 5 from
> configuration
> regarding 328306,

ODBC connection failure

After upgrading to Windows 2003 Server, I can no longer
access SQL Server via ODBC. It says the SQL Server
doesn't exist or access denied. None of the settings have
changed after the upgrade.
Is there a fix to this?
Thanks in advance.
(a) stop using ODBC, it's been deprecated. OLEDB is much preferred.
(b) SQL Server authentication? Windows authentication? What is the
username you are using? What kind of account is it? Have you tried a
different authentication method and/or a different user?
(c) http://support.microsoft.com/?kbid=328306
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:19b9c01c44d6d$b0030b20$a401280a@.phx.gbl...
> After upgrading to Windows 2003 Server, I can no longer
> access SQL Server via ODBC. It says the SQL Server
> doesn't exist or access denied. None of the settings have
> changed after the upgrade.
> Is there a fix to this?
> Thanks in advance.
|||How would I switch to the OLEDB method? It's SQL Server
auth., and also tried different methods and users.
Also, I found that the ODBC Driver versions are different
on the client machines. Would I need to update the
clients to the new version?

>--Original Message--
>(a) stop using ODBC, it's been deprecated. OLEDB is much
preferred.
>(b) SQL Server authentication? Windows authentication?
What is the
>username you are using? What kind of account is it?
Have you tried a
>different authentication method and/or a different user?
>(c) http://support.microsoft.com/?kbid=328306
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"Mike" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:19b9c01c44d6d$b0030b20$a401280a@.phx.gbl...
have
>
>.
>
|||> How would I switch to the OLEDB method?
That really depends... what application/language are you using for the
client applications?

> Also, I found that the ODBC Driver versions are different
> on the client machines. Would I need to update the
> clients to the new version?
Yes, apply the latest MDAC all around. You should try to avoid mismatched
versions between client and server.
http://www.microsoft.com/downloads/d...DisplayLang=en
http://www.aspfaq.com/
(Reverse address to reply.)
|||Installing the MDAC results in the same SQL Server does
not exist error.
All of the clients are using Windows XP Pro to connect to
the SQL Server.

>--Original Message--
>That really depends... what application/language are you
using for the[vbcol=seagreen]
>client applications?
different
>Yes, apply the latest MDAC all around. You should try to
avoid mismatched
>versions between client and server.
>http://www.microsoft.com/downloads/details.aspx?
FamilyID=6c050fe3-c795-4b7d-b037-
185d0506396c&DisplayLang=en
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
|||> All of the clients are using Windows XP Pro to connect to
> the SQL Server.
That's the operating system, but it doesn't tell me anything about the
application that is attempting to make a connection. Are you trying to
connect from Excel, notepad, ColdFusion, Query Analyzer, the ODBC control
panel applet, ... ?
Have you gone through http://support.microsoft.com/?kbid=328306 ?
http://www.aspfaq.com/
(Reverse address to reply.)
|||I'm trying to connect from the ODBC Control Panel.
Yes, I have through the 328306 article and haven't found
any resolutions.
Would the easiest thing to do be revert back to Windows
2000 when this all worked correctly?
[vbcol=seagreen]
>--Original Message--
to
>That's the operating system, but it doesn't tell me
anything about the
>application that is attempting to make a connection. Are
you trying to
>connect from Excel, notepad, ColdFusion, Query Analyzer,
the ODBC control
>panel applet, ... ?
>Have you gone through http://support.microsoft.com/?
kbid=328306 ?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>
|||> I'm trying to connect from the ODBC Control Panel.
Why? And then what are you going to do with it once you've connected?
Typically this is used to create a DSN for some other application, like an
ASP page or VB app. In which case, you are much better off connecting
through OLEDB. I can't tell you how to do that until you provide more
information.

> Yes, I have through the 328306 article and haven't found
> any resolutions.
Can you tell us what you tried, with regard to each article listed at that
link? I'm guessing you didn't inspect every single article listed there,
since it has been less than an hour, and you'd have to be Number 5 from
Short Circuit to have read all of the content already.

> Would the easiest thing to do be revert back to Windows
> 2000 when this all worked correctly?
No, that's silly. Windows XP is not to blame; you have a configuration
issue, that's all. If you tell us everything you tried regarding 328306,
you will leave the remaining potential options.
http://www.aspfaq.com/
(Reverse address to reply.)
|||I need the DSN to run Crystal Reports.
As for KB #328306, I tried everything under the Server-
Related Causes. The protocols are all ok, port 1433 is
the same on each machine, and tried giving the server a
new alias.
As for the Client/App-Related Causes, the protocols don't
change, no network adaptor issues, not worried about MDAC
connections, and Named Pipes don't apply.
There was nothing applicable under the Network Causes as
everything is run locally.

>--Original Message--
>Why? And then what are you going to do with it once
you've connected?
>Typically this is used to create a DSN for some other
application, like an
>ASP page or VB app. In which case, you are much better
off connecting
>through OLEDB. I can't tell you how to do that until you
provide more
>information.
>
>Can you tell us what you tried, with regard to each
article listed at that
>link? I'm guessing you didn't inspect every single
article listed there,
>since it has been less than an hour, and you'd have to be
Number 5 from
>Short Circuit to have read all of the content already.
>
>No, that's silly. Windows XP is not to blame; you have a
configuration
>issue, that's all. If you tell us everything you tried
regarding 328306,
>you will leave the remaining potential options.
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>
|||So what name are you using to refer to the local server? Have you tried
"LOCALHOST", "(LOCAL)", "127.0.0.1", the actual server name, the actual IP
address?
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:199ec01c44d7f$b2851cf0$a301280a@.phx.gbl...[vbcol=seagreen]
> I need the DSN to run Crystal Reports.
> As for KB #328306, I tried everything under the Server-
> Related Causes. The protocols are all ok, port 1433 is
> the same on each machine, and tried giving the server a
> new alias.
> As for the Client/App-Related Causes, the protocols don't
> change, no network adaptor issues, not worried about MDAC
> connections, and Named Pipes don't apply.
> There was nothing applicable under the Network Causes as
> everything is run locally.
> you've connected?
> application, like an
> off connecting
> provide more
> article listed at that
> article listed there,
> Number 5 from
> configuration
> regarding 328306,

ODBC connection failure

After upgrading to Windows 2003 Server, I can no longer
access SQL Server via ODBC. It says the SQL Server
doesn't exist or access denied. None of the settings have
changed after the upgrade.
Is there a fix to this?
Thanks in advance.(a) stop using ODBC, it's been deprecated. OLEDB is much preferred.
(b) SQL Server authentication? Windows authentication? What is the
username you are using? What kind of account is it? Have you tried a
different authentication method and/or a different user?
(c) http://support.microsoft.com/?kbid=328306
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:19b9c01c44d6d$b0030b20$a401280a@.phx.gbl...
> After upgrading to Windows 2003 Server, I can no longer
> access SQL Server via ODBC. It says the SQL Server
> doesn't exist or access denied. None of the settings have
> changed after the upgrade.
> Is there a fix to this?
> Thanks in advance.|||How would I switch to the OLEDB method? It's SQL Server
auth., and also tried different methods and users.
Also, I found that the ODBC Driver versions are different
on the client machines. Would I need to update the
clients to the new version?
>--Original Message--
>(a) stop using ODBC, it's been deprecated. OLEDB is much
preferred.
>(b) SQL Server authentication? Windows authentication?
What is the
>username you are using? What kind of account is it?
Have you tried a
>different authentication method and/or a different user?
>(c) http://support.microsoft.com/?kbid=328306
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"Mike" <anonymous@.discussions.microsoft.com> wrote in
message
>news:19b9c01c44d6d$b0030b20$a401280a@.phx.gbl...
>> After upgrading to Windows 2003 Server, I can no longer
>> access SQL Server via ODBC. It says the SQL Server
>> doesn't exist or access denied. None of the settings
have
>> changed after the upgrade.
>> Is there a fix to this?
>> Thanks in advance.
>
>.
>|||> How would I switch to the OLEDB method?
That really depends... what application/language are you using for the
client applications?
> Also, I found that the ODBC Driver versions are different
> on the client machines. Would I need to update the
> clients to the new version?
Yes, apply the latest MDAC all around. You should try to avoid mismatched
versions between client and server.
http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&DisplayLang=en
--
http://www.aspfaq.com/
(Reverse address to reply.)|||Installing the MDAC results in the same SQL Server does
not exist error.
All of the clients are using Windows XP Pro to connect to
the SQL Server.
>--Original Message--
>> How would I switch to the OLEDB method?
>That really depends... what application/language are you
using for the
>client applications?
>> Also, I found that the ODBC Driver versions are
different
>> on the client machines. Would I need to update the
>> clients to the new version?
>Yes, apply the latest MDAC all around. You should try to
avoid mismatched
>versions between client and server.
>http://www.microsoft.com/downloads/details.aspx?
FamilyID=6c050fe3-c795-4b7d-b037-
185d0506396c&DisplayLang=en
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)|||> All of the clients are using Windows XP Pro to connect to
> the SQL Server.
That's the operating system, but it doesn't tell me anything about the
application that is attempting to make a connection. Are you trying to
connect from Excel, notepad, ColdFusion, Query Analyzer, the ODBC control
panel applet, ... ?
Have you gone through http://support.microsoft.com/?kbid=328306 ?
--
http://www.aspfaq.com/
(Reverse address to reply.)|||I'm trying to connect from the ODBC Control Panel.
Yes, I have through the 328306 article and haven't found
any resolutions.
Would the easiest thing to do be revert back to Windows
2000 when this all worked correctly?
>--Original Message--
>> All of the clients are using Windows XP Pro to connect
to
>> the SQL Server.
>That's the operating system, but it doesn't tell me
anything about the
>application that is attempting to make a connection. Are
you trying to
>connect from Excel, notepad, ColdFusion, Query Analyzer,
the ODBC control
>panel applet, ... ?
>Have you gone through http://support.microsoft.com/?
kbid=328306 ?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>|||> I'm trying to connect from the ODBC Control Panel.
Why? And then what are you going to do with it once you've connected?
Typically this is used to create a DSN for some other application, like an
ASP page or VB app. In which case, you are much better off connecting
through OLEDB. I can't tell you how to do that until you provide more
information.
> Yes, I have through the 328306 article and haven't found
> any resolutions.
Can you tell us what you tried, with regard to each article listed at that
link? I'm guessing you didn't inspect every single article listed there,
since it has been less than an hour, and you'd have to be Number 5 from
Short Circuit to have read all of the content already.
> Would the easiest thing to do be revert back to Windows
> 2000 when this all worked correctly?
No, that's silly. Windows XP is not to blame; you have a configuration
issue, that's all. If you tell us everything you tried regarding 328306,
you will leave the remaining potential options.
--
http://www.aspfaq.com/
(Reverse address to reply.)|||I need the DSN to run Crystal Reports.
As for KB #328306, I tried everything under the Server-
Related Causes. The protocols are all ok, port 1433 is
the same on each machine, and tried giving the server a
new alias.
As for the Client/App-Related Causes, the protocols don't
change, no network adaptor issues, not worried about MDAC
connections, and Named Pipes don't apply.
There was nothing applicable under the Network Causes as
everything is run locally.
>--Original Message--
>> I'm trying to connect from the ODBC Control Panel.
>Why? And then what are you going to do with it once
you've connected?
>Typically this is used to create a DSN for some other
application, like an
>ASP page or VB app. In which case, you are much better
off connecting
>through OLEDB. I can't tell you how to do that until you
provide more
>information.
>> Yes, I have through the 328306 article and haven't found
>> any resolutions.
>Can you tell us what you tried, with regard to each
article listed at that
>link? I'm guessing you didn't inspect every single
article listed there,
>since it has been less than an hour, and you'd have to be
Number 5 from
>Short Circuit to have read all of the content already.
>> Would the easiest thing to do be revert back to Windows
>> 2000 when this all worked correctly?
>No, that's silly. Windows XP is not to blame; you have a
configuration
>issue, that's all. If you tell us everything you tried
regarding 328306,
>you will leave the remaining potential options.
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>|||So what name are you using to refer to the local server? Have you tried
"LOCALHOST", "(LOCAL)", "127.0.0.1", the actual server name, the actual IP
address?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:199ec01c44d7f$b2851cf0$a301280a@.phx.gbl...
> I need the DSN to run Crystal Reports.
> As for KB #328306, I tried everything under the Server-
> Related Causes. The protocols are all ok, port 1433 is
> the same on each machine, and tried giving the server a
> new alias.
> As for the Client/App-Related Causes, the protocols don't
> change, no network adaptor issues, not worried about MDAC
> connections, and Named Pipes don't apply.
> There was nothing applicable under the Network Causes as
> everything is run locally.
> >--Original Message--
> >> I'm trying to connect from the ODBC Control Panel.
> >
> >Why? And then what are you going to do with it once
> you've connected?
> >Typically this is used to create a DSN for some other
> application, like an
> >ASP page or VB app. In which case, you are much better
> off connecting
> >through OLEDB. I can't tell you how to do that until you
> provide more
> >information.
> >
> >> Yes, I have through the 328306 article and haven't found
> >> any resolutions.
> >
> >Can you tell us what you tried, with regard to each
> article listed at that
> >link? I'm guessing you didn't inspect every single
> article listed there,
> >since it has been less than an hour, and you'd have to be
> Number 5 from
> >Short Circuit to have read all of the content already.
> >
> >> Would the easiest thing to do be revert back to Windows
> >> 2000 when this all worked correctly?
> >
> >No, that's silly. Windows XP is not to blame; you have a
> configuration
> >issue, that's all. If you tell us everything you tried
> regarding 328306,
> >you will leave the remaining potential options.
> >
> >--
> >http://www.aspfaq.com/
> >(Reverse address to reply.)
> >
> >
> >.
> >|||The actual server name is what I'm using.
>--Original Message--
>So what name are you using to refer to the local server?
Have you tried
>"LOCALHOST", "(LOCAL)", "127.0.0.1", the actual server
name, the actual IP
>address?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"Mike" <anonymous@.discussions.microsoft.com> wrote in
message
>news:199ec01c44d7f$b2851cf0$a301280a@.phx.gbl...
>> I need the DSN to run Crystal Reports.
>> As for KB #328306, I tried everything under the Server-
>> Related Causes. The protocols are all ok, port 1433 is
>> the same on each machine, and tried giving the server a
>> new alias.
>> As for the Client/App-Related Causes, the protocols
don't
>> change, no network adaptor issues, not worried about
MDAC
>> connections, and Named Pipes don't apply.
>> There was nothing applicable under the Network Causes as
>> everything is run locally.
>> >--Original Message--
>> >> I'm trying to connect from the ODBC Control Panel.
>> >
>> >Why? And then what are you going to do with it once
>> you've connected?
>> >Typically this is used to create a DSN for some other
>> application, like an
>> >ASP page or VB app. In which case, you are much better
>> off connecting
>> >through OLEDB. I can't tell you how to do that until
you
>> provide more
>> >information.
>> >
>> >> Yes, I have through the 328306 article and haven't
found
>> >> any resolutions.
>> >
>> >Can you tell us what you tried, with regard to each
>> article listed at that
>> >link? I'm guessing you didn't inspect every single
>> article listed there,
>> >since it has been less than an hour, and you'd have to
be
>> Number 5 from
>> >Short Circuit to have read all of the content already.
>> >
>> >> Would the easiest thing to do be revert back to
Windows
>> >> 2000 when this all worked correctly?
>> >
>> >No, that's silly. Windows XP is not to blame; you
have a
>> configuration
>> >issue, that's all. If you tell us everything you tried
>> regarding 328306,
>> >you will leave the remaining potential options.
>> >
>> >--
>> >http://www.aspfaq.com/
>> >(Reverse address to reply.)
>> >
>> >
>> >.
>> >
>
>.
>|||So, try the others...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:199f801c44d81$97deaf90$a301280a@.phx.gbl...
> The actual server name is what I'm using.
> >--Original Message--
> >So what name are you using to refer to the local server?
> Have you tried
> >"LOCALHOST", "(LOCAL)", "127.0.0.1", the actual server
> name, the actual IP
> >address?
> >
> >--
> >http://www.aspfaq.com/
> >(Reverse address to reply.)
> >
> >
> >
> >
> >"Mike" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:199ec01c44d7f$b2851cf0$a301280a@.phx.gbl...
> >> I need the DSN to run Crystal Reports.
> >>
> >> As for KB #328306, I tried everything under the Server-
> >> Related Causes. The protocols are all ok, port 1433 is
> >> the same on each machine, and tried giving the server a
> >> new alias.
> >>
> >> As for the Client/App-Related Causes, the protocols
> don't
> >> change, no network adaptor issues, not worried about
> MDAC
> >> connections, and Named Pipes don't apply.
> >>
> >> There was nothing applicable under the Network Causes as
> >> everything is run locally.
> >>
> >> >--Original Message--
> >> >> I'm trying to connect from the ODBC Control Panel.
> >> >
> >> >Why? And then what are you going to do with it once
> >> you've connected?
> >> >Typically this is used to create a DSN for some other
> >> application, like an
> >> >ASP page or VB app. In which case, you are much better
> >> off connecting
> >> >through OLEDB. I can't tell you how to do that until
> you
> >> provide more
> >> >information.
> >> >
> >> >> Yes, I have through the 328306 article and haven't
> found
> >> >> any resolutions.
> >> >
> >> >Can you tell us what you tried, with regard to each
> >> article listed at that
> >> >link? I'm guessing you didn't inspect every single
> >> article listed there,
> >> >since it has been less than an hour, and you'd have to
> be
> >> Number 5 from
> >> >Short Circuit to have read all of the content already.
> >> >
> >> >> Would the easiest thing to do be revert back to
> Windows
> >> >> 2000 when this all worked correctly?
> >> >
> >> >No, that's silly. Windows XP is not to blame; you
> have a
> >> configuration
> >> >issue, that's all. If you tell us everything you tried
> >> regarding 328306,
> >> >you will leave the remaining potential options.
> >> >
> >> >--
> >> >http://www.aspfaq.com/
> >> >(Reverse address to reply.)
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >

obsolete subscriptions still exist

Hi everyone,
I disabled replication on my local sql server. I would assume publication and subscription folder will be empty after I refresh Enterprise Manager. however that's not the case.
Publication folder is empty after I disabled replication, but subscription folder is not empty, what is going on?
I kept refresh subscription folder under 'replication', I can't get rid of those subscriptions? how can I get rid of them?
thanks
Kevin
Please try running sp_removedbreplication in the relevant databases.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Objects related to DB

Hi Folks,
I suppose should exist a way to find the relationship between all external
objects (logins, dts, jobs, ...) with one database. I mean, the objects
related\attached with database.
That is because we have to take off several databases including objects
related.
Of course we have the respective documentation of the relationships but in
the past several engineers did mistakes and they missed the removement of
some object related...So, we got sql server with dirty objects.
The idea is to make a kind of script that checks all external objects
related to database before to delete it.
Thanks in advance.HI ,
You could try a documentation tool like my SQL Scribe Documentation Builder.
There a 14 day trial . Document the entire system , the documentation
details logins, jobs and other server elements as well as the schema details
http://www.geckoware.com.au/Content.aspx?Doc_id=1001
-
Greg O
SQL Server Documentation the easy way
SQL 2000, SQL 2005 the best is back
http://www.geckoware.com.au/Content.aspx?Doc_id=1001
"Jaisol" <jaisol@.QUITARMEhotmail.com> wrote in message
news:eNYZB%23WrHHA.4180@.TK2MSFTNGP04.phx.gbl...
> Hi Folks,
> I suppose should exist a way to find the relationship between all external
> objects (logins, dts, jobs, ...) with one database. I mean, the objects
> related\attached with database.
> That is because we have to take off several databases including objects
> related.
> Of course we have the respective documentation of the relationships but in
> the past several engineers did mistakes and they missed the removement of
> some object related...So, we got sql server with dirty objects.
> The idea is to make a kind of script that checks all external objects
> related to database before to delete it.
> Thanks in advance.
>

Objects related to DB

Hi Folks,
I suppose should exist a way to find the relationship between all external
objects (logins, dts, jobs, ...) with one database. I mean, the objects
related\attached with database.
That is because we have to take off several databases including objects
related.
Of course we have the respective documentation of the relationships but in
the past several engineers did mistakes and they missed the removement of
some object related...So, we got sql server with dirty objects.
The idea is to make a kind of script that checks all external objects
related to database before to delete it.
Thanks in advance.HI ,
You could try a documentation tool like my SQL Scribe Documentation Builder.
There a 14 day trial . Document the entire system , the documentation
details logins, jobs and other server elements as well as the schema details
http://www.geckoware.com.au/Content.aspx?Doc_id=1001
-
Greg O
SQL Server Documentation the easy way
SQL 2000, SQL 2005 the best is back
http://www.geckoware.com.au/Content.aspx?Doc_id=1001
"Jaisol" <jaisol@.QUITARMEhotmail.com> wrote in message
news:eNYZB%23WrHHA.4180@.TK2MSFTNGP04.phx.gbl...
> Hi Folks,
> I suppose should exist a way to find the relationship between all external
> objects (logins, dts, jobs, ...) with one database. I mean, the objects
> related\attached with database.
> That is because we have to take off several databases including objects
> related.
> Of course we have the respective documentation of the relationships but in
> the past several engineers did mistakes and they missed the removement of
> some object related...So, we got sql server with dirty objects.
> The idea is to make a kind of script that checks all external objects
> related to database before to delete it.
> Thanks in advance.
>