I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
get an error trying to backup to a local drive:
Cannot verify the existence of the backup file location.
I read how this usually refers to backing up to a network share or
something, but this is a local drive. I tried it logged in to the Management
Studio as trusted and SQL authentication.
Any ideas? Thanks!
Hi
You may want to check backing up to a different directory, if that works it
must be ralated to the directory in which you are backing up to, such as
permissions.
John
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
|||Thanks, I tried that. Even tried to backup right to C, just for fun
--didn't work. Other suggestions?
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
|||ricky252525 wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
Is the SQL Server service running as a domain user or as Local System?
Which domain user? What rights does that domain user have on the local
machine?
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Hi
If you have checked/changed the service accounts as Tracy has suggested then
what message do you get if you back this up using a T-SQL script?
John
"ricky252525" wrote:
[vbcol=seagreen]
> Thanks, I tried that. Even tried to backup right to C, just for fun
> --didn't work. Other suggestions?
> "ricky252525" wrote:
Showing posts with label logged. Show all posts
Showing posts with label logged. Show all posts
Thursday, March 22, 2012
Error doing manual backup
I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
get an error trying to backup to a local drive:
Cannot verify the existence of the backup file location.
I read how this usually refers to backing up to a network share or
something, but this is a local drive. I tried it logged in to the Managemen
t
Studio as trusted and SQL authentication.
Any ideas? Thanks!Hi
You may want to check backing up to a different directory, if that works it
must be ralated to the directory in which you are backing up to, such as
permissions.
John
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin a
nd
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Managem
ent
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!|||Thanks, I tried that. Even tried to backup right to C, just for fun
--didn't work. Other suggestions?
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin a
nd
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Managem
ent
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!|||ricky252525 wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin a
nd
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Managem
ent
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
Is the SQL Server service running as a domain user or as Local System?
Which domain user? What rights does that domain user have on the local
machine?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi
If you have checked/changed the service accounts as Tracy has suggested then
what message do you get if you back this up using a T-SQL script?
John
"ricky252525" wrote:
[vbcol=seagreen]
> Thanks, I tried that. Even tried to backup right to C, just for fun
> --didn't work. Other suggestions?
> "ricky252525" wrote:
>
get an error trying to backup to a local drive:
Cannot verify the existence of the backup file location.
I read how this usually refers to backing up to a network share or
something, but this is a local drive. I tried it logged in to the Managemen
t
Studio as trusted and SQL authentication.
Any ideas? Thanks!Hi
You may want to check backing up to a different directory, if that works it
must be ralated to the directory in which you are backing up to, such as
permissions.
John
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin a
nd
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Managem
ent
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!|||Thanks, I tried that. Even tried to backup right to C, just for fun
--didn't work. Other suggestions?
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin a
nd
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Managem
ent
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!|||ricky252525 wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin a
nd
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Managem
ent
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
Is the SQL Server service running as a domain user or as Local System?
Which domain user? What rights does that domain user have on the local
machine?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi
If you have checked/changed the service accounts as Tracy has suggested then
what message do you get if you back this up using a T-SQL script?
John
"ricky252525" wrote:
[vbcol=seagreen]
> Thanks, I tried that. Even tried to backup right to C, just for fun
> --didn't work. Other suggestions?
> "ricky252525" wrote:
>
Error doing manual backup
I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
get an error trying to backup to a local drive:
Cannot verify the existence of the backup file location.
I read how this usually refers to backing up to a network share or
something, but this is a local drive. I tried it logged in to the Management
Studio as trusted and SQL authentication.
Any ideas? Thanks!Hi
You may want to check backing up to a different directory, if that works it
must be ralated to the directory in which you are backing up to, such as
permissions.
John
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!|||Thanks, I tried that. Even tried to backup right to C, just for fun
--didn't work. Other suggestions?
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!|||ricky252525 wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
Is the SQL Server service running as a domain user or as Local System?
Which domain user? What rights does that domain user have on the local
machine?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi
If you have checked/changed the service accounts as Tracy has suggested then
what message do you get if you back this up using a T-SQL script?
John
"ricky252525" wrote:
> Thanks, I tried that. Even tried to backup right to C, just for fun
> --didn't work. Other suggestions?
> "ricky252525" wrote:
> > I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> > get an error trying to backup to a local drive:
> >
> > Cannot verify the existence of the backup file location.
> >
> > I read how this usually refers to backing up to a network share or
> > something, but this is a local drive. I tried it logged in to the Management
> > Studio as trusted and SQL authentication.
> >
> > Any ideas? Thanks!
get an error trying to backup to a local drive:
Cannot verify the existence of the backup file location.
I read how this usually refers to backing up to a network share or
something, but this is a local drive. I tried it logged in to the Management
Studio as trusted and SQL authentication.
Any ideas? Thanks!Hi
You may want to check backing up to a different directory, if that works it
must be ralated to the directory in which you are backing up to, such as
permissions.
John
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!|||Thanks, I tried that. Even tried to backup right to C, just for fun
--didn't work. Other suggestions?
"ricky252525" wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!|||ricky252525 wrote:
> I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> get an error trying to backup to a local drive:
> Cannot verify the existence of the backup file location.
> I read how this usually refers to backing up to a network share or
> something, but this is a local drive. I tried it logged in to the Management
> Studio as trusted and SQL authentication.
> Any ideas? Thanks!
Is the SQL Server service running as a domain user or as Local System?
Which domain user? What rights does that domain user have on the local
machine?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi
If you have checked/changed the service accounts as Tracy has suggested then
what message do you get if you back this up using a T-SQL script?
John
"ricky252525" wrote:
> Thanks, I tried that. Even tried to backup right to C, just for fun
> --didn't work. Other suggestions?
> "ricky252525" wrote:
> > I'm sitting at the server itself (SQL 2005 Standard), logged in as admin and
> > get an error trying to backup to a local drive:
> >
> > Cannot verify the existence of the backup file location.
> >
> > I read how this usually refers to backing up to a network share or
> > something, but this is a local drive. I tried it logged in to the Management
> > Studio as trusted and SQL authentication.
> >
> > Any ideas? Thanks!
Error Description differs when logged with Redirect Rows compared with Debug mode
Hi,
Can any one please tell me how to get the complete error description for example when i dont Redirect Row for Error in OLEDB Source i get a detailed error message with column name as
[RCheck [385]] Error: There was an error with input column "CHECK_STATUS" (456) on input "OLE DB Destination Input" (398). The column status returned was: "The value could not be converted because of a potential loss of data.".
But when I set Redirect Row for error and use the Script component to log them into a Table with ErrorDescription based on ErrorColumnID it only gives me this.
The data value cannot be converted for reasons other than sign mismatch or data overflow.
Thanks
Sat
Can't make the FailComponent and RedirectRow error messages the same with stock OLEDB source component.
If you want to actually redirect AND get the original provider error message that you would get in Fail Component mode, well, that component has yet to be written by Microsoft.
Instead, as you're seeing, when performing redirection using the OLEDB source; only the generic ErrorCode => generic textual description is exposed via ComponentMetaData.GetErrorDescription().
With a custom component of course, you can amend error outputs with additional columns, which is exactly what I have had to do to circumvent this problem.
Subscribe to:
Posts (Atom)