Guest_imported
New member
- Jan 1, 1970
- 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!!!!
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!!!!