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/downlo...a/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.BA K' 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!
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/downlo...a/MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/u...emen t+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossner.../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/downlo...a/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.BA K' 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!
>
|||Thanks stefan,
Can I just check if the FAQ in regards to "General Network Error" when using
server side SDO to do export/import apply to MCMS2002 with SP1A (the CD
comes with SP1A) or not? If not, could you suggest any other remedies? I
have tried all the remedies listed in the FAQ at
http://download.microsoft.com/downlo...a/MCMS+2002+-+(complete)+FAQ.htm#B01B7B38-C97A-4935-8957-DC346719CE9B
and still we are getting quite frequent "General Network Error" when
performing export on a repository (whose SQL DB is 1GB ish and whose SDO
file is 80MB). e.g. timeouts/maxium request size are much larger than that
required already!!
"Stefan [MSFT]" <stefang@.online.microsoft.com> wrote in message
news:elC3D2RiEHA.396@.TK2MSFTNGP12.phx.gbl...
> 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/downlo...a/MCMS+2002+-+(complete)+FAQ.htm
> MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
> MCMS Sample Code:
>
http://www.gotdotnet.com/community/u...emen t+Server[vbcol=seagreen]
> MCMS Whitepapers and other docs:
> http://blogs.msdn.com/stefan_gossner.../07/41859.aspx
> --
>
> "Patrick" <patl@.reply.newsgroup.msn.com> wrote in message
> news:esccSyRiEHA.2908@.TK2MSFTNGP10.phx.gbl...
properly!
>
http://download.microsoft.com/downlo...a/MCMS+2002+-+(complete)+FAQ.htm#B01B7B38-C97A-4935-8957-DC346719CE9B[vbcol=seagreen]
> importing
of[vbcol=seagreen]
> backup
file[vbcol=seagreen]
to[vbcol=seagreen]
device[vbcol=seagreen]
> NOUNLOAD
job[vbcol=seagreen]
file[vbcol=seagreen]
> 42000]
last
> SQL
> device
> it
> database
> out
>
|||Hi Patrick,
you should surely test if using named pipes solves the problem or not. We
had customers indicating that this solved their problem even after SP1a -
although we assume that the problem was related to their network
architecture as we haven't been able to repro this inhouse.
Using an ALIAS allows to do this easily without affecting any other
applications.
From my understanding backup should work with all protocols - so this
sounds as if there are indeed problems with your network architecture. You
should follow up on this in an SQL related newsgroup.
Cheers,
Stefan.
This posting is provided "AS IS" with no warranties, and confers no rights.
MCMS FAQ:
http://download.microsoft.com/downlo...a/MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/u...emen t+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossner.../07/41859.aspx
"Patrick" <patl@.reply.newsgroup.msn.com> wrote in message
news:eG8LodbiEHA.3608@.TK2MSFTNGP09.phx.gbl...
> Thanks stefan,
> Can I just check if the FAQ in regards to "General Network Error" when
using
> server side SDO to do export/import apply to MCMS2002 with SP1A (the CD
> comes with SP1A) or not? If not, could you suggest any other remedies? I
> have tried all the remedies listed in the FAQ at
>
http://download.microsoft.com/downlo...a/MCMS+2002+-+(complete)+FAQ.htm#B01B7B38-C97A-4935-8957-DC346719CE9B
> and still we are getting quite frequent "General Network Error" when
> performing export on a repository (whose SQL DB is 1GB ish and whose SDO
> file is 80MB). e.g. timeouts/maxium request size are much larger than
that
> required already!!
> "Stefan [MSFT]" <stefang@.online.microsoft.com> wrote in message
> news:elC3D2RiEHA.396@.TK2MSFTNGP12.phx.gbl...
> allow
> rights.
>
http://download.microsoft.com/downlo...a/MCMS+2002+-+(complete)+FAQ.htm
>
http://www.gotdotnet.com/community/u...emen t+Server[vbcol=seagreen]
Named
> properly!
>
http://download.microsoft.com/downlo...a/MCMS+2002+-+(complete)+FAQ.htm#B01B7B38-C97A-4935-8957-DC346719CE9B[vbcol=seagreen]
> of
databases[vbcol=seagreen]
> file
Pipes[vbcol=seagreen]
> to
as[vbcol=seagreen]
follows[vbcol=seagreen]
> device
> job
> file
> last
[Microsoft][ODBC[vbcol=seagreen]
DB,[vbcol=seagreen]
Enterprise[vbcol=seagreen]
errors[vbcol=seagreen]
me[vbcol=seagreen]
use
>
|||Actually:
1) Tests reveal that we cannot consistently prove whether Server side SDO
export/import would work with TCP/IP or Named-pipes
2) Tests reveal that Flat file backups
2.1) for the MCMS 2002 SP1A Repository consistently fail when SQL Client
Network utility is set to use Named Pipes.
2.2) For other databases (including a 3GB database, as opposed to a mere 1GB
MCMS SQL DB) all works with named pipes
3) The SQL Server, IIS and CMS are all on the same box! So, named pipes
should be using (I believe) the internal kernel, which is meant to be super
fast?
"Stefan [MSFT]" <stefang@.online.microsoft.com> wrote in message
news:evymkDciEHA.4020@.TK2MSFTNGP10.phx.gbl...
> Hi Patrick,
> you should surely test if using named pipes solves the problem or not. We
> had customers indicating that this solved their problem even after SP1a -
> although we assume that the problem was related to their network
> architecture as we haven't been able to repro this inhouse.
> Using an ALIAS allows to do this easily without affecting any other
> applications.
> From my understanding backup should work with all protocols - so this
> sounds as if there are indeed problems with your network architecture. You
> should follow up on this in an SQL related newsgroup.
> Cheers,
> Stefan.
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> MCMS FAQ:
>
http://download.microsoft.com/downlo...a/MCMS+2002+-+(complete)+FAQ.htm
> MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
> MCMS Sample Code:
>
http://www.gotdotnet.com/community/u...emen t+Server[vbcol=seagreen]
> MCMS Whitepapers and other docs:
> http://blogs.msdn.com/stefan_gossner.../07/41859.aspx
> --
>
> "Patrick" <patl@.reply.newsgroup.msn.com> wrote in message
> news:eG8LodbiEHA.3608@.TK2MSFTNGP09.phx.gbl...
> using
I
>
http://download.microsoft.com/downlo...a/MCMS+2002+-+(complete)+FAQ.htm#B01B7B38-C97A-4935-8957-DC346719CE9B
> that
>
http://download.microsoft.com/downlo...a/MCMS+2002+-+(complete)+FAQ.htm
>
http://www.gotdotnet.com/community/u...emen t+Server[vbcol=seagreen]
doing
> Named
>
http://download.microsoft.com/downlo...a/MCMS+2002+-+(complete)+FAQ.htm#B01B7B38-C97A-4935-8957-DC346719CE9B[vbcol=seagreen]
use[vbcol=seagreen]
use[vbcol=seagreen]
settings.[vbcol=seagreen]
> databases
flat[vbcol=seagreen]
> Pipes
function[vbcol=seagreen]
> as
> follows
command[vbcol=seagreen]
the[vbcol=seagreen]
[SQLSTATE[vbcol=seagreen]
The
> [Microsoft][ODBC
> DB,
> Enterprise
> errors
> me
> use
>
|||Hi Patrick,
Just wondering if you found a solution to your backup problem. We have a
similiar issue and are banging our head trying to figure out what the problem
is.
"Patrick" wrote:
> Actually:
> 1) Tests reveal that we cannot consistently prove whether Server side SDO
> export/import would work with TCP/IP or Named-pipes
> 2) Tests reveal that Flat file backups
> 2.1) for the MCMS 2002 SP1A Repository consistently fail when SQL Client
> Network utility is set to use Named Pipes.
> 2.2) For other databases (including a 3GB database, as opposed to a mere 1GB
> MCMS SQL DB) all works with named pipes
> 3) The SQL Server, IIS and CMS are all on the same box! So, named pipes
> should be using (I believe) the internal kernel, which is meant to be super
> fast?
>
> "Stefan [MSFT]" <stefang@.online.microsoft.com> wrote in message
> news:evymkDciEHA.4020@.TK2MSFTNGP10.phx.gbl...
> rights.
> http://download.microsoft.com/downlo...a/MCMS+2002+-+(complete)+FAQ.htm
> http://www.gotdotnet.com/community/u...emen t+Server
> I
> http://download.microsoft.com/downlo...a/MCMS+2002+-+(complete)+FAQ.htm#B01B7B38-C97A-4935-8957-DC346719CE9B
> http://download.microsoft.com/downlo...a/MCMS+2002+-+(complete)+FAQ.htm
> http://www.gotdotnet.com/community/u...emen t+Server
> doing
> http://download.microsoft.com/downlo...a/MCMS+2002+-+(complete)+FAQ.htm#B01B7B38-C97A-4935-8957-DC346719CE9B
> use
> use
> settings.
> flat
> function
> command
> the
> [SQLSTATE
> The
>
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment