Prev: Login Failed for user "Distributor_admin'
Next: Cannot insert explicit value for identity column
From: jaylou on 6 Nov 2007 09:56
Hi all,
I had a hard drive crash and I rebuilt a SQL 2005 Express. I used an image
I have been using for about 5 other locations. I renamed everything as I did
for all my other locations and I tried to turn replication on for this new
box. At first it failed because the subscription was invalid. I dropped and
recreated it. I added an output file with OutputVerboseLevel 2.

I attached the last lines of the file below. Hopefully someone can decipher
what the issue is. The DLL being referenced is not on my Box nor is it on
any of my other boxes where my replication is having no issues. The only
references I have found for this DLL is for SQL2000 SP3. My publisher is
SQL2005 Standard SP2 and this is SQL2005 Express Edition SP2.

The error I am getting in my file is:

2007-11-06 14:17:51.609 OLE DB Subscriber 'LOC146':
sp_MSacquiresnapshotdeliverysessionlock
2007-11-06 14:17:51.609 OLE DB Subscriber 'LOC146':
sp_MStrypurgingoldsnapshotdeliveryprogress
2007-11-06 14:17:51.625 OLE DB Subscriber 'LOC146': {call
sys.sp_MSadd_merge_history90
(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2007-11-06 14:17:51.641 [3%] [0 sec remaining] Percent Complete: 3
2007-11-06 14:17:51.641 Preparing table 'APPLICATION_VERSION_CONTROL' for
merge replication
2007-11-06 14:17:51.641 OLE DB Distributor 'SQLSERVER1': {call
sys.sp_MSadd_merge_history90
(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2007-11-06 14:17:51.641 The merge process was unable to deliver the snapshot
to the Subscriber. If using Web synchronization, the merge process may have
been unable to create or write to the message file. When troubleshooting,
restart the synchronization with verbose history logging and specify an
output file to which to write.
2007-11-06 14:17:51.641 OLE DB Subscriber 'LOC146': {call
sys.sp_MSadd_merge_history90
(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2007-11-06 14:17:51.641 Percent Complete: 3
2007-11-06 14:17:51.641 Could not load the DLL xprepl.dll, or one of the
DLLs it references. Reason: 126(The specified module could not be found.).
2007-11-06 14:17:51.641 OLE DB Distributor 'SQLSERVER1': {call
sys.sp_MSadd_merge_history90
(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2007-11-06 14:17:51.672 Percent Complete: 0
2007-11-06 14:17:51.672 Category:SQLSERVER
Source: LOC146
Number: 17750
Message: Could not load the DLL xprepl.dll, or one of the DLLs it
references. Reason: 126(The specified module could not be found.).
2007-11-06 14:17:51.688 Percent Complete: 0
2007-11-06 14:17:51.688 Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The merge process was unable to deliver the snapshot to the
Subscriber. If using Web synchronization, the merge process may have been
unable to create or write to the message file. When troubleshooting, restart
the synchronization with verbose history logging and specify an output file
to which to write.

From: Chris on 14 Nov 2007 18:45

Replication is not installed by default on SQL Server Express edition.

see "How to: Install Replication During SQL Server Express Setup" in SQL
Express documentation.

ChrisB MCDBA
MSSQLConsulting.com

"jaylou" wrote:

> Hi all,
> I had a hard drive crash and I rebuilt a SQL 2005 Express. I used an image
> I have been using for about 5 other locations. I renamed everything as I did
> for all my other locations and I tried to turn replication on for this new
> box. At first it failed because the subscription was invalid. I dropped and
> recreated it. I added an output file with OutputVerboseLevel 2.
>
> I attached the last lines of the file below. Hopefully someone can decipher
> what the issue is. The DLL being referenced is not on my Box nor is it on
> any of my other boxes where my replication is having no issues. The only
> references I have found for this DLL is for SQL2000 SP3. My publisher is
> SQL2005 Standard SP2 and this is SQL2005 Express Edition SP2.
>
> The error I am getting in my file is:
>
> 2007-11-06 14:17:51.609 OLE DB Subscriber 'LOC146':
> sp_MSacquiresnapshotdeliverysessionlock
> 2007-11-06 14:17:51.609 OLE DB Subscriber 'LOC146':
> sp_MStrypurgingoldsnapshotdeliveryprogress
> 2007-11-06 14:17:51.625 OLE DB Subscriber 'LOC146': {call
> sys.sp_MSadd_merge_history90
> (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
> 2007-11-06 14:17:51.641 [3%] [0 sec remaining] Percent Complete: 3
> 2007-11-06 14:17:51.641 Preparing table 'APPLICATION_VERSION_CONTROL' for
> merge replication
> 2007-11-06 14:17:51.641 OLE DB Distributor 'SQLSERVER1': {call
> sys.sp_MSadd_merge_history90
> (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
> 2007-11-06 14:17:51.641 The merge process was unable to deliver the snapshot
> to the Subscriber. If using Web synchronization, the merge process may have
> been unable to create or write to the message file. When troubleshooting,
> restart the synchronization with verbose history logging and specify an
> output file to which to write.
> 2007-11-06 14:17:51.641 OLE DB Subscriber 'LOC146': {call
> sys.sp_MSadd_merge_history90
> (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
> 2007-11-06 14:17:51.641 Percent Complete: 3
> 2007-11-06 14:17:51.641 Could not load the DLL xprepl.dll, or one of the
> DLLs it references. Reason: 126(The specified module could not be found.).
> 2007-11-06 14:17:51.641 OLE DB Distributor 'SQLSERVER1': {call
> sys.sp_MSadd_merge_history90
> (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
> 2007-11-06 14:17:51.672 Percent Complete: 0
> 2007-11-06 14:17:51.672 Category:SQLSERVER
> Source: LOC146
> Number: 17750
> Message: Could not load the DLL xprepl.dll, or one of the DLLs it
> references. Reason: 126(The specified module could not be found.).
> 2007-11-06 14:17:51.688 Percent Complete: 0
> 2007-11-06 14:17:51.688 Category:NULL
> Source: Merge Replication Provider
> Number: -2147201001
> Message: The merge process was unable to deliver the snapshot to the
> Subscriber. If using Web synchronization, the merge process may have been
> unable to create or write to the message file. When troubleshooting, restart
> the synchronization with verbose history logging and specify an output file
> to which to write.
>
From: jaylou on 15 Nov 2007 08:06
Actually, this issue was with my image that was created on the box. I
reimaged the machine and all was well.

Thanks for the response.


"Chris" wrote:

>
> Replication is not installed by default on SQL Server Express edition.
>
> see "How to: Install Replication During SQL Server Express Setup" in SQL
> Express documentation.
>
> ChrisB MCDBA
> MSSQLConsulting.com
>
> "jaylou" wrote:
>
> > Hi all,
> > I had a hard drive crash and I rebuilt a SQL 2005 Express. I used an image
> > I have been using for about 5 other locations. I renamed everything as I did
> > for all my other locations and I tried to turn replication on for this new
> > box. At first it failed because the subscription was invalid. I dropped and
> > recreated it. I added an output file with OutputVerboseLevel 2.
> >
> > I attached the last lines of the file below. Hopefully someone can decipher
> > what the issue is. The DLL being referenced is not on my Box nor is it on
> > any of my other boxes where my replication is having no issues. The only
> > references I have found for this DLL is for SQL2000 SP3. My publisher is
> > SQL2005 Standard SP2 and this is SQL2005 Express Edition SP2.
> >
> > The error I am getting in my file is:
> >
> > 2007-11-06 14:17:51.609 OLE DB Subscriber 'LOC146':
> > sp_MSacquiresnapshotdeliverysessionlock
> > 2007-11-06 14:17:51.609 OLE DB Subscriber 'LOC146':
> > sp_MStrypurgingoldsnapshotdeliveryprogress
> > 2007-11-06 14:17:51.625 OLE DB Subscriber 'LOC146': {call
> > sys.sp_MSadd_merge_history90
> > (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
> > 2007-11-06 14:17:51.641 [3%] [0 sec remaining] Percent Complete: 3
> > 2007-11-06 14:17:51.641 Preparing table 'APPLICATION_VERSION_CONTROL' for
> > merge replication
> > 2007-11-06 14:17:51.641 OLE DB Distributor 'SQLSERVER1': {call
> > sys.sp_MSadd_merge_history90
> > (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
> > 2007-11-06 14:17:51.641 The merge process was unable to deliver the snapshot
> > to the Subscriber. If using Web synchronization, the merge process may have
> > been unable to create or write to the message file. When troubleshooting,
> > restart the synchronization with verbose history logging and specify an
> > output file to which to write.
> > 2007-11-06 14:17:51.641 OLE DB Subscriber 'LOC146': {call
> > sys.sp_MSadd_merge_history90
> > (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
> > 2007-11-06 14:17:51.641 Percent Complete: 3
> > 2007-11-06 14:17:51.641 Could not load the DLL xprepl.dll, or one of the
> > DLLs it references. Reason: 126(The specified module could not be found.).
> > 2007-11-06 14:17:51.641 OLE DB Distributor 'SQLSERVER1': {call
> > sys.sp_MSadd_merge_history90
> > (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
> > 2007-11-06 14:17:51.672 Percent Complete: 0
> > 2007-11-06 14:17:51.672 Category:SQLSERVER
> > Source: LOC146
> > Number: 17750
> > Message: Could not load the DLL xprepl.dll, or one of the DLLs it
> > references. Reason: 126(The specified module could not be found.).
> > 2007-11-06 14:17:51.688 Percent Complete: 0
> > 2007-11-06 14:17:51.688 Category:NULL
> > Source: Merge Replication Provider
> > Number: -2147201001
> > Message: The merge process was unable to deliver the snapshot to the
> > Subscriber. If using Web synchronization, the merge process may have been
> > unable to create or write to the message file. When troubleshooting, restart
> > the synchronization with verbose history logging and specify an output file
> > to which to write.
> >
 | 
Pages: 1
Prev: Login Failed for user "Distributor_admin'
Next: Cannot insert explicit value for identity column