Oh this is getting beyond a joke...

  • Thread starter Thread starter Heidi Linda
  • Start date Start date
H

Heidi Linda

I have been battling my *&*(^£$ database all day. I have finally got to
the stage of trying to install the thing on SQL server for the second
time. This time, it won't work. No matter where I try to install it, I get:

An ERROR occurred while attaching the database to SQL server, file
$path\MantisSQLDB_Data.mdf, message:
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not open new
database 'MantisSQLDB'. CREATE DATABASE is aborted.
[Microsoft][ODBC SQL Server Driver][SQL Server]Device activation error.
The physical file name 'e:\windows embedded data\MantisSQLDB_log.LDF'
may be incorrect.

Alright, I thought, let's install you on e: then, even though that's
inconvenient. I'll live with it. It still does it.
And light that can be shed on this would be appreciated.
 
Hi Heidi-
In Enterprise Manager - is there already a "MantisSQLDB" database listed
for the SQL Server? If there is then that could easily explain why you
cannot install the database anywhere on the machine.

Hopefully this is the issue. I'll try to think of anything else just in
case that wasn't the resolution.

Cheers. :)
 
No. There isn't. That was the first thing I checked. There was one, but
I got rid of it.
 
Just so you know, you cannot use a network drive with SQL. The drive (C, D,
E) must be a local disk drive, it cannot be mapped to some remote filesystem.
A major deficiency of MSSQL.

TBiker

Nick Nehrhood /MSFT/ said:
Hi Heidi-
In Enterprise Manager - is there already a "MantisSQLDB" database listed
for the SQL Server? If there is then that could easily explain why you
cannot install the database anywhere on the machine.

Hopefully this is the issue. I'll try to think of anything else just in
case that wasn't the resolution.

Cheers. :)
--
Nick Nehrhood
(Windows Embedded Group)

Embedded team blog: http://blogs.msdn.com/embedded/
---
This posting is provided "AS IS" with no warranties, and confers no rights.
_____________________________________

Heidi Linda said:
I have been battling my *&*(^£$ database all day. I have finally got to the
stage of trying to install the thing on SQL server for the second time.
This time, it won't work. No matter where I try to install it, I get:

An ERROR occurred while attaching the database to SQL server, file
$path\MantisSQLDB_Data.mdf, message:
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not open new database
'MantisSQLDB'. CREATE DATABASE is aborted.
[Microsoft][ODBC SQL Server Driver][SQL Server]Device activation error.
The physical file name 'e:\windows embedded data\MantisSQLDB_log.LDF' may
be incorrect.

Alright, I thought, let's install you on e: then, even though that's
inconvenient. I'll live with it. It still does it.
And light that can be shed on this would be appreciated.
Click to expand...
Click to expand...
 
TBiker said:
Just so you know, you cannot use a network drive with SQL. The drive (C, D,
E) must be a local disk drive, it cannot be mapped to some remote filesystem.
A major deficiency of MSSQL.
Click to expand...
I can't really see a situation in which I would want my database to be
slow and flaky, but still. It is not a network drive.
 
Also - why is it looking on e: when I was trying to install to c: ?
Hi Heidi-
In Enterprise Manager - is there already a "MantisSQLDB" database listed
for the SQL Server? If there is then that could easily explain why you
cannot install the database anywhere on the machine.

Hopefully this is the issue. I'll try to think of anything else just in
case that wasn't the resolution.

Cheers. :)
--
Nick Nehrhood
(Windows Embedded Group)

Embedded team blog: http://blogs.msdn.com/embedded/
---
This posting is provided "AS IS" with no warranties, and confers no rights.
_____________________________________

Heidi Linda said:
I have been battling my *&*(^£$ database all day. I have finally got to the
stage of trying to install the thing on SQL server for the second time.
This time, it won't work. No matter where I try to install it, I get:

An ERROR occurred while attaching the database to SQL server, file
$path\MantisSQLDB_Data.mdf, message:
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not open new database
'MantisSQLDB'. CREATE DATABASE is aborted.
[Microsoft][ODBC SQL Server Driver][SQL Server]Device activation error.
The physical file name 'e:\windows embedded data\MantisSQLDB_log.LDF' may
be incorrect.

Alright, I thought, let's install you on e: then, even though that's
inconvenient. I'll live with it. It still does it.
And light that can be shed on this would be appreciated.
Click to expand...
Click to expand...
 
I can't really see a situation in which I would want my database to be
slow and flaky, but still. It is not a network drive.
Click to expand...

Also, there are certain file I/O APIs that don't work against networked
drives. If I had to vote between "local and fast" or "flexible but slow"
I'd vote for the former. :-)
 
Nick said:
Hi Heidi-
In Enterprise Manager - is there already a "MantisSQLDB" database listed
for the SQL Server? If there is then that could easily explain why you
cannot install the database anywhere on the machine.

Hopefully this is the issue. I'll try to think of anything else just in
case that wasn't the resolution.

Cheers. :)
Click to expand...

I have, finally sorted this out. I'd forgotten to cut my hand on the
case of the Dell to give my demonic workstation the required sacrifice.
Seriously, this is what needed doing:

Uninstall XPe.
Uninstall SQL Server.
Trawl the registry looking for anything related to XPe or the mantis
database. Kill.
Reinstall everything.
 
Back
Top