By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,836 Members | 1,876 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,836 IT Pros & Developers. It's quick & easy.

Problems Accessing New MSDE

P: n/a
Help!

I just upgraded MSDE to the latest version on my Windows 2000 server.
Everything appears to work fine - the enterprise manager on both the server
and on my computer are able to access the new database and I have loaded it
with all of its data using the enterprise manager. (Actually I've completed
the entire cycle three times!)

The catch is that my VB.NET web application is no longer able to access the
database! I'm using the same connection string as before.

I have a VB.NET client program that CAN access the database with no problems
at all.

I've posted this question in the MSDE forum - I'm hoping that others have
already faced this issue and found a solution!

Also: Is there a way to determine why my calls to stored procedures are
failing - perhaps this would help!

Any help would be GREATLY appreciated!

Thanks,

Fred
Nov 21 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
By default, networking is disabled in the latest vesions of MSDE. See the
readme file for instructions for how to enable networking and assign the SA
password.

It can be done by hacking the registry and stopping/starting mssqlserver.
Search Google. There are probly other ways as well.

"Fred Nelson" <fr**@smartybird.com> wrote in message
news:OR**************@tk2msftngp13.phx.gbl...
Help!

I just upgraded MSDE to the latest version on my Windows 2000 server.
Everything appears to work fine - the enterprise manager on both the
server
and on my computer are able to access the new database and I have loaded
it
with all of its data using the enterprise manager. (Actually I've
completed
the entire cycle three times!)

The catch is that my VB.NET web application is no longer able to access
the
database! I'm using the same connection string as before.

I have a VB.NET client program that CAN access the database with no
problems
at all.

I've posted this question in the MSDE forum - I'm hoping that others have
already faced this issue and found a solution!

Also: Is there a way to determine why my calls to stored procedures are
failing - perhaps this would help!

Any help would be GREATLY appreciated!

Thanks,

Fred

Nov 21 '05 #2

P: n/a
Hi Jim:

I have enabled network protocols and I can access my SQL-MSDE from the
enterprise manager both on the server itself and from my computer.
Additionally I can access it from a remote VB.NET client program.

I can't access it from the web server that is also running on the same
machine.

Also: I have set up two other machines in the same way and the work fine!

So: I'm very confused - I haven't found many articles on google that are
helpful.

If you have any suggestions I would greatly appreciate it.

Thanks,

Fred
"Jim Hughes" <NO*********@Hotmail.com> wrote in message
news:eA**************@TK2MSFTNGP10.phx.gbl...
By default, networking is disabled in the latest vesions of MSDE. See the
readme file for instructions for how to enable networking and assign the SA password.

It can be done by hacking the registry and stopping/starting mssqlserver.
Search Google. There are probly other ways as well.

"Fred Nelson" <fr**@smartybird.com> wrote in message
news:OR**************@tk2msftngp13.phx.gbl...
Help!

I just upgraded MSDE to the latest version on my Windows 2000 server.
Everything appears to work fine - the enterprise manager on both the
server
and on my computer are able to access the new database and I have loaded
it
with all of its data using the enterprise manager. (Actually I've
completed
the entire cycle three times!)

The catch is that my VB.NET web application is no longer able to access
the
database! I'm using the same connection string as before.

I have a VB.NET client program that CAN access the database with no
problems
at all.

I've posted this question in the MSDE forum - I'm hoping that others have already faced this issue and found a solution!

Also: Is there a way to determine why my calls to stored procedures are
failing - perhaps this would help!

Any help would be GREATLY appreciated!

Thanks,

Fred


Nov 21 '05 #3

P: n/a
Hey Jim:

Just a follow up: I found that something in the MSDE installation "hosed"
my default web site - no idea what it was. To fix it I temporarily made
another site my default, deleted the programs, re-installed and life is good
again!

I put the "old" msde back on the system and it still didn't work so I tried
this.

Now the next step is to install the new MSDE again and know that I will need
to redeploy the program.

Hope this helps you sometime in the future!

Fred

"Jim Hughes" <NO*********@Hotmail.com> wrote in message
news:eA**************@TK2MSFTNGP10.phx.gbl...
By default, networking is disabled in the latest vesions of MSDE. See the
readme file for instructions for how to enable networking and assign the SA password.

It can be done by hacking the registry and stopping/starting mssqlserver.
Search Google. There are probly other ways as well.

"Fred Nelson" <fr**@smartybird.com> wrote in message
news:OR**************@tk2msftngp13.phx.gbl...
Help!

I just upgraded MSDE to the latest version on my Windows 2000 server.
Everything appears to work fine - the enterprise manager on both the
server
and on my computer are able to access the new database and I have loaded
it
with all of its data using the enterprise manager. (Actually I've
completed
the entire cycle three times!)

The catch is that my VB.NET web application is no longer able to access
the
database! I'm using the same connection string as before.

I have a VB.NET client program that CAN access the database with no
problems
at all.

I've posted this question in the MSDE forum - I'm hoping that others have already faced this issue and found a solution!

Also: Is there a way to determine why my calls to stored procedures are
failing - perhaps this would help!

Any help would be GREATLY appreciated!

Thanks,

Fred


Nov 21 '05 #4

P: n/a
What type of authentication do you use in your web server.
If you use SQL authentication, maybe your MSDE is only configured to use
Windows auth. If so look at the readme how to enable it.
"Fred Nelson" <fr**@smartybird.com> wrote in message
news:OR**************@tk2msftngp13.phx.gbl...
Help!

I just upgraded MSDE to the latest version on my Windows 2000 server.
Everything appears to work fine - the enterprise manager on both the
server
and on my computer are able to access the new database and I have loaded
it
with all of its data using the enterprise manager. (Actually I've
completed
the entire cycle three times!)

The catch is that my VB.NET web application is no longer able to access
the
database! I'm using the same connection string as before.

I have a VB.NET client program that CAN access the database with no
problems
at all.

I've posted this question in the MSDE forum - I'm hoping that others have
already faced this issue and found a solution!

Also: Is there a way to determine why my calls to stored procedures are
failing - perhaps this would help!

Any help would be GREATLY appreciated!

Thanks,

Fred

Nov 21 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.