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.
| Author |
Topic |
|
rustyw
Starting Member
3 Posts |
 Posted - 2007-05-31 : 22:04:13
|
| Hi,We tried to create a new database on an application server (Win 2003 server/SQL Server 2003) and got the following error.error 945........device activation error. The physical filename g:\mssqldata\templog.ldf may be incorrect. The interesting thing is that tempdb is on f:\mssql as shown in the database properties and with sp_dbhelp.Poking around in master the real wierdness comes through. sysaltfiles has 2 entries each for tempdb logs and data files. One of them is on g: and one is on f:. The lower dbid is on f: and the higher one is on g: (actually the last two rows in the table).Several months ago our software vendor moved tempdb from g: to f: to try and speed it up a bit. Appearantly they messed it up and now have written us off till WE fix it. The entries in sysaltfiles were the only references to g: that turned up (though we didn't look at every table and aren't even remotely sure where other references might be located).Any pointers on getting this corrected would be greatly apprecieated. We thought about trying a reconfigure and restarting but I'm not real hopeful. We also thought about just updating the wrong entries to reflect the right locations but that smacks of kluge. Tangential wierdness is that while trying to isolate the source of g:\mssql in the error I found that in master.sysdevices the file location is e:\Program Files\Microsoft SQL Server\MSSQL\data\tempdb.mdf.I believe this is from the initial install then while configuring the server it got moved to g: then to f:. HELP!!!Thanks in advance for any input!Rusty |
|
|
rustyw
Starting Member
3 Posts |
Posted - 2007-05-31 : 22:24:41
|
oops. Just noticed I posted this for 2005 server. Sorry for the faux pas.  |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-05-31 : 22:43:35
|
| Try fix it with 'alter database' then restore sql. |
|
|
|
rustyw
Starting Member
3 Posts |
Posted - 2007-05-31 : 22:48:17
|
| I tried the alter database about 5 minutes ago per the ms kb article on moving tempdb. It made no changes to the rows referencing the g: drive. We can't restart it yet as there are users logged in. |
|
|
|
|
|
|
sysaltfiles wierdness