error during setup of microsoft sql express 2005 edition for visual web design?

error saying disk compressed or encryted, choose another drive?

how should i t-shoot !!!!!

This one means exactly what it says. You can't install SQL Server onto a compressed drive, you will need to choose another drive or uncompress your drive. This is documented in BOL.

Mike

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.).

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:
> 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 connecting to SQL from within same machine

I am trying to move my SharePoint db's from on drive on a SQL Server to
another. Apparently, This cannot be done with the Management Tool and must
be done with the sqlcmd.
The first comand needed is: >sqlcmd -S
\\.\pipe\mssql$microsoft##ssee\sql\query -E
This yields the follwoing error:
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establi
shing a connection to the server. When connecting to SQL Server 2005, this
failu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
TCP, Named Pipes and Shared Memory are enabled and configuration allows for
remote connection (even thought this local)
I have tried to modify the command with the specific instance and
server\instance all result in the same error.
I am at a loss as what to do to move these db's
Can anyone help with this issue.
Thanks,
Mike Altman
Hello Mike,
Do not use sqlcmd. Just stop your SharePoint services. Detach your databases
using Management Studio, go to the operating system and move all your
database files to the new drive and then attach your databases using
Management Studio again.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"travldc" wrote:

> I am trying to move my SharePoint db's from on drive on a SQL Server to
> another. Apparently, This cannot be done with the Management Tool and must
> be done with the sqlcmd.
> The first comand needed is: >sqlcmd -S
> \\.\pipe\mssql$microsoft##ssee\sql\query -E
> This yields the follwoing error:
> HResult 0x2, Level 16, State 1
> Named Pipes Provider: Could not open a connection to SQL Server [2].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server does
> not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> TCP, Named Pipes and Shared Memory are enabled and configuration allows for
> remote connection (even thought this local)
> I have tried to modify the command with the specific instance and
> server\instance all result in the same error.
> I am at a loss as what to do to move these db's
> Can anyone help with this issue.
> Thanks,
> Mike Altman
>
>
|||Hi Ben,
I had read that this was not best practice, but it worked just fine. Thanks
for the help.
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hello Mike,
> Do not use sqlcmd. Just stop your SharePoint services. Detach your databases
> using Management Studio, go to the operating system and move all your
> database files to the new drive and then attach your databases using
> Management Studio again.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "travldc" wrote:

Error connecting to SQL from within same machine

I am trying to move my SharePoint db's from on drive on a SQL Server to
another. Apparently, This cannot be done with the Management Tool and must
be done with the sqlcmd.
The first comand needed is: >sqlcmd -S
\\.\pipe\mssql$microsoft##ssee\sql\query -E
This yields the follwoing error:
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establi
shing a connection to the server. When connecting to SQL Server 2005, this
failu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
TCP, Named Pipes and Shared Memory are enabled and configuration allows for
remote connection (even thought this local)
I have tried to modify the command with the specific instance and
server\instance all result in the same error.
I am at a loss as what to do to move these db's
Can anyone help with this issue.
Thanks,
Mike AltmanHello Mike,
Do not use sqlcmd. Just stop your SharePoint services. Detach your databases
using Management Studio, go to the operating system and move all your
database files to the new drive and then attach your databases using
Management Studio again.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"travldc" wrote:
> I am trying to move my SharePoint db's from on drive on a SQL Server to
> another. Apparently, This cannot be done with the Management Tool and must
> be done with the sqlcmd.
> The first comand needed is: >sqlcmd -S
> \\.\pipe\mssql$microsoft##ssee\sql\query -E
> This yields the follwoing error:
> HResult 0x2, Level 16, State 1
> Named Pipes Provider: Could not open a connection to SQL Server [2].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server does
> not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> TCP, Named Pipes and Shared Memory are enabled and configuration allows for
> remote connection (even thought this local)
> I have tried to modify the command with the specific instance and
> server\instance all result in the same error.
> I am at a loss as what to do to move these db's
> Can anyone help with this issue.
> Thanks,
> Mike Altman
>
>|||Hi Ben,
I had read that this was not best practice, but it worked just fine. Thanks
for the help.
"Ben Nevarez" wrote:
> Hello Mike,
> Do not use sqlcmd. Just stop your SharePoint services. Detach your databases
> using Management Studio, go to the operating system and move all your
> database files to the new drive and then attach your databases using
> Management Studio again.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "travldc" wrote:
> > I am trying to move my SharePoint db's from on drive on a SQL Server to
> > another. Apparently, This cannot be done with the Management Tool and must
> > be done with the sqlcmd.
> >
> > The first comand needed is: >sqlcmd -S
> > \\.\pipe\mssql$microsoft##ssee\sql\query -E
> >
> > This yields the follwoing error:
> >
> > HResult 0x2, Level 16, State 1
> > Named Pipes Provider: Could not open a connection to SQL Server [2].
> > Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> > establi
> > shing a connection to the server. When connecting to SQL Server 2005, this
> > failu
> > re may be caused by the fact that under the default settings SQL Server does
> > not
> > allow remote connections..
> > Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> >
> > TCP, Named Pipes and Shared Memory are enabled and configuration allows for
> > remote connection (even thought this local)
> >
> > I have tried to modify the command with the specific instance and
> > server\instance all result in the same error.
> >
> > I am at a loss as what to do to move these db's
> >
> > Can anyone help with this issue.
> >
> > Thanks,
> >
> > Mike Altman
> >
> >
> >
> >

Error connecting to SQL from within same machine

I am trying to move my SharePoint db's from on drive on a SQL Server to
another. Apparently, This cannot be done with the Management Tool and must
be done with the sqlcmd.
The first comand needed is: >sqlcmd -S
\\.\pipe\mssql$microsoft##ssee\sql\query -E
This yields the follwoing error:
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establi
shing a connection to the server. When connecting to SQL Server 2005, this
failu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
TCP, Named Pipes and Shared Memory are enabled and configuration allows for
remote connection (even thought this local)
I have tried to modify the command with the specific instance and
server\instance all result in the same error.
I am at a loss as what to do to move these db's
Can anyone help with this issue.
Thanks,
Mike AltmanHello Mike,
Do not use sqlcmd. Just stop your SharePoint services. Detach your databases
using Management Studio, go to the operating system and move all your
database files to the new drive and then attach your databases using
Management Studio again.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"travldc" wrote:

> I am trying to move my SharePoint db's from on drive on a SQL Server to
> another. Apparently, This cannot be done with the Management Tool and mus
t
> be done with the sqlcmd.
> The first comand needed is: >sqlcmd -S
> \\.\pipe\mssql$microsoft##ssee\sql\query -E
> This yields the follwoing error:
> HResult 0x2, Level 16, State 1
> Named Pipes Provider: Could not open a connection to SQL Server [2].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server do
es
> not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> TCP, Named Pipes and Shared Memory are enabled and configuration allows fo
r
> remote connection (even thought this local)
> I have tried to modify the command with the specific instance and
> server\instance all result in the same error.
> I am at a loss as what to do to move these db's
> Can anyone help with this issue.
> Thanks,
> Mike Altman
>
>|||Hi Ben,
I had read that this was not best practice, but it worked just fine. Thanks
for the help.
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hello Mike,
> Do not use sqlcmd. Just stop your SharePoint services. Detach your databas
es
> using Management Studio, go to the operating system and move all your
> database files to the new drive and then attach your databases using
> Management Studio again.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "travldc" wrote:
>