Re: Backup Issue! Interesting or weird - you decide!
From: venAdder (venAdder_at_discussions.microsoft.com)
Date: 12/11/04
- Next message: Adam Machanic: "Re: Locks - simple question"
- Previous message: jlybbert: "Passing large amounts of text to append to an NText field on the s"
- In reply to: John Bell: "Re: Backup Issue! Interesting or weird - you decide!"
- Next in thread: John Bell: "Re: Backup Issue! Interesting or weird - you decide!"
- Reply: John Bell: "Re: Backup Issue! Interesting or weird - you decide!"
- Reply: John Bell: "Re: Backup Issue! Interesting or weird - you decide!"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 11 Dec 2004 13:53:07 -0800
backup database statement does same thing
and dump has been working fine till now
and anyways the computer is not a network computer it is the same computer
on which server tries to backup . the reason why \\myserver\c$ is used is cuz
someone was too lazy to check in the app if the server is local or remote, so
let's not go there.\
The point is it has been working fine till date and it works fine still on a
number of other locations thruout US
what is service account?
"John Bell" wrote:
> Hi
>
> Has the SQL Server service account been changed to a non-administrator? The
> use of DUMP would imply SQL Server 6.5 or earlier and I don't know if shares
> were allowed in those versions as a device, if version 7 or later use backup
> instead.
>
> John
>
> "venAdder" <venAdder@discussions.microsoft.com> wrote in message
> news:9B67F0FE-B642-4353-87E9-D69266A300B4@microsoft.com...
> >I run this query in query analyzer
> > dump database MYDB to disk = '\\myserver\c$\temp.dat' with init
> >
> > 'I get following error.
> > Server: Msg 3202, Level 16, State 1, Line 1
> > Write on 'c:\temp.dat' failed, status = 64. See the SQL Server Error Log
> > For
> > More details.
> >
> > Server: Msg 3013, Level 16, State 1, Line 1
> > Backup Database is terminating abnormally.
> >
> > The status = 64 means The specified network name
> > is no longer available ( ERROR_NETNAME_DELETED ). But the myserver is the
> > name of the computer on which sql server runs. I mean sql server is
> > installed
> > on myserver. So it should be same as saying c:\temp.dat.
> >
> > So the query becomes
> >
> >
> > But in case of c:\temp.dat it succeeds and in case of
> > \\myserver\c$\temp.dat
> > it fails ( it used to work, but ahs been failing recently).
> >
> > Now i tried following.
> >
> > 1. I am able to access c drive on myserver by typing \\myserver\c$ in
> > windows explorer from another computer on LAN.
> >
> > 2. I am able to access c drive by typing \\myserver\c$ in the windows
> > explorer on myserver.
> >
> > 3. ping 127.0.0.1 return normal results on myserver.
> >
> >
> > So why does windows generates ERROR_NETNAME_DELETED when i run
> > dump database MYDB to disk = '\\myserver\c$\temp.dat' with init
> > in query analyzer???
> >
> > P.S. : this works fine
> > RESTORE DATABASE MYDB FROM DISK = '\\myserver\c$\temp.dat'
> >
> > So guess access is not an issue.
>
>
>
- Next message: Adam Machanic: "Re: Locks - simple question"
- Previous message: jlybbert: "Passing large amounts of text to append to an NText field on the s"
- In reply to: John Bell: "Re: Backup Issue! Interesting or weird - you decide!"
- Next in thread: John Bell: "Re: Backup Issue! Interesting or weird - you decide!"
- Reply: John Bell: "Re: Backup Issue! Interesting or weird - you decide!"
- Reply: John Bell: "Re: Backup Issue! Interesting or weird - you decide!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|