Re: Failed to apply script using 'osql' utility (sp_addscriptexec)

From: Warren Patterson (des_at_newsgroups.nospam)
Date: 05/10/04 

Date: Mon, 10 May 2004 14:42:43 +0200

Many thanks for your replies,

I have been speaking to Microsoft and it turns out this is a bug. Although
I am updating the Stored Procedures and the bug is for adding articles to a
subscription, the principal remains the same. There is no fix for this bug
and it may only be addressed in Yukon.

here are the particulars of the bug:

**********************************************************************
***************************START OF TEXT*****************************

BUG: Incremental Article Additions to an Existing Merge Publication Do
WGID:130

ID: 320600.KB.EN-US CREATED: 2002-03-29 MODIFIED: 2003-10-03

 Public |

============================================================================
===

---------------------------------------------------------------------------- 

---
The information in this article applies to:
 - Microsoft SQL Server 2000 (all editions)
----------------------------------------------------------------------------
---
BUG #: 356693 (SHILOH_BUGS)
SYMPTOMS
========
 If all the following conditions are true, the Merge Agent fails with an
error message when it tries to apply snapshot files:
 - Articles are being added incrementally to an existing merge  publication.
- The merge publication has already been published and subscribed.
- The mechanism for the distribution of snapshot is configured to use   FTP.
If the outputverboselevel option is set to 3, the following error messages
are in the Merge Agent Log file:
UNC Path
If the default snapshot location is a UNC path, the following error messages
are in the Merge Agent Log file:
            [1/29/2002 6:57:23 PM]REPL42\RTM.pubs: exec sp_datatype_info 0,
3
            The schema script '\\REPL42\D$\Program Files\Microsoft SQL
Server\MSSQL$RTM\ReplData\ftp\REPL42$RTM_pubs_pubs\20020129185653\Table2_8.s
ch' could not be propagated to the subscriber.
            Percent Complete: 0
            The schema script '\\REPL42\D$\Program Files\Microsoft SQL
Server\MSSQL$RTM\ReplData\ftp\REPL42$RTM_pubs_pubs\20020129185653\Table2_8.s
ch' could not be propagated to the subscriber.
            Repl Agent Status: 6
            Percent Complete: 0
            Category:NULL
            Source:  Merge Replication Provider
            Number:  -2147201001
            Message: The schema script '\\REPL42\D$\Program Files\Microsoft
SQL
Server\MSSQL$RTM\ReplData\ftp\REPL42$RTM_pubs_pubs\20020129185653\Table2_8.s
ch' could not be propagated to the subscriber.
            Repl Agent Status: 3
            Percent Complete: 0
            Category:AGENT
            Source:  REPL43\SQL2K
            Number:  0
            Message: The process could not read file '\\REPL42\D$\Program
Files\Microsoft SQL
Server\MSSQL$RTM\ReplData\ftp\REPL42$RTM_pubs_pubs\20020129185653\Table2_8.s
ch' due to OS error 5.
            Repl Agent Status: 3
            Percent Complete: 0
            Category:OS
            Source:
            Number:  5
            Message: Access is denied.
Local Folder
If the default snapshot location is a Local Folder, the following error
messages are in the Merge Agent Log file:
            [10/23/01 4:20:20 PM]LCL2B17B.TestDb: exec sp_datatype_info 0, 3
            The schema script
'C:\INETPUB\FTPROOT\ftp\LCL2B17B_TestDb_TestDb\20011029152641\Article3_15.sc
h' could not be propagated to the subscriber.
            Percent Complete: 0
            The schema script
'C:\INETPUB\FTPROOT\ftp\LCL2B17B_TestDb_TestDb\20011029152641\Article3_15.sc
h' could not be propagated to the subscriber.
            Repl Agent Status: 6
            Percent Complete: 0
            Category:NULL
            Source:  Merge Replication Provider
            Number:  -2147201001
            Message: The schema script
'C:\INETPUB\FTPROOT\ftp\LCL2B17B_TestDb_TestDb\20011029152641\Article3_15.sc
h' could not be propagated to the subscriber.
            Repl Agent Status: 3
            Percent Complete: 0
            Category:AGENT
            Source:  LCL2B22C
            Number:  0
            Message: The process could not read file
'C:\INETPUB\FTPROOT\ftp\LCL2B17B_TestDb_TestDb\20011029152641\Article3_15.sc
h' due to OS error 3.
            Repl Agent Status: 3
            Percent Complete: 0
            Category:OS
            Source:
            Number:  3
            Message: The system cannot find the path specified.
WORKAROUND
==========
 Incremental article additions to a merge publication cannot be handled if
you use FTP. Hence, no practical workaround exists other than performing a
REINIT of the whole publication.
If you must make incremental article additions, then you must use the UNC
mechanism to move the snapshot files instead of relying on FTP.
For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
            KBLink:320499.KB.EN-US: HOW TO: Manually Synchronize Replication
            Subscriptions by Using Backup or Restore
STATUS
======
Microsoft has confirmed that this is a problem in the Microsoft products
that are listed at the beginning of this article.
***************************END OF TEXT*******************************
**********************************************************************
""Michael Cheng [MSFT]"" <v-mingqc@online.microsoft.com> wrote in message
news:wv5yJCDNEHA.2692@cpmsftngxa10.phx.gbl...
> Hi Warren,
>
> From your descriptions, I understand that when you exec sp_addscriptexec
to
> appy scripts from remote computer, you will get an error message like
"OSQL
> cannot open input file". Have I understood you? If there is anything I
> misunderstood, please feel free to let me know.
>
> Would you please try to do the following steps and see whether it could
> resolved your issue?
> 1. Added the path to \mssql\binn directory in Computer
> Properties/Environment tab/System variables and rebooted the box.
> 2. I advised you that any paths used as parameters to xp_cmdshell had to
> refer to the local (database) computer not the client computer because
> xp_cmdshell runs from the database computer.  Unless you specfies them as
> network paths.
>
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
>
> Michael Cheng
> 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, many thanks.
>

Relevant Pages

  • Re: WMP 11 Bug
    ... I answered the question and still suggested they seek a response about their problem because it really didn't sound like a bug. ... If there is another means of reporting bugs that I have left off, please feel free to point it out. ... You couldn't really believe that WMP is less simple than say, Vista, or Windows XP, or Microsoft Office, or Internet Explorer. ... Microsoft's behalf that you're having problems with Windows Media Player. ...
    (microsoft.public.windowsmedia)
  • Re: Custom Dictionary
    ... that the effort Microsoft puts into evaluating, quantifying, and tracking ... customer report they get. ... going to be fixed and what isn't until they get to the "Zero Bug Benchmark", ...
    (microsoft.public.mac.office.word)
  • Re: send bug report to Microsoft
    ... the normal way to report bugs is to call Microsoft ... steps as documented on the MSDN Bug Check Code page for Bug Check ... anti-virus software that is installed on the Terminal Server: ... Invalid system memory was referenced. ...
    (microsoft.public.windows.terminal_services)
  • Re: [Full-disclosure] Steve Gibson smokes crack?
    ... about the bug for a long time and made a concious decision not to patch it even though they knew it could lead to a system compromise. ... People commented on how Microsoft put out a patch quicker than they ... This is their history going back to before they purchased IE, and something that became really evident when they first began rebuilding Mosaic. ... When NT came out and Microsoft moved from producing OS' that were not network ready out of the box and toy-like GUI infrastructures, the impacts of that strategy were transposed onto administrators and users alike. ...
    (Full-Disclosure)
  • Re: LoadPicture VB function in Office:mac 2004
    ... this is a known bug. ... Please take a moment to visit this URL and send a report ... MVPs are not Microsoft Employees ... > properties page to manually set the picture property of the image1 object ...
    (microsoft.public.mac.office.excel)
Quantcast