Showing posts with label verify. Show all posts
Showing posts with label verify. Show all posts

Monday, March 26, 2012

Error during backup verify

SQL Server 2000.
Doing an SQL backup to a network shared drive on our file server.
Any help appreciated ...
During the verify on several different databases, I find the following
error in the Maintenance Plan log:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3203:
[Microsoft][ODBC SQL Server Driver][SQL Server]Read on
'\\Pfcdata\SQLBackup\PFCSQLT\pfcgold_db_200402102300.BAK' failed,
status = 64. See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
terminating abnormally.
I get the following info from the SQL Server Error Log:
BackupMedium::ReportIoError: read failure on backup device
'\\Pfcdata\SQLBackup\PFCSQLT\pfcgold_db_200402162359.BAK'. Operating
system error 64(The specified network name is no longer available.).That is a common NT error. Could you test the network connections by copying
large files between the servers. Also have you checked the NT eventlogs on
the file server to see if you have any messages releated to network
problems.
Simon
This posting is provided "as is" with no warranties and confers no rights.
"SoCal Snapper" <snapperjackson@.juno.com> wrote in message
news:2d4f003f.0402251113.6c36d43d@.posting.google.com...
> SQL Server 2000.
> Doing an SQL backup to a network shared drive on our file server.
> Any help appreciated ...
> During the verify on several different databases, I find the following
> error in the Maintenance Plan log:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3203:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Read on
> '\\Pfcdata\SQLBackup\PFCSQLT\pfcgold_db_200402102300.BAK' failed,
> status = 64. See the SQL Server error log for more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
> terminating abnormally.
> I get the following info from the SQL Server Error Log:
> BackupMedium::ReportIoError: read failure on backup device
> '\\Pfcdata\SQLBackup\PFCSQLT\pfcgold_db_200402162359.BAK'. Operating
> system error 64(The specified network name is no longer available.).

Thursday, March 22, 2012

Error during backup verify

SQL Server 2000.
Doing an SQL backup to a network shared drive on our file server.
Any help appreciated ...
During the verify on several different databases, I find the following
error in the Maintenance Plan log:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3203:
[Microsoft][ODBC SQL Server Driver][SQL Server]Read on
'\\Pfcdata\SQLBackup\PFCSQLT\pfcgold_db_
200402102300.BAK' failed,
status = 64. See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE i
s
terminating abnormally.
I get the following info from the SQL Server Error Log:
BackupMedium::ReportIoError: read failure on backup device
'\\Pfcdata\SQLBackup\PFCSQLT\pfcgold_db_
200402162359.BAK'. Operating
system error 64(The specified network name is no longer available.).That is a common NT error. Could you test the network connections by copying
large files between the servers. Also have you checked the NT eventlogs on
the file server to see if you have any messages releated to network
problems.
Simon
This posting is provided "as is" with no warranties and confers no rights.
"SoCal Snapper" <snapperjackson@.juno.com> wrote in message
news:2d4f003f.0402251113.6c36d43d@.posting.google.com...
> SQL Server 2000.
> Doing an SQL backup to a network shared drive on our file server.
> Any help appreciated ...
> During the verify on several different databases, I find the following
> error in the Maintenance Plan log:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3203:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Read on
> '\\Pfcdata\SQLBackup\PFCSQLT\pfcgold_db_
200402102300.BAK' failed,
> status = 64. See the SQL Server error log for more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE
is
> terminating abnormally.
> I get the following info from the SQL Server Error Log:
> BackupMedium::ReportIoError: read failure on backup device
> '\\Pfcdata\SQLBackup\PFCSQLT\pfcgold_db_
200402162359.BAK'. Operating
> system error 64(The specified network name is no longer available.).sql

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:
[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 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!

Wednesday, March 21, 2012

error creating mdf - Connection to SQL server files (*.mdf) require SQL express 2005 to...

Connection to SQL server files (*.mdf) require SQL express 2005 to function properly. please verify the installation of the component or download fromhttp://go.microsoft.com/fwlink/?linkid=49251

I AM GOING TO RIP MY HAIR OUT WITH THIS PROBLEM. I have reinstalled both sql server express 2005 and VWD about 5 times with the same problem. please, please, please someone throw me a bone here and help me resolve this problem.

When I create a new EMPTY website and I rightclick on my website in the solution explorer and choose add item, I chooe SQL Database, I give it a name 'database.mdf' and click add. I get the following message:

you are attempting to add a database to an asp.net application. for a database to be gfenerally consumable in your site, it should be placed inside the 'app_data' folder. would you like to place the database inside the 'app_data' folder? I click YES (I know this message is normal)

then I get the following message:

Connection to SQL server files (*.mdf) require SQL express 2005 to function properly. please verify the installation of the component or download fromhttp://go.microsoft.com/fwlink/?linkid=49251

I can add anything else but this damn mdf file.

thanks for all your help in advance.

FYI to anyone who has had this problem and cannot find a resolution. I have found the solution in a another forum:

From:Brian Piesik -view profileDate:Mon, Feb 13 2006 3:20 pmEmail:Brian Piesik <bpie...@.community.nospam>Groups:microsoft.public.dotnet.framework.windowsforms

Not yet rated

Rating: show options


Reply to Author |Forward |Print |Individual Message |Show original |Report Abuse |Find messages by this author

Thanks Jeffrey, the problem turned out to be a problem in Visual Studio
with an incorrect setting.

What I did was go into Tools, Options, Database Tools, Data Connections.

UnderSQLServer Instance Name (blank for default) i had the following
in there: MyComputerName\SQLEXPRESS

I changed it to the following: SQLEXPRESS

I also tested it just leaving it blank and working too.

Of course I would love to say a favorite end user quote "I never changed
it", but I'm too geeky to know that.

Happy Coding!

Brian Piesik

|||

Thanksbigdbingo, for this valuable post