Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 SQL Server connection

Author  Topic 

TorreyKite
Starting Member

40 Posts

Posted - 2003-07-21 : 11:07:01
Overview: NT server 4.0, SQL Server 7(part of back office package)
VB6 app. Using ADO (being developed on an XP workstation)
Initialy I had no trouble connecting at all. I was able to retrieve data and display it on my UI with no problems.

But now I get a general networking error.

It all started when I attempted to change the servers Name and Workgroup. Thinking that I could simply change my connection string and re-register it in my SQL server enterprise manager.
Not so easy, somewhere along the way the server prompted me to run “setup” so, unable to find any other applicable setup I ran back office set up which I think may have re configured some things on my server and now I’m abit lost.

My hunch is that there is a service running on the server that is conflicting with my app. However I was able to register the SQL server via my workstations' enterprise manager. Here I’m able to make any changes to my DB just like normal. But my App still can’t see the server.

Any Ideas

Thanks in advance,

TK

X002548
Not Just a Number

15586 Posts

Posted - 2003-07-21 : 11:16:50
How are you connecting via the app? Are you the dba? Did the security setting change?

Are you registering the same as the connection string?



Brett

8-)
Go to Top of Page

TorreyKite
Starting Member

40 Posts

Posted - 2003-07-21 : 11:36:18
Yes I'm the DBA (2 man IT shop)

In my App i'm using an adodb.command to run various stored procedures on my server. I'm confident that the code works fine as I've been using it successfully for several weeks now.

m_DefaultConnectionString = "Provider=SQLOLEDB; Data Source=NT_APPLICATIONS; Initial Catalog=InfoTracDatabase; User ID=APPLICATION; Password="

Security: the Login that i'm using in my connection string matches that of the login in my sql server enterprise manager.

could there be another service running that would require authentication for access to the server itself?

TK

Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2003-07-21 : 11:48:02
Is anything working now?

Are you using SQL or NT Security?

Does anyone else have Access to the box.

(IT shop of 2? Do you also wash windows?)



Brett

8-)
Go to Top of Page

TorreyKite
Starting Member

40 Posts

Posted - 2003-07-21 : 12:15:05
What is working now is that from my workstation I can use "SQL Server Enterprise Manager" to see the SQL server including the intended database. I can edit the DB. So for that matter from my desktop i am able to connect to the DB.

When i test my VB App it freezes and says that there is a general network error. logicaly i would think that if my enterprise manager can connect my app should be able to connect too.

for SQL security it's only the logins that i mentioned previously,
for NT security could verywell be the problem but i don't know what to look for. I did not intentionaly change my NT security but this could have happened while I ran Back office setup.

I'm the only one with access to the box

(I haven't been asked to do windows yet but anything that plugs into the wall or might require a screwdriver is fairgame )

TK .


Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-07-21 : 12:18:31
If you change the name of the server, then you HAVE to run the SQL Server setup to fix it and also run sp_dropserver then sp_addserver. There is a Microsoft knowledge base article on this (just do search for it at support.microsoft.com). For SQL 2000, you don't have to run setup but you do run those two stored procedures still, but for 7.0 you have to run setup.

Tara
Go to Top of Page

TorreyKite
Starting Member

40 Posts

Posted - 2003-07-21 : 15:56:28
Thanks both of you guys,

I've tried your suggestions Tara and I think it's on target but still hasn't done the trick.

I ran sql setup from my original CD

executed both stored procedures as the faq #5 said

[url]http://support.microsoft.com/default.aspx?scid=kb;EN-US;195759 [/url]
as well as all the network utility stuff.


anyway I think I'm on the right track but not out of the woods yet.
I'll go over more thuroughly tomorrow. Again thank you Brett and Tara very much for your time, I really appreciate it.

TK

Go to Top of Page

TorreyKite
Starting Member

40 Posts

Posted - 2003-07-22 : 13:44:25
ok I'm still not making any headway on this.

If I were to uninstall SQL server then reinstall it. Would that do the trick? I'm sure it's abit more work than if the previous procedure worked but it's not and I'm willing to just do it the long way to get it done.

also what should I do to preserve the DB that I'm working on. will Uninstalling delete it? should I copy the files to somewhere else or is it better to use DTC to export it. I'm only care about preserving the structure of the DB not the data it'self.

Thanks for the help,

TK

Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-07-22 : 13:47:46
quote:

If I were to uninstall SQL server then reinstall it. Would that do the trick? I'm sure it's abit more work than if the previous procedure worked but it's not and I'm willing to just do it the long way to get it done.



Yes that should do the trick.

quote:

also what should I do to preserve the DB that I'm working on. will Uninstalling delete it? should I copy the files to somewhere else or is it better to use DTC to export it. I'm only care about preserving the structure of the DB not the data it'self.



Uninstalling it does not delete it, but you should always be safe than sorry. You can either run a backup or detach the database. Once the install is complete, you would then restore the database or attach it. Detaching it and then attaching it after the installation is the fastest and easiest way to do it. Both of these are discussed quite a bit on SQLTeam, so just do a search on them or read up on it in Books Online. The stored procedures are sp_detach_db and sp_attach_db/sp_attach_single_file_db. Also if you go the backup/restore method, just look up BACKUP DATABASE and RESTORE DATABASE.

Tara
Go to Top of Page

TorreyKite
Starting Member

40 Posts

Posted - 2003-07-22 : 13:58:54
Thanks
You guys rock

TK

Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2003-07-22 : 14:30:01
What else would expect from a

SQL Warrior Princess



Brett

8-)
Go to Top of Page
   

- Advertisement -