Re: Backup error on Microsoft CMS 2002 SP1A Database

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Patrick (patl_at_reply.newsgroup.msn.com)
Date: 03/10/04 

Date: Wed, 10 Mar 2004 10:11:32 -0000

Strangely, if I change SQL Client Network utility to use TCP/IP before
Named-pipes, then the problem seems to have gone. But why is this? I
thought when SQL Server is installed locally to the server, named-pipes go
via the system kernel which is meant to be super fast?

"Patrick" <patl@reply.newsgroup.msn.com> wrote in message
news:uy6S1VoBEHA.2888@TK2MSFTNGP09.phx.gbl...
> 1) I did a serach for handle *.BAK with SysInternal's process explorer and
> could not find Symantec Anti Virus trying to access the *.BAK file.
>
> 2) I could select the Website database, right click All Task->Backup
> Database to do a complete backup successfully
>
> 3) For some reason if I log on as a user with DBA role (by Windows admin
> group membership) into query analyser, the execution of EXEC xp_cmdshell
> failed saying command not found, but more worrying is that when I execute
> the backup command, I get the following error
>
> [Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 10 percent backed up.
>
> Connection Broken
>
> The SQLServer 2000 with SP3a is installed on a Windows 2000 SP4 running
> Microsoft Content Management Server 2002 SP1A, ASP.NET, ASP applications
and
> it is a domain controller. The SQL Client Network utility is configured
as
> followed:
> - Enabled Shared memory protocol not ticked
> - enabled Protocol by order- Named Piped, TCP/IP
>
> SQL Client was set up as above because there were timed-out issues when
> using the Microsoft Content Management Server 2002 SP1A Site deployment
> import scripts.
>
> What is wrong?
> "Baisong Wei[MSFT]" <v-baiwei@online.microsoft.com> wrote in message
> news:jA66KVmBEHA.660@cpmsftngxa06.phx.gbl...
> > Hi Patrick,
> >
> > Thank your for using the newsgroup. It is my pleasure to help you with
> your
> > issue.
> >
> > From you information, you job to maintenance the database 'Website' ran

> > fine in the past, however, just recently, it persistently failed.
> >
> > There must be some change that different with before, so I want to
confirm
> > that when you disable the Anti-Virus Software on your computer, do you
> > still meet the problem? The following link would take you to the
download
> > of the Utility called ProcessExplorer that you can use to monitor access
> of
> > files by different processes.
>
> > To find what processes are accessing a particular file, you would need
to
> > Search and enter the File Name for obtaining a list of the processes.
> > http://www.sysinternals.com/ntw2k/freeware/procexp.shtml
> >
> > If it is not caused by the Anti-Virus software, you could try the
> following
> > steps to narrow down the problem. First, stop the antivirus software
and:
> >
> > 1) In the Enterprise Manager, using the Backup Wizard to backup the
> > database, any problems?
> > 2) Run in you Query Analyzer the following code (Suppose you are using
sa
> > and you login into the Query Analyzer by the account starting the SQL
> Agent
> > Service):
> >
> > Exec xp_cmdshell 'md d:\MSSQL\BACKUP\Website\aaa'
> > Go
> > Exec xp_cmdshell 'rd d:\MSSQL\BACKUP\Website\aaa'
> > go
> > BACKUP DATABASE [Website] TO DISK
> > =N'd:\MSSQL\BACKUP\Website\Website_db_200403091753.BAK' WITH INIT ,
> > NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
> >
> > Is there any Problems and messages?
> >
> > Looking forward to you reply.
> >
> > Thanks
> >
> > Best regards
> >
> > Baisong Wei
> > Microsoft Online Support
> > ----------------------------------------------------
> > Get Secure! - www.microsoft.com/security
> > This posting is provided "as is" with no warranties and confers no
rights.
> > Please reply to newsgroups only. Thanks.
> >
> >
> >
>
>

Relevant Pages

  • Re: windows Server 200· vs. Windows 98
    ... SQL Client protocol. ... Using the SQL Client Network Utility, check for the TCP protocol, and add it ...
    (microsoft.public.sqlserver.connect)
  • RE: Name of the SQLInstance?
    ... Try using SQL Client Network Utility and creating an alias for your instance. ... The only other way I know of is to rename you machine to 'sqllocal' - that ...
    (microsoft.public.sqlserver.programming)
  • Re: 2003 server web edition and 3rd party apps
    ... yeah, but is there a way to script/code this in the web page and not have to ... use SQL client network utility. ...
    (microsoft.public.inetserver.iis)
  • RE: Connection Prodlem-with instance node
    ... This means that the "Enable Protocol Encryption" option was set on the ... Use the SQL Client Network Utility to uncheck this. ...
    (microsoft.public.sqlserver.connect)
  • RE: Connection Prodlem-with instance node
    ... Razi ... > Use the SQL Client Network Utility to uncheck this. ...
    (microsoft.public.sqlserver.connect)