Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Urgent! Cannot write to any sql server 6.5 db

Status
Not open for further replies.

Guest_imported

New member
Joined
Jan 1, 1970
Messages
0
We are running SQL server 6.5 on 3 win NT4 boxes. Box 1 is a live database, box 2 is a reporting database that contains the previous day's database, box 3 contains friday of the week before (training database).

On ALL databases, our front-end client CANNOT write to the database but CAN read to it. We're stumped, as the problem has occurred after 1 hour of this working day (logically, the training db is a copy from last week, therefore the whole thing should've been down for a whole week)

The front-end client hasn't changed, has been restored from backups, as has the main database. We can still read but not write on all 3 boxes. If you get in via ISQL_w, you CAN right. Both use OLE connections.

There are NO error messages on ANY of the boxes. There is plenty of diskspace on ALL boxes. The problem is repeated on all segments of the LAN and WAN. None of the NT permissions have changed. All boxes can be connected to via ISQL_w.

This is our mission critical app, and we're STUMPED!!!!
 
If you are saying you can still do updates via an ISQL window then I would start looking at your App and how it connects to your databases.

I know you mentioned nothing has changed in this area but that's where my instinct is pointing me.

Do you not get an error message from within you client app when it tries to do an update or does it appear to work but no update takes place??

Rick.

 
Users can view the data, but when they amend it and save the data they get:

"System error: undefined application error".
So I too, would suspect a client problem at this point.

However, the set-up is like this; each segment of the WAN has a server that contains a copy of the client, ALL users connect via that client, and hence there are at least 10 different copies that have simultaneously corrupted???? (I running a virus scan just in case)there is no copying schedule for the clients .exe's.

The network seems fine. Unfortunately the client is proprietary and we have not been given source, or even how it connects directly to the server. I am now investigating this thru the dll's installed etc, but this could take some time! Eeek! :-/

Ric (as well!)



 
...now it appears that users from one domain CAN write to the DB. The plot thickens...
 
Looks like one of them horrible problems where something has been changed but no one is owning up!!

Just a thought but has anyone been messing around with your NT Trust relationships between Domains. Although I don't think that would affect your database access.

Sorry can't be of more help at the moment but if you come across any thing else put another post in.

Rick.
 
Thanks for the help. We went for a reboot and took the backup servers off the network. It's working fine now.

Just one of them things, I suppose!

Thanks for the help anyhow!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top