Re: Conflicting SQL Client Settings

From: Stefan [MSFT] (stefang_at_online.microsoft.com)
Date: 08/23/04 

Date: Mon, 23 Aug 2004 16:29:12 +0200

Hi Patrick,

1) MCMS likes all protocols if SP1 or SP1a are installed
2) creating an ALIAS in SQL tools for the different application would allow
to configure the protocols for all apps individually.

Cheers,
Stefan. 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
MCMS FAQ:
http://download.microsoft.com/download/4/2/5/4250f79a-c3a1-4003-9272-2404e92bb76a/MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/usersamples/Default.aspx?ProductDropDownList=Content+Management+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossner/archive/2003/12/07/41859.aspx
--------------------------------
"Patrick" <patl@reply.newsgroup.msn.com> wrote in message
news:esccSyRiEHA.2908@TK2MSFTNGP10.phx.gbl...
> Seems like SQL Server 2000 likes SQL Client to use TCP/IP (when doing
> backups), but Microsoft Content Management Server 2002 SP1A likes Named
> Pipes for MCMS Server Side Site Deployment Object export to work properly!
> I am faced with a big dilemma!
>
> See
>
http://download.microsoft.com/download/4/2/5/4250f79a-c3a1-4003-9272-2404e92bb76a/MCMS+2002+-+(complete)+FAQ.htm#B01B7B38-C97A-4935-8957-DC346719CE9B
>
> I have been experiencing frequest "General network Error"s, when I use
> Server side SDO to export the CMS repository (as a backup, before
importing
> a SDO file from another test server).  This article recommends the use of
> Named Pipes in preference over TCP/IP for SQL Client Network settings.
>
> However, there has been some recent failures in SQL Server Flat file
backup
> (SQL SErver maintenance plan to do full backup all application databases
> with verify).  Invesigation reveal (quite consistently) that the flat file
> backup of the MCMS 2002 SP1A database will always fail when Named Pipes to
> use.  As soon as SQL Client is changed to use TCP/IP, backup function as
> expectd.  The error that are logged when Named pipes are used as follows
> *1) The error logged in the error log file is :
> 2004-08-21 21:25:14.07 spid60    BackupDiskFile::OpenMedia: Backup device
> 'd:\MSSQL\BACKUP\DBLive\DBLive_db_200408212125.BAK' failed to open.
> Operating system error = 32(error not found).
> 2004-08-21 21:25:14.20 backup    BACKUP failed to complete the command
> BACKUP DATABASE [YJBLive] TO  DISK =
> N'd:\MSSQL\BACKUP\DBLive\DBLive_db_200408212125.BAK' WITH  INIT ,
NOUNLOAD
> ,  NOSKIP ,  STATS = 10,  NOFORMAT
>
>
> *2) If I change the job to just do the backup without verify, then the job
> completes, but
> *2.1) Normally, the BAK file used to be 3xxMB large, but now the BAK file
> which only succeeded in backing up without verifying is 1xxMB large
>
> *3) The Job History indicates
> Executed as user: WEBSERVER\SQLServer. sqlmaint.exe failed. [SQLSTATE
42000]
> (Error 22029).  The step failed.
> The job failed.  The Job was invoked by Schedule 2 (Schedule 1).  The last
> step to run was step 1 (Step 1).
>
> *4) The backup file appear corrupted:
> *4.1) If I look at the Maintenance Plan history, I found:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Cannot open backup device
> 'd:\MSSQL\BACKUP\DBLive\DBLive_db_200408231407.BAK'. Device error or
device
> off-line. See the SQL Server error log for more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
> terminating abnormally.
> *4.2) If I try to restore this (corrupted) 1xxMB BAK file to another DB,
it
> doesn't work.  After the popup to say restore has completed, Enterprise
> Manager shows the database as grey with "(Loading)" appended to the
database
> name (even after 5mins)
>
> *5) The user group Everyone has full permission on d:\MSSQL\BACKUP
>
> *6) DBCC CheckDB, DBCC CheckFileGroup, DBCC CheckIdent reveal no errors
>
> So, I am really stuck here, could some SQL Server / MCMS expert help me
out
> here!  If I use Named Pipes, SQL Backup is not going to work.  If I use
> TCP/IP, then my MCMS export/import would not work most of the time!
>
>

Relevant Pages

  • Re: SQL backup questions
    ... I support the Professional Association for SQL Server ... Copy DB is functionally the same as Backup and Restore. ...
    (microsoft.public.sqlserver.server)
  • Re: URGENT: SQL 6.5 Server Crash
    ... > Are these database backup done by SQL Server? ... > Or file backups performed by some Windows backup software? ... were they performed while SQL Server was running? ...
    (microsoft.public.sqlserver.server)
  • Re: Does NTBackup backup SQL Express?
    ... schedule backups of the SQL databases which were written to a backup ... models you would have to backup and flush things manually. ... if you load the backup set does the database appear to be ... I've always scripted my SQL Server backups separatly. ...
    (microsoft.public.windows.server.sbs)
  • Re: Does NTBackup backup SQL Express?
    ... as I know enough that the logs must be flushed during every full backup. ... and the SBS server I regularly use runs MySQL not SQL ... if you load the backup set does the database appear to be listed ... I've always scripted my SQL Server backups separatly. ...
    (microsoft.public.windows.server.sbs)
  • Conflicting SQL Client Settings
    ... Pipes for MCMS Server Side Site Deployment Object export to work properly! ... Server side SDO to export the CMS repository (as a backup, ... there has been some recent failures in SQL Server Flat file backup ...
    (microsoft.public.sqlserver.server)