RE: Getting 5105 error when I try to attach database

From: Mark Miller (MarkMiller_at_discussions.microsoft.com)
Date: 12/21/04 

Date: Mon, 20 Dec 2004 22:59:01 -0800

I tried turning on trace flag 1807, like the article says, to turn off the
check SQL Server does to detect if I'm accessing a database file through a
network share, and I get the same error. I gave this a try because it seemed
to be in the ballpark of my problem, but I'm not trying to access the
database file over a network share anyway. It's on my computer's hard drive.
 Other than this bit of information in the article, nothing else in it seemed
relevant.

"surajits" wrote:

> Miller -
> Please go through the following link :-
> http://support.microsoft.com/default.aspx?scid=kb;en-us;304261
>
> Let me know if you where able to get the help for your problem.
>
> Regards
>
>
> "Mark Miller" wrote:
>
> > Here's what I did. I created a new database on SQL Server 2000, on a remote
> > server, using Enterprise Manager. I then exported some data from another
> > database (same instance) into my new database. I then detached the database
> > I created, and copied the .MDF and .LDF files to my machine.
> >
> > I've been trying to attach the .MDF and .LDF files, again using Enterprise
> > Manager (I'm also running SQL Server 2000). In EM, I tell it to Attach
> > Database... I give it the path to my .MDF and .LDF files, hit Verify, and
> > they verify (both the .MDF and .LDF file paths show up in the window,
> > checked). The problem comes when I hit OK. It gives me error 5105 (device
> > activation error), it gives the same path that I gave it, and says that the
> > filename may be wrong.
> >
> > I don't think this is a permissions problem, and I've checked whether any
> > other process has grabbed ahold of it, and there isn't any. So I'm not sure
> > what's wrong. Please help.
> >
> > Thanks.
> >

Relevant Pages

  • Re: Record-Locking
    ... It means that as soon as the front end opens, a connection is made to the ... created after Jet reads and deciphers the information from the database file ... Bury the back end file deep in the directory structure on a network ... Another Windows API ...
    (microsoft.public.access.security)
  • ODBC Connection with SQL Managed Provider
    ... on a "network drive". ... database using the Microsoft .NET Framework 1.1 Data Provider for SQL ... authorizing the user against a table in the SQL server database. ... for the app to display the "splash" screen (which is the first thing it does ...
    (microsoft.public.dotnet.framework.adonet)
  • RE: SQL Server 2005 64 bit on Window Server 2003 R2 64bit slow per
    ... even gone as far as swapping network cables and updating NIC card drivers to ... If the box itself checked out fine, then move on to runnign SQL Server on ... Perfmon, Disk I/O, Pages, Profiler traces, checked locks/blocks, long running ... slow on these boxes to me. ...
    (microsoft.public.sqlserver.setup)
  • Odd connection problem (proxy + internal)
    ... system and can not be placed facing the internet. ... that belongs to our network and also connects to this accounting ... DSN's) to our internal SQL server. ... by installing the Winsock proxy on the SQL server and mapping the ip ...
    (comp.databases.ms-sqlserver)
  • Re: What is the best way to administering two separate forests?
    ... Now that you mentioned a trust relationship, it actually makes sense to do ... development and SQL Server management for them. ... network and network resources i.e. Exchange, SQL Server, applications, etc. ... We will just have a separate logical network with a separate ...
    (microsoft.public.win2000.networking)