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,
Showing posts with label upgrading. Show all posts
Showing posts with label upgrading. Show all posts
Wednesday, March 21, 2012
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,
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.)
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >
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.)
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >
Wednesday, March 7, 2012
Obtaining Snapsot via FTP using SQL Express client
Hi All,
I really need some help here! I have spent the last few days upgrading a clients system to SQL 2005, part of which involved upgrading their sales people's laptops to Sql 2005 Express and setting up Merge Replication. I have configured the Server to use Web Synchronisation, and have tested that the replisapi.dll?diag all works ok and it does.
I am running into problems now with getting the laptops to synchronise. I have set up the Replication task, and am getting an error when I run the Wndows Synchroniser:
====================
The schema script '\\PTC42\ParklandsWebsiteV2\ftp\PTC42_PARKLANDS_PARKLANDS\20060812131209\' could not be propagated to the subscriber.
The process could not connect to FTP site 'mail.parklands.net' using port 21.
A connection with the server could not be established
==============
I have tested independantly connecting to the FTP server using Windows explorer and it works fine using the same username and password. I am at a loss here!!! I am going in circles looking for help too as there doesnt seem to be much info on this in SQL 2005 yet. I have re-read all the books online articles for Replication, Replication in SQL 2005 Express, and also gone back & reset up the Server & the Client several times - with no luck!
The client needs to get these sales guys laptops back ASAP and I am starting to really stress out here!! (can you tell I havent had much sleep in the last few days?) Any help would be so wonderfully apreciated!!!
Thanks so very much,
Catherine
Well I have FINALLY worked it out - and thought I would post my findings to help others that may run into the same problem.
I ran ftp using command prompt and all connected fine so I knew it wasnt the FTP side of things.
I set up the same replication on another machine and received the same error so that meant it was a config probem & not a problem specific to the laptop i was working on.
I ran replmerge.exe via the command prompt and received the same error message - after much testing & trying & playng with settings I realised that the setting I was entering for FTP address werent being used - the setting on the SQL server Publication were being used. It then occurred to me that the Mail.parklands.net address was an external address and perhaps the machine hosting the IIS component of the Web Sync may not be able to map that address. When I tested this on the IIS server I received the same message. I changed this connection path to the internal machine name - and could connect!! i changed this setting in the SQL publication & rebuilt the Snapshot. I then added the PTC42 machine name to my hosts file and tested I could FTP into that locally using the command prompt. When that all worked i tested the replmerge.exe via the ocmmand prompt once again and I am very happy to report that my DB is now synchronising!! :)
So in summary - ensure when you set up your FTP server for the snapshot of a Replicated database that the IIS server that is hosting the Web Synch can access that exact name - keeping in mind internal & external server names.
I am happy to be corrected on this (my explination & terminology may be way off) - but am breathing a sigh of relief as it seems to be working now!
Thanks,
Catherine
Subscribe to:
Posts (Atom)