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 Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem installing SQL Server 7

Status
Not open for further replies.

Jenns

Programmer
Nov 1, 2000
36
US
Hello out there!

I am trying to install SQL Server7 on a PC. The PC had SQL 7 installed before, but had to be re-cloned. The message I receive on the install is: ODBC components on your system need to be updated but one or more files are in use or marked as read only. Close all applications and retry. A reboot my be necessary.. blah blah blah.

There are no applications open and I don't know what else may be using ODBC components. The only thing different (that I Know of) on this PC is that the person now uses an IBM workpad. (For those who aren't familiar, it is a little hand held gadget that can download or upload information to/from a PC.) Is it possible that the Workpad or it's software somehow uses ODBC drivers? The Workpad was not connected to the PC when I tried to install.

Any other suggestions on where to look would be helpful.

Thanks,
Jenn
 
Quite often things like the workpad have a small app running looking for commands from them (even if the thing isn't plugged in or running) have you got any icon's related to it in your System Tray (next to your clock) if so close them down and try again. Failing that, try hitting the Microsoft site for the latest Microsoft Data Access Components pack, it's generally not so particular about installing when ODBC's are in use. Then re-run your SQL install.......

Virgil
 
OOoh and another thing.....

the only other thing I can think of is to stick a trace on the ODBC. It sometimes gives you useful indications as to the source of any ODBC conversations. To turn tracing on do:

Start -> Settings -> Control Panel

then select the ODBC icon (sometimes called Data Sources depending on what version MDAC your using) and there is a tab in there for tracing. Run the tracing and try your SQL install.......

See how that goes,

Virgil
 
Virgil,

Following your first suggestion, I stopped all services, tried the install and it completed. That was they key. Thanks!

It's good to know how to do the trace also. If something similiar happens again, I'll be able to tell what in particular is the source of the problem.

Thank you for sharing your knowledge. :)

Jenn
 
FYI,

Don't forget to turn the tracing off after you use it. It is very easy to forget and next thing you know you run out of space on your c drive (default location for tracing sql.log file).

JB
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top