A Different Login failed for user sa problem

Hello,

I know there are already topics on the "Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection" problem but I think this one might be different.

I am working with 2 servers, both running Windows Server 2003 with 1 running SQL Server 2000 and the other acting as a Web Server, and a PC running Windows XP Pro as a development machine - all of which are on the same domain.

I am developing a couple of ASP.NET web applications, and this is where the problem occurs. If I try to connect to the SQL database with the web application running on the development PC I get the "Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection" error message.

This is where it gets interesting. If I take a copy of the code that is running on the development PC and run it on the Web Server, it is able to connect to the SQL database without any problems.

The Authentication mode is set to SQL Server and Windows. I have tried several different things with our Techs and we get the same problem.

Any ideas or suggestions would be greatly appreciated as we are totally stumped.

Thanks,
AlHowdy

Never, ever, ever, ever has NT authentication on SQL been bullet proof...then mix that with multiple versions of VB & SQL & W2K & W2K3 and....aw man...game over.....

Worth trying using plain SQL authentication ( if thats acceptible in your environment ) and see how that goes - at least it will get your app working initially. Then work on the NT authentication bit.

You may wind up having to wait for the next SP for everything if its a bug.

Cheers,

SG.|||All I am using at the moment is SQL authentication and I have absolutely no interest in using NT or Windows Authentication.

Thanks anyway,
Al|||Howdy,

Sounds like connection thinks it is using a trusted connection...can you force it to be sure its using straight SQL authentication? I have seen similar errors with sql configured apps trying to use ODBC connections configured fro NT authentication.

HTH

Cheers,

SG|||Go to the enterprise manager, right click on the server, in the properties, select security tab and select the first option(SQL Server and Windows NT) in the Authentication.

Now try connecting from your application.

A connection to the report server failed

Hello,

I am getting extremely frustrated with this situation. I have two machines that are both connected to the domain and I am logged into both. I also have a W2K3 Server that is hosting SQL Server 2005 Standard. Both desktop machines have SSMS and all machines including server are now SP1. On one machine I can connect to reporting services just fine, but on the other I am getting the following error:

TITLE: Connect to Server

Cannot connect to MEDUSA.

ADDITIONAL INFORMATION:

A connection to the report server failed. Most likely, you do not have permission to connect to the computer. You should either try to connect using report server URL for the Server name, or if the Distributed COM Users group exists on the remote computer, verify that you are a member. (Microsoft.SqlServer.Management.UI.RSClient)

Now I can use the machine that cannot connect to this particular server and connect to my other machine just fine and vice versa. I am also having to enter login information each time I am trying to deploy new reports, which wasn't the case before. This happened out of the blue and I have not been able to find a reason for it. I can't connect through using the url either it gives me a 401 unauthorized error. I need to find an answer to this as soon as possible as this is causing me a multitude of issues. I hope someone can help me....thanks in advanced!

For those who are interested the solution is that your profile is corrupt. I tried everything I possibly could until I created a new profile on the machine I was having troubles connecting with. As soon as I did this it worked fine. Something must get funky with the authentication and somehow that is tied to the profile.|||

I was also having the problem of connecting from my xp machine sql management studio to a win2k3 reporting services 2005 and was getting

"can not connect to Report server from SQL SERVER 2005 Management studio error" although if a term served into another machine it would connect just fine and I am a domain admin.

In the end I found and removed the server from my user accounts. At some point i must have added the server to my user accounts under a different name for testing and it was connecting using that account instead of my login account.

Just another place to look if you are having problems connecting.

Hope this helps!!

A connection to the report server failed

Hello,

I am getting extremely frustrated with this situation. I have two machines that are both connected to the domain and I am logged into both. I also have a W2K3 Server that is hosting SQL Server 2005 Standard. Both desktop machines have SSMS and all machines including server are now SP1. On one machine I can connect to reporting services just fine, but on the other I am getting the following error:

TITLE: Connect to Server

Cannot connect to MEDUSA.

ADDITIONAL INFORMATION:

A connection to the report server failed. Most likely, you do not have permission to connect to the computer. You should either try to connect using report server URL for the Server name, or if the Distributed COM Users group exists on the remote computer, verify that you are a member. (Microsoft.SqlServer.Management.UI.RSClient)

Now I can use the machine that cannot connect to this particular server and connect to my other machine just fine and vice versa. I am also having to enter login information each time I am trying to deploy new reports, which wasn't the case before. This happened out of the blue and I have not been able to find a reason for it. I can't connect through using the url either it gives me a 401 unauthorized error. I need to find an answer to this as soon as possible as this is causing me a multitude of issues. I hope someone can help me....thanks in advanced!

For those who are interested the solution is that your profile is corrupt. I tried everything I possibly could until I created a new profile on the machine I was having troubles connecting with. As soon as I did this it worked fine. Something must get funky with the authentication and somehow that is tied to the profile.|||

I was also having the problem of connecting from my xp machine sql management studio to a win2k3 reporting services 2005 and was getting

"can not connect to Report server from SQL SERVER 2005 Management studio error" although if a term served into another machine it would connect just fine and I am a domain admin.

In the end I found and removed the server from my user accounts. At some point i must have added the server to my user accounts under a different name for testing and it was connecting using that account instead of my login account.

Just another place to look if you are having problems connecting.

Hope this helps!!

sql

a connection could not be made to the data source

I am trying to process a cube still it failed since "Errors in the high-level relational engine. A connection could not be made to the data source with the DataSource of "MY-DATASOURCE", Name of "MY-DATASOURCE").

The sql instance is running on the same machine in where I am working the solution. Can someone provide some hints on what to do to resolve this issue?

By looking at the "AdventuresWorks" sample the main difference that I have in my solution is that I have an instance and the AW sample is pointing to the default instance using the "localhost" reference only. My datasource connection is refered as "MyHost\MySqlInstance"...
I used the wong impersonation settings! I changed those and now I am processing the cube.

A column has been specified more than once in the order by list.

I have a function dbo.FIELD that extracts a part of the value from a field. I want to get two pieces and order by them.

Select failed: Warning: 169(15): A column has been specified more than once in the order by list. Columns in the order by list must be unique.

How can I do this?

SELECT WORK_ID FROM WORK ORDER BY dbo.FIELD(WORK_ID, '*', 2) ASC, dbo.FIELD(WORK_ID, '*', 1) ASC

These work:

SELECT WORK_ID FROM WORK ORDER BY dbo.FIELD(WORK_ID, '*', 2) ASC, WORK_ID ASC

SELECT WORK_ID FROM WORK ORDER BY dbo.FIELD(WORK_ID, '*', 2) ASC, dbo.FIELD('WORK_ID', '*', 1) ASC

Since you are calling a function, and the function 'could' run two times and return the same information both time, it 'could' create a situation where a ORDER BY column is duplicated.

It seems to me that shouldn't be an issue, but it is... (I don't know why SQL Server should care if my query is 'ORDER BY LastName, LastName')

A column has been specified more than once in the order by list.

I have a function dbo.FIELD that extracts a part of the value from a field. I want to get two pieces and order by them.

Select failed: Warning: 169(15): A column has been specified more than once in the order by list. Columns in the order by list must be unique.

How can I do this?

SELECT WORK_ID FROM WORK ORDER BY dbo.FIELD(WORK_ID, '*', 2) ASC, dbo.FIELD(WORK_ID, '*', 1) ASC

These work:

SELECT WORK_ID FROM WORK ORDER BY dbo.FIELD(WORK_ID, '*', 2) ASC, WORK_ID ASC

SELECT WORK_ID FROM WORK ORDER BY dbo.FIELD(WORK_ID, '*', 2) ASC, dbo.FIELD('WORK_ID', '*', 1) ASC

Check here for responses to your duplicate post in SQL Server Database Engine.

Often, the quality of the responses received is related to our ability to ‘bounce’ ideas off of each other. In the future, to make it easier for us to offer you assistance, and to prevent folks from wasting time on already answered questions, please don't post to multiple newsgroups. Choose the one that best fits your question and post there. Only post to another newsgroup if you get no answer in a day or two (or if you accidentally posted to the wrong newsgroup –and you indicate that you've already posted elsewhere).

A Challenging Query

Hi EveryBody,
Here is a very interesting SQL which I failed to solve.
I have two tables called Main and Notes.Table notes has id field which is
primary key of the Main table and foreign key in notes table. Notes table has
an identity column called NotesId.
What I have to do is that I have to show all data of main table but they
will be ordered depending upon a particular value of the note field in the
notes table. What I mean is : say there is ID 100,101,102,103 existing in the
main table. They may have several entries in the notes table and some of
those entries containing say "Desired match" in their note field.
What I want : in time of selection those entries who have "Desired Match" in
their notes field they will be coming first in their chronological order.
But their are some constraints : you cannot use any group by or distinct
clause in the query. and the resultant data cannot have any duplicate rows
Here is what I tried :
select top 100 percent main.*,notes.note,notes.date
from main left join notes on main.id=notes.id
order by convert(
numeric,
case
when notes.note like('Desired%') then '100000'
else
'500'
end
) desc,notes.date asc
But problem is that this result set contains duplicate data
Any new or better Idea.
Thanks
Kaushik
On Wed, 23 Mar 2005 22:23:01 -0800, Kaushik wrote:

>Hi EveryBody,
>Here is a very interesting SQL which I failed to solve.
(snip)
Hi Kaushik,
I love solving SQL challenges. But I'm not quite as good at trying to
understand verbose descriptions. I'll refer you to a website that
explains what information you should include in a post in order for us
to help you: www.aspfaq.com/5006. If you follow the guidelines given
there, I'll probably be able to help you.

>But their are some constraints : you cannot use any group by or distinct
>clause in the query. and the resultant data cannot have any duplicate rows
I understand the need to eliminate duplicate rows, but the constraints
to not use GROUP BY or DISTINCT makes no sense to me. Can you explain
the reason for this restriction? Because I really don't understand why
any SQL coder would voluntarily part with part of the tools he needs to
do his job.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)

A call to SQL Server Reconciler failed. SQL Server 2005, SQL Server Mobile merge replication

Hi,

Iam trying to perform merge replication between SQL Server 2005 and SQL server mobile. It has previously been working. Recently something is causing the following problem when i try to perform the merge. I grabed the following output from the replication monitor.
Error messages:
An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQLServer, Error number: 2147767868)
Get help: http://help/2147767868

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. (Source: MSSQLServer, Error number: 2147766295)
Get help: http://help/2147766295

From Sql Server managment studio i:
--> right clicked on the publication
--> selected view snapshot agent status
--> i then pressed start
the result was [100%] A snapshot of 8 article(s) was generated.

I then retried to sync it and it had the same problem. I upped then logging to level 3. The log produced the following:

2005/10/02 20:56:18 Hr=00000000 Compression Level set to 1
2005/10/02 20:56:18 Hr=00000000 Count of active RSCBs = 0
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Compressed bytes in = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Uncompressed bytes in = 309
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Responding to OpenWrite, total bytes = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 C:\Program Files\Microsoft SQL Server 2005 Mobile Edition\server\30.4E1B0DC71663_8B01FD62-37A2-8AD5-F4E5-B5FF8162902B 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=00000000 Synchronize prepped 0
<PARAMS RSCB="15" HostName="" Publisher="i-removed-this-for-the-post" PublisherNetwork="" PublisherAddress="" PublisherSecurityMode="1" PublisherLogin="" PublisherDatabase="CARSRBO_DB" Publication="CARSRBO_DB" ProfileName="DEFAULT" SubscriberServer="CARSRBO_DB - 4e1b0dc71663" SubscriberDatabasePath="Program Files\carsmr.ui\CARSMR_DB.sdf" Distributor="i-removed-this-for-the-post" DistributorNetwork="" DistributorAddress="" DistributorSecurityMode="1" DistributorLogin="" ExchangeType="3" ValidationType="0" QueryTimeout="300" LoginTimeout="15" SnapshotTransferType="0" DistributorSessionId="72"/>
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=8004563C An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. -2147199428
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=80045017 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. -2147201001
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=80004005 SyncCheck responding 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=00000000 Removing this RSCB 0

Note i noticed that the "MSMerge_rowtrack" does not exist in the snapshot folder only variations in the format MSMerge_rowtrack*.bcp such as MSMerge_rowtrack90.bcp

Any advice on this issue would be appreciated as i have not found anything solid through google.

Thanks in advance,
pdns

If looks like you have not configured the read permissions on the snapshot folder.
The error code 80045017 seems to indicate a permission problem.
Can you try the sync after you give read permissions to the snapshot folder/subfolder and all files.
And note that if you using absolute paths (instead of share) you will need to give NTFS permissions too.

80045017 The SQL Server CE Replication Provider must have read permissions to the snapshot folder. Read permission is needed so the SQL Server CE Replication Provider can download the initial subscription to the Windows CE-based device.

The identity under which the SQL Server CE Replication Provider runs depends upon how IIS authentication is configured.

|||Hi Mahesh,

I think you were right in it being a security problem.

i followed the tutorial at http://msdn2.microsoft.com/en-us/library/ms240364
and the issue is now resolved.

I am not sure of exactly where the permission problem was.

Could it have been that for the SQL Server 2005 security properties that the settings for Security -> Logins -> Computername/IUSR_*
did not have MSmerge_* database roles assigned for the database ?|||Glad that the issue is resolved.
I think the user ISUR* did not read permissions on the snapshot folder.|||

I have following error in propagate while subscription, the error like this.

Error messages:

The schema script 'C:\Program Files\Microsoft SQL Server\MSSQL.5\MSSQL\ReplData\unc\TOSHIBA$SQLSERVER2005ENT_TESTMOBILE_TESTSQLMOBILE\20060303170979\tblTest_2.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147024891)
Get help: http://help/MSSQL_REPL-2147024891

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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001

I try to synchronization from SQL Server 2005 Enterprise to SQL Mobile 2005. While add new subscription on SQL Mobile 2005 it raised error like this on synchronizing data :

- Synchronizing Data (100%) (Error)

Messages

Initializing SQL Server Reconciler has failed.
HRESULT 0x80045901 (29045)

The remote server "TOSHIBA\SQLSERVER2005ENT" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
HRESULT 0x00003700 (0)

{call sp_helpdistpublisher (N'TOSHIBA\SQLSERVER2005ENT') }
HRESULT 0x00000000 (0)

You do not have the required permissions to complete the operation.
HRESULT 0x0000372E (0)

The operation could not be completed.

Any way to fix this ? The both error are on the same scene (while add SQL Mobile Subscription).

Thanks.

|||

Hello...

I had the same problem the past few days...and what solved it for me was two things:

1. making sure that the windows user accounts for the replication had read/write control of the replication problems.

2. making sure that those windows user accounts (and my one sql login account that is used for anonymous access) were in the Publication Access List for the publication.

|||how do I check if the user account is in publication access list or not? Thx.|||should be somewhere on the publication properties page. Search books online for "merge publication access list" for more information.|||

I found the list and verified the the two things you mentioned. Yet I still have the exact same error message as you did. I am trying to snyc sql server 2005 standard to SQL mobile. Our IIS is on a seperate box. Did you use IIS on a seperate box too? Much obliged to your info.

|||We are also synchronizing between sql server 2005 standard and sql server Mobile. However, we are running IIS and SQL Server on the same box.|||We are experiencing the same symptoms. All was going fine until yesterday morning. Nobody has changed anything and the issue is not happening for all of the users. This makes me suspcious of the theory that permissions are at fault.

Can anyone who had this problem and resolved it recount what processes they went through?

Thanks|||Additionally you have to make sure that the user connecting to the IIS site has permissions to launch and execute the replisapi.dll. This can be done using the Configure Web Sync wizard.|||Also check if the snapshot is still valid and the files are not cleaned up. If they arent, then rerun the snapshot agent.|||Re-runnning the snapshot is what we do to get it going again - but this does not explain why there is different behaviour for individual users.

Each user has an individual snapshot - should they be updated? The normal snapshot gets run every night so shouldn't be out of date.

What we have established is that this only occurs for some users when the application has been re-installed. (Again, not for all users).|||

When a normal snapshot runs, it invalidates all the dynamic snapshots. Also if the snapshot is expired due to retention or other admin actions then the snapshot needs to be run to make the syncs succeed.

What do you mean by application has been re-installed? On what server, and what does it mean to the subscriber?

A call to SQL Server Reconciler failed. SQL Server 2005, SQL Server Mobile merge replication

Hi,

Iam trying to perform merge replication between SQL Server 2005 and SQL server mobile. It has previously been working. Recently something is causing the following problem when i try to perform the merge. I grabed the following output from the replication monitor.
Error messages:
An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQLServer, Error number: 2147767868)
Get help: http://help/2147767868

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. (Source: MSSQLServer, Error number: 2147766295)
Get help: http://help/2147766295

From Sql Server managment studio i:
--> right clicked on the publication
--> selected view snapshot agent status
--> i then pressed start
the result was [100%] A snapshot of 8 article(s) was generated.

I then retried to sync it and it had the same problem. I upped then logging to level 3. The log produced the following:

2005/10/02 20:56:18 Hr=00000000 Compression Level set to 1
2005/10/02 20:56:18 Hr=00000000 Count of active RSCBs = 0
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Compressed bytes in = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Uncompressed bytes in = 309
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Responding to OpenWrite, total bytes = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 C:\Program Files\Microsoft SQL Server 2005 Mobile Edition\server\30.4E1B0DC71663_8B01FD62-37A2-8AD5-F4E5-B5FF8162902B 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=00000000 Synchronize prepped 0
<PARAMS RSCB="15" HostName="" Publisher="i-removed-this-for-the-post" PublisherNetwork="" PublisherAddress="" PublisherSecurityMode="1" PublisherLogin="" PublisherDatabase="CARSRBO_DB" Publication="CARSRBO_DB" ProfileName="DEFAULT" SubscriberServer="CARSRBO_DB - 4e1b0dc71663" SubscriberDatabasePath="Program Files\carsmr.ui\CARSMR_DB.sdf" Distributor="i-removed-this-for-the-post" DistributorNetwork="" DistributorAddress="" DistributorSecurityMode="1" DistributorLogin="" ExchangeType="3" ValidationType="0" QueryTimeout="300" LoginTimeout="15" SnapshotTransferType="0" DistributorSessionId="72"/>
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=8004563C An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. -2147199428
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=80045017 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. -2147201001
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=80004005 SyncCheck responding 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=00000000 Removing this RSCB 0

Note i noticed that the "MSMerge_rowtrack" does not exist in the snapshot folder only variations in the format MSMerge_rowtrack*.bcp such as MSMerge_rowtrack90.bcp

Any advice on this issue would be appreciated as i have not found anything solid through google.

Thanks in advance,
pdns

If looks like you have not configured the read permissions on the snapshot folder.
The error code 80045017 seems to indicate a permission problem.
Can you try the sync after you give read permissions to the snapshot folder/subfolder and all files.
And note that if you using absolute paths (instead of share) you will need to give NTFS permissions too.

80045017 The SQL Server CE Replication Provider must have read permissions to the snapshot folder. Read permission is needed so the SQL Server CE Replication Provider can download the initial subscription to the Windows CE-based device.

The identity under which the SQL Server CE Replication Provider runs depends upon how IIS authentication is configured.

|||Hi Mahesh,

I think you were right in it being a security problem.

i followed the tutorial at http://msdn2.microsoft.com/en-us/library/ms240364
and the issue is now resolved.

I am not sure of exactly where the permission problem was.

Could it have been that for the SQL Server 2005 security properties that the settings for Security -> Logins -> Computername/IUSR_*
did not have MSmerge_* database roles assigned for the database ?|||Glad that the issue is resolved.
I think the user ISUR* did not read permissions on the snapshot folder.|||

I have following error in propagate while subscription, the error like this.

Error messages:

The schema script 'C:\Program Files\Microsoft SQL Server\MSSQL.5\MSSQL\ReplData\unc\TOSHIBA$SQLSERVER2005ENT_TESTMOBILE_TESTSQLMOBILE\20060303170979\tblTest_2.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147024891)
Get help: http://help/MSSQL_REPL-2147024891

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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001

I try to synchronization from SQL Server 2005 Enterprise to SQL Mobile 2005. While add new subscription on SQL Mobile 2005 it raised error like this on synchronizing data :

- Synchronizing Data (100%) (Error)

Messages

Initializing SQL Server Reconciler has failed.
HRESULT 0x80045901 (29045)

The remote server "TOSHIBA\SQLSERVER2005ENT" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
HRESULT 0x00003700 (0)

{call sp_helpdistpublisher (N'TOSHIBA\SQLSERVER2005ENT') }
HRESULT 0x00000000 (0)

You do not have the required permissions to complete the operation.
HRESULT 0x0000372E (0)

The operation could not be completed.

Any way to fix this ? The both error are on the same scene (while add SQL Mobile Subscription).

Thanks.

|||

Hello...

I had the same problem the past few days...and what solved it for me was two things:

1. making sure that the windows user accounts for the replication had read/write control of the replication problems.

2. making sure that those windows user accounts (and my one sql login account that is used for anonymous access) were in the Publication Access List for the publication.

|||how do I check if the user account is in publication access list or not? Thx.|||should be somewhere on the publication properties page. Search books online for "merge publication access list" for more information.|||

I found the list and verified the the two things you mentioned. Yet I still have the exact same error message as you did. I am trying to snyc sql server 2005 standard to SQL mobile. Our IIS is on a seperate box. Did you use IIS on a seperate box too? Much obliged to your info.

|||We are also synchronizing between sql server 2005 standard and sql server Mobile. However, we are running IIS and SQL Server on the same box.|||We are experiencing the same symptoms. All was going fine until yesterday morning. Nobody has changed anything and the issue is not happening for all of the users. This makes me suspcious of the theory that permissions are at fault.

Can anyone who had this problem and resolved it recount what processes they went through?

Thanks|||Additionally you have to make sure that the user connecting to the IIS site has permissions to launch and execute the replisapi.dll. This can be done using the Configure Web Sync wizard.|||Also check if the snapshot is still valid and the files are not cleaned up. If they arent, then rerun the snapshot agent.|||Re-runnning the snapshot is what we do to get it going again - but this does not explain why there is different behaviour for individual users.

Each user has an individual snapshot - should they be updated? The normal snapshot gets run every night so shouldn't be out of date.

What we have established is that this only occurs for some users when the application has been re-installed. (Again, not for all users).|||

When a normal snapshot runs, it invalidates all the dynamic snapshots. Also if the snapshot is expired due to retention or other admin actions then the snapshot needs to be run to make the syncs succeed.

What do you mean by application has been re-installed? On what server, and what does it mean to the subscriber?

A call to SQL Server Reconciler failed. SQL Server 2005, SQL Server Mobile merge replication

Hi,

Iam trying to perform merge replication between SQL Server 2005 and SQL server mobile. It has previously been working. Recently something is causing the following problem when i try to perform the merge. I grabed the following output from the replication monitor.
Error messages:
An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQLServer, Error number: 2147767868)
Get help: http://help/2147767868

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. (Source: MSSQLServer, Error number: 2147766295)
Get help: http://help/2147766295

From Sql Server managment studio i:
--> right clicked on the publication
--> selected view snapshot agent status
--> i then pressed start
the result was [100%] A snapshot of 8 article(s) was generated.

I then retried to sync it and it had the same problem. I upped then logging to level 3. The log produced the following:

2005/10/02 20:56:18 Hr=00000000 Compression Level set to 1
2005/10/02 20:56:18 Hr=00000000 Count of active RSCBs = 0
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Compressed bytes in = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Uncompressed bytes in = 309
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Responding to OpenWrite, total bytes = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 C:\Program Files\Microsoft SQL Server 2005 Mobile Edition\server\30.4E1B0DC71663_8B01FD62-37A2-8AD5-F4E5-B5FF8162902B 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=00000000 Synchronize prepped 0
<PARAMS RSCB="15" HostName="" Publisher="i-removed-this-for-the-post" PublisherNetwork="" PublisherAddress="" PublisherSecurityMode="1" PublisherLogin="" PublisherDatabase="CARSRBO_DB" Publication="CARSRBO_DB" ProfileName="DEFAULT" SubscriberServer="CARSRBO_DB - 4e1b0dc71663" SubscriberDatabasePath="Program Files\carsmr.ui\CARSMR_DB.sdf" Distributor="i-removed-this-for-the-post" DistributorNetwork="" DistributorAddress="" DistributorSecurityMode="1" DistributorLogin="" ExchangeType="3" ValidationType="0" QueryTimeout="300" LoginTimeout="15" SnapshotTransferType="0" DistributorSessionId="72"/>
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=8004563C An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. -2147199428
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=80045017 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. -2147201001
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=80004005 SyncCheck responding 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=00000000 Removing this RSCB 0

Note i noticed that the "MSMerge_rowtrack" does not exist in the snapshot folder only variations in the format MSMerge_rowtrack*.bcp such as MSMerge_rowtrack90.bcp

Any advice on this issue would be appreciated as i have not found anything solid through google.

Thanks in advance,
pdns

If looks like you have not configured the read permissions on the snapshot folder.
The error code 80045017 seems to indicate a permission problem.
Can you try the sync after you give read permissions to the snapshot folder/subfolder and all files.
And note that if you using absolute paths (instead of share) you will need to give NTFS permissions too.

80045017 The SQL Server CE Replication Provider must have read permissions to the snapshot folder. Read permission is needed so the SQL Server CE Replication Provider can download the initial subscription to the Windows CE-based device.

The identity under which the SQL Server CE Replication Provider runs depends upon how IIS authentication is configured.

|||Hi Mahesh,

I think you were right in it being a security problem.

i followed the tutorial at http://msdn2.microsoft.com/en-us/library/ms240364
and the issue is now resolved.

I am not sure of exactly where the permission problem was.

Could it have been that for the SQL Server 2005 security properties that the settings for Security -> Logins -> Computername/IUSR_*
did not have MSmerge_* database roles assigned for the database ?|||Glad that the issue is resolved.
I think the user ISUR* did not read permissions on the snapshot folder.|||

I have following error in propagate while subscription, the error like this.

Error messages:

The schema script 'C:\Program Files\Microsoft SQL Server\MSSQL.5\MSSQL\ReplData\unc\TOSHIBA$SQLSERVER2005ENT_TESTMOBILE_TESTSQLMOBILE\20060303170979\tblTest_2.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147024891)
Get help: http://help/MSSQL_REPL-2147024891

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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001

I try to synchronization from SQL Server 2005 Enterprise to SQL Mobile 2005. While add new subscription on SQL Mobile 2005 it raised error like this on synchronizing data :

- Synchronizing Data (100%) (Error)

Messages

Initializing SQL Server Reconciler has failed.
HRESULT 0x80045901 (29045)

The remote server "TOSHIBA\SQLSERVER2005ENT" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
HRESULT 0x00003700 (0)

{call sp_helpdistpublisher (N'TOSHIBA\SQLSERVER2005ENT') }
HRESULT 0x00000000 (0)

You do not have the required permissions to complete the operation.
HRESULT 0x0000372E (0)

The operation could not be completed.

Any way to fix this ? The both error are on the same scene (while add SQL Mobile Subscription).

Thanks.

|||

Hello...

I had the same problem the past few days...and what solved it for me was two things:

1. making sure that the windows user accounts for the replication had read/write control of the replication problems.

2. making sure that those windows user accounts (and my one sql login account that is used for anonymous access) were in the Publication Access List for the publication.

|||how do I check if the user account is in publication access list or not? Thx.|||should be somewhere on the publication properties page. Search books online for "merge publication access list" for more information.|||

I found the list and verified the the two things you mentioned. Yet I still have the exact same error message as you did. I am trying to snyc sql server 2005 standard to SQL mobile. Our IIS is on a seperate box. Did you use IIS on a seperate box too? Much obliged to your info.

|||We are also synchronizing between sql server 2005 standard and sql server Mobile. However, we are running IIS and SQL Server on the same box.|||We are experiencing the same symptoms. All was going fine until yesterday morning. Nobody has changed anything and the issue is not happening for all of the users. This makes me suspcious of the theory that permissions are at fault.

Can anyone who had this problem and resolved it recount what processes they went through?

Thanks|||Additionally you have to make sure that the user connecting to the IIS site has permissions to launch and execute the replisapi.dll. This can be done using the Configure Web Sync wizard.|||Also check if the snapshot is still valid and the files are not cleaned up. If they arent, then rerun the snapshot agent.|||Re-runnning the snapshot is what we do to get it going again - but this does not explain why there is different behaviour for individual users.

Each user has an individual snapshot - should they be updated? The normal snapshot gets run every night so shouldn't be out of date.

What we have established is that this only occurs for some users when the application has been re-installed. (Again, not for all users).|||

When a normal snapshot runs, it invalidates all the dynamic snapshots. Also if the snapshot is expired due to retention or other admin actions then the snapshot needs to be run to make the syncs succeed.

What do you mean by application has been re-installed? On what server, and what does it mean to the subscriber?

A call to SQL Server Reconciler failed. SQL Server 2005, SQL Server Mobile merge replication

Hi,

Iam trying to perform merge replication between SQL Server 2005 and SQL server mobile. It has previously been working. Recently something is causing the following problem when i try to perform the merge. I grabed the following output from the replication monitor.
Error messages:
An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQLServer, Error number: 2147767868)
Get help: http://help/2147767868

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. (Source: MSSQLServer, Error number: 2147766295)
Get help: http://help/2147766295

From Sql Server managment studio i:
--> right clicked on the publication
--> selected view snapshot agent status
--> i then pressed start
the result was [100%] A snapshot of 8 article(s) was generated.

I then retried to sync it and it had the same problem. I upped then logging to level 3. The log produced the following:

2005/10/02 20:56:18 Hr=00000000 Compression Level set to 1
2005/10/02 20:56:18 Hr=00000000 Count of active RSCBs = 0
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Compressed bytes in = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Uncompressed bytes in = 309
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Responding to OpenWrite, total bytes = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 C:\Program Files\Microsoft SQL Server 2005 Mobile Edition\server\30.4E1B0DC71663_8B01FD62-37A2-8AD5-F4E5-B5FF8162902B 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=00000000 Synchronize prepped 0
<PARAMS RSCB="15" HostName="" Publisher="i-removed-this-for-the-post" PublisherNetwork="" PublisherAddress="" PublisherSecurityMode="1" PublisherLogin="" PublisherDatabase="CARSRBO_DB" Publication="CARSRBO_DB" ProfileName="DEFAULT" SubscriberServer="CARSRBO_DB - 4e1b0dc71663" SubscriberDatabasePath="Program Files\carsmr.ui\CARSMR_DB.sdf" Distributor="i-removed-this-for-the-post" DistributorNetwork="" DistributorAddress="" DistributorSecurityMode="1" DistributorLogin="" ExchangeType="3" ValidationType="0" QueryTimeout="300" LoginTimeout="15" SnapshotTransferType="0" DistributorSessionId="72"/>
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=8004563C An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. -2147199428
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=80045017 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. -2147201001
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=80004005 SyncCheck responding 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=00000000 Removing this RSCB 0

Note i noticed that the "MSMerge_rowtrack" does not exist in the snapshot folder only variations in the format MSMerge_rowtrack*.bcp such as MSMerge_rowtrack90.bcp

Any advice on this issue would be appreciated as i have not found anything solid through google.

Thanks in advance,
pdns

If looks like you have not configured the read permissions on the snapshot folder.
The error code 80045017 seems to indicate a permission problem.
Can you try the sync after you give read permissions to the snapshot folder/subfolder and all files.
And note that if you using absolute paths (instead of share) you will need to give NTFS permissions too.

80045017 The SQL Server CE Replication Provider must have read permissions to the snapshot folder. Read permission is needed so the SQL Server CE Replication Provider can download the initial subscription to the Windows CE-based device.

The identity under which the SQL Server CE Replication Provider runs depends upon how IIS authentication is configured.

|||Hi Mahesh,

I think you were right in it being a security problem.

i followed the tutorial at http://msdn2.microsoft.com/en-us/library/ms240364
and the issue is now resolved.

I am not sure of exactly where the permission problem was.

Could it have been that for the SQL Server 2005 security properties that the settings for Security -> Logins -> Computername/IUSR_*
did not have MSmerge_* database roles assigned for the database ?|||Glad that the issue is resolved.
I think the user ISUR* did not read permissions on the snapshot folder.|||

I have following error in propagate while subscription, the error like this.

Error messages:

The schema script 'C:\Program Files\Microsoft SQL Server\MSSQL.5\MSSQL\ReplData\unc\TOSHIBA$SQLSERVER2005ENT_TESTMOBILE_TESTSQLMOBILE\20060303170979\tblTest_2.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147024891)
Get help: http://help/MSSQL_REPL-2147024891

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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001

I try to synchronization from SQL Server 2005 Enterprise to SQL Mobile 2005. While add new subscription on SQL Mobile 2005 it raised error like this on synchronizing data :

- Synchronizing Data (100%) (Error)

Messages

Initializing SQL Server Reconciler has failed.
HRESULT 0x80045901 (29045)

The remote server "TOSHIBA\SQLSERVER2005ENT" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
HRESULT 0x00003700 (0)

{call sp_helpdistpublisher (N'TOSHIBA\SQLSERVER2005ENT') }
HRESULT 0x00000000 (0)

You do not have the required permissions to complete the operation.
HRESULT 0x0000372E (0)

The operation could not be completed.

Any way to fix this ? The both error are on the same scene (while add SQL Mobile Subscription).

Thanks.

|||

Hello...

I had the same problem the past few days...and what solved it for me was two things:

1. making sure that the windows user accounts for the replication had read/write control of the replication problems.

2. making sure that those windows user accounts (and my one sql login account that is used for anonymous access) were in the Publication Access List for the publication.

|||how do I check if the user account is in publication access list or not? Thx.|||should be somewhere on the publication properties page. Search books online for "merge publication access list" for more information.|||

I found the list and verified the the two things you mentioned. Yet I still have the exact same error message as you did. I am trying to snyc sql server 2005 standard to SQL mobile. Our IIS is on a seperate box. Did you use IIS on a seperate box too? Much obliged to your info.

|||We are also synchronizing between sql server 2005 standard and sql server Mobile. However, we are running IIS and SQL Server on the same box.|||We are experiencing the same symptoms. All was going fine until yesterday morning. Nobody has changed anything and the issue is not happening for all of the users. This makes me suspcious of the theory that permissions are at fault.

Can anyone who had this problem and resolved it recount what processes they went through?

Thanks|||Additionally you have to make sure that the user connecting to the IIS site has permissions to launch and execute the replisapi.dll. This can be done using the Configure Web Sync wizard.|||Also check if the snapshot is still valid and the files are not cleaned up. If they arent, then rerun the snapshot agent.|||Re-runnning the snapshot is what we do to get it going again - but this does not explain why there is different behaviour for individual users.

Each user has an individual snapshot - should they be updated? The normal snapshot gets run every night so shouldn't be out of date.

What we have established is that this only occurs for some users when the application has been re-installed. (Again, not for all users).|||

When a normal snapshot runs, it invalidates all the dynamic snapshots. Also if the snapshot is expired due to retention or other admin actions then the snapshot needs to be run to make the syncs succeed.

What do you mean by application has been re-installed? On what server, and what does it mean to the subscriber?

sql

A call to SQL Server Reconciler failed. SQL Server 2005, SQL Server Mobile merge replication

Hi,

Iam trying to perform merge replication between SQL Server 2005 and SQL server mobile. It has previously been working. Recently something is causing the following problem when i try to perform the merge. I grabed the following output from the replication monitor.
Error messages:
An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQLServer, Error number: 2147767868)
Get help: http://help/2147767868

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. (Source: MSSQLServer, Error number: 2147766295)
Get help: http://help/2147766295

From Sql Server managment studio i:
--> right clicked on the publication
--> selected view snapshot agent status
--> i then pressed start
the result was [100%] A snapshot of 8 article(s) was generated.

I then retried to sync it and it had the same problem. I upped then logging to level 3. The log produced the following:

2005/10/02 20:56:18 Hr=00000000 Compression Level set to 1
2005/10/02 20:56:18 Hr=00000000 Count of active RSCBs = 0
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Compressed bytes in = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Uncompressed bytes in = 309
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Responding to OpenWrite, total bytes = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 C:\Program Files\Microsoft SQL Server 2005 Mobile Edition\server\30.4E1B0DC71663_8B01FD62-37A2-8AD5-F4E5-B5FF8162902B 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=00000000 Synchronize prepped 0
<PARAMS RSCB="15" HostName="" Publisher="i-removed-this-for-the-post" PublisherNetwork="" PublisherAddress="" PublisherSecurityMode="1" PublisherLogin="" PublisherDatabase="CARSRBO_DB" Publication="CARSRBO_DB" ProfileName="DEFAULT" SubscriberServer="CARSRBO_DB - 4e1b0dc71663" SubscriberDatabasePath="Program Files\carsmr.ui\CARSMR_DB.sdf" Distributor="i-removed-this-for-the-post" DistributorNetwork="" DistributorAddress="" DistributorSecurityMode="1" DistributorLogin="" ExchangeType="3" ValidationType="0" QueryTimeout="300" LoginTimeout="15" SnapshotTransferType="0" DistributorSessionId="72"/>
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=8004563C An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. -2147199428
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=80045017 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. -2147201001
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=80004005 SyncCheck responding 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=00000000 Removing this RSCB 0

Note i noticed that the "MSMerge_rowtrack" does not exist in the snapshot folder only variations in the format MSMerge_rowtrack*.bcp such as MSMerge_rowtrack90.bcp

Any advice on this issue would be appreciated as i have not found anything solid through google.

Thanks in advance,
pdns

If looks like you have not configured the read permissions on the snapshot folder.
The error code 80045017 seems to indicate a permission problem.
Can you try the sync after you give read permissions to the snapshot folder/subfolder and all files.
And note that if you using absolute paths (instead of share) you will need to give NTFS permissions too.

80045017 The SQL Server CE Replication Provider must have read permissions to the snapshot folder. Read permission is needed so the SQL Server CE Replication Provider can download the initial subscription to the Windows CE-based device.

The identity under which the SQL Server CE Replication Provider runs depends upon how IIS authentication is configured.

|||Hi Mahesh,

I think you were right in it being a security problem.

i followed the tutorial at http://msdn2.microsoft.com/en-us/library/ms240364
and the issue is now resolved.

I am not sure of exactly where the permission problem was.

Could it have been that for the SQL Server 2005 security properties that the settings for Security -> Logins -> Computername/IUSR_*
did not have MSmerge_* database roles assigned for the database ?|||Glad that the issue is resolved.
I think the user ISUR* did not read permissions on the snapshot folder.|||

I have following error in propagate while subscription, the error like this.

Error messages:

The schema script 'C:\Program Files\Microsoft SQL Server\MSSQL.5\MSSQL\ReplData\unc\TOSHIBA$SQLSERVER2005ENT_TESTMOBILE_TESTSQLMOBILE\20060303170979\tblTest_2.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147024891)
Get help: http://help/MSSQL_REPL-2147024891

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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001

I try to synchronization from SQL Server 2005 Enterprise to SQL Mobile 2005. While add new subscription on SQL Mobile 2005 it raised error like this on synchronizing data :

- Synchronizing Data (100%) (Error)

Messages

Initializing SQL Server Reconciler has failed.
HRESULT 0x80045901 (29045)

The remote server "TOSHIBA\SQLSERVER2005ENT" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
HRESULT 0x00003700 (0)

{call sp_helpdistpublisher (N'TOSHIBA\SQLSERVER2005ENT') }
HRESULT 0x00000000 (0)

You do not have the required permissions to complete the operation.
HRESULT 0x0000372E (0)

The operation could not be completed.

Any way to fix this ? The both error are on the same scene (while add SQL Mobile Subscription).

Thanks.

|||

Hello...

I had the same problem the past few days...and what solved it for me was two things:

1. making sure that the windows user accounts for the replication had read/write control of the replication problems.

2. making sure that those windows user accounts (and my one sql login account that is used for anonymous access) were in the Publication Access List for the publication.

|||how do I check if the user account is in publication access list or not? Thx.|||should be somewhere on the publication properties page. Search books online for "merge publication access list" for more information.|||

I found the list and verified the the two things you mentioned. Yet I still have the exact same error message as you did. I am trying to snyc sql server 2005 standard to SQL mobile. Our IIS is on a seperate box. Did you use IIS on a seperate box too? Much obliged to your info.

|||We are also synchronizing between sql server 2005 standard and sql server Mobile. However, we are running IIS and SQL Server on the same box.|||We are experiencing the same symptoms. All was going fine until yesterday morning. Nobody has changed anything and the issue is not happening for all of the users. This makes me suspcious of the theory that permissions are at fault.

Can anyone who had this problem and resolved it recount what processes they went through?

Thanks|||Additionally you have to make sure that the user connecting to the IIS site has permissions to launch and execute the replisapi.dll. This can be done using the Configure Web Sync wizard.|||Also check if the snapshot is still valid and the files are not cleaned up. If they arent, then rerun the snapshot agent.|||Re-runnning the snapshot is what we do to get it going again - but this does not explain why there is different behaviour for individual users.

Each user has an individual snapshot - should they be updated? The normal snapshot gets run every night so shouldn't be out of date.

What we have established is that this only occurs for some users when the application has been re-installed. (Again, not for all users).|||

When a normal snapshot runs, it invalidates all the dynamic snapshots. Also if the snapshot is expired due to retention or other admin actions then the snapshot needs to be run to make the syncs succeed.

What do you mean by application has been re-installed? On what server, and what does it mean to the subscriber?

A call to SQL Server Reconciler failed. SQL Server 2005, SQL Server Mobile merge replication

Hi,

Iam trying to perform merge replication between SQL Server 2005 and SQL server mobile. It has previously been working. Recently something is causing the following problem when i try to perform the merge. I grabed the following output from the replication monitor.
Error messages:
An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQLServer, Error number: 2147767868)
Get help: http://help/2147767868

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. (Source: MSSQLServer, Error number: 2147766295)
Get help: http://help/2147766295

From Sql Server managment studio i:
--> right clicked on the publication
--> selected view snapshot agent status
--> i then pressed start
the result was [100%] A snapshot of 8 article(s) was generated.

I then retried to sync it and it had the same problem. I upped then logging to level 3. The log produced the following:

2005/10/02 20:56:18 Hr=00000000 Compression Level set to 1
2005/10/02 20:56:18 Hr=00000000 Count of active RSCBs = 0
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Compressed bytes in = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Uncompressed bytes in = 309
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Responding to OpenWrite, total bytes = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 C:\Program Files\Microsoft SQL Server 2005 Mobile Edition\server\30.4E1B0DC71663_8B01FD62-37A2-8AD5-F4E5-B5FF8162902B 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=00000000 Synchronize prepped 0
<PARAMS RSCB="15" HostName="" Publisher="i-removed-this-for-the-post" PublisherNetwork="" PublisherAddress="" PublisherSecurityMode="1" PublisherLogin="" PublisherDatabase="CARSRBO_DB" Publication="CARSRBO_DB" ProfileName="DEFAULT" SubscriberServer="CARSRBO_DB - 4e1b0dc71663" SubscriberDatabasePath="Program Files\carsmr.ui\CARSMR_DB.sdf" Distributor="i-removed-this-for-the-post" DistributorNetwork="" DistributorAddress="" DistributorSecurityMode="1" DistributorLogin="" ExchangeType="3" ValidationType="0" QueryTimeout="300" LoginTimeout="15" SnapshotTransferType="0" DistributorSessionId="72"/>
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=8004563C An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. -2147199428
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=80045017 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. -2147201001
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=80004005 SyncCheck responding 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=00000000 Removing this RSCB 0

Note i noticed that the "MSMerge_rowtrack" does not exist in the snapshot folder only variations in the format MSMerge_rowtrack*.bcp such as MSMerge_rowtrack90.bcp

Any advice on this issue would be appreciated as i have not found anything solid through google.

Thanks in advance,
pdns

If looks like you have not configured the read permissions on the snapshot folder.
The error code 80045017 seems to indicate a permission problem.
Can you try the sync after you give read permissions to the snapshot folder/subfolder and all files.
And note that if you using absolute paths (instead of share) you will need to give NTFS permissions too.

80045017 The SQL Server CE Replication Provider must have read permissions to the snapshot folder. Read permission is needed so the SQL Server CE Replication Provider can download the initial subscription to the Windows CE-based device.

The identity under which the SQL Server CE Replication Provider runs depends upon how IIS authentication is configured.

|||Hi Mahesh,

I think you were right in it being a security problem.

i followed the tutorial at http://msdn2.microsoft.com/en-us/library/ms240364
and the issue is now resolved.

I am not sure of exactly where the permission problem was.

Could it have been that for the SQL Server 2005 security properties that the settings for Security -> Logins -> Computername/IUSR_*
did not have MSmerge_* database roles assigned for the database ?|||Glad that the issue is resolved.
I think the user ISUR* did not read permissions on the snapshot folder.|||

I have following error in propagate while subscription, the error like this.

Error messages:

The schema script 'C:\Program Files\Microsoft SQL Server\MSSQL.5\MSSQL\ReplData\unc\TOSHIBA$SQLSERVER2005ENT_TESTMOBILE_TESTSQLMOBILE\20060303170979\tblTest_2.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147024891)
Get help: http://help/MSSQL_REPL-2147024891

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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001

I try to synchronization from SQL Server 2005 Enterprise to SQL Mobile 2005. While add new subscription on SQL Mobile 2005 it raised error like this on synchronizing data :

- Synchronizing Data (100%) (Error)

Messages

Initializing SQL Server Reconciler has failed.
HRESULT 0x80045901 (29045)

The remote server "TOSHIBA\SQLSERVER2005ENT" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
HRESULT 0x00003700 (0)

{call sp_helpdistpublisher (N'TOSHIBA\SQLSERVER2005ENT') }
HRESULT 0x00000000 (0)

You do not have the required permissions to complete the operation.
HRESULT 0x0000372E (0)

The operation could not be completed.

Any way to fix this ? The both error are on the same scene (while add SQL Mobile Subscription).

Thanks.

|||

Hello...

I had the same problem the past few days...and what solved it for me was two things:

1. making sure that the windows user accounts for the replication had read/write control of the replication problems.

2. making sure that those windows user accounts (and my one sql login account that is used for anonymous access) were in the Publication Access List for the publication.

|||how do I check if the user account is in publication access list or not? Thx.|||should be somewhere on the publication properties page. Search books online for "merge publication access list" for more information.|||

I found the list and verified the the two things you mentioned. Yet I still have the exact same error message as you did. I am trying to snyc sql server 2005 standard to SQL mobile. Our IIS is on a seperate box. Did you use IIS on a seperate box too? Much obliged to your info.

|||We are also synchronizing between sql server 2005 standard and sql server Mobile. However, we are running IIS and SQL Server on the same box.|||We are experiencing the same symptoms. All was going fine until yesterday morning. Nobody has changed anything and the issue is not happening for all of the users. This makes me suspcious of the theory that permissions are at fault.

Can anyone who had this problem and resolved it recount what processes they went through?

Thanks|||Additionally you have to make sure that the user connecting to the IIS site has permissions to launch and execute the replisapi.dll. This can be done using the Configure Web Sync wizard.|||Also check if the snapshot is still valid and the files are not cleaned up. If they arent, then rerun the snapshot agent.|||Re-runnning the snapshot is what we do to get it going again - but this does not explain why there is different behaviour for individual users.

Each user has an individual snapshot - should they be updated? The normal snapshot gets run every night so shouldn't be out of date.

What we have established is that this only occurs for some users when the application has been re-installed. (Again, not for all users).|||

When a normal snapshot runs, it invalidates all the dynamic snapshots. Also if the snapshot is expired due to retention or other admin actions then the snapshot needs to be run to make the syncs succeed.

What do you mean by application has been re-installed? On what server, and what does it mean to the subscriber?

A call to SQL Server Reconciler failed. SQL Server 2005, SQL Server Mobile merge replication

Hi,

Iam trying to perform merge replication between SQL Server 2005 and SQL server mobile. It has previously been working. Recently something is causing the following problem when i try to perform the merge. I grabed the following output from the replication monitor.
Error messages:
An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQLServer, Error number: 2147767868)
Get help: http://help/2147767868

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. (Source: MSSQLServer, Error number: 2147766295)
Get help: http://help/2147766295

From Sql Server managment studio i:
--> right clicked on the publication
--> selected view snapshot agent status
--> i then pressed start
the result was [100%] A snapshot of 8 article(s) was generated.

I then retried to sync it and it had the same problem. I upped then logging to level 3. The log produced the following:

2005/10/02 20:56:18 Hr=00000000 Compression Level set to 1
2005/10/02 20:56:18 Hr=00000000 Count of active RSCBs = 0
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Compressed bytes in = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Uncompressed bytes in = 309
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Responding to OpenWrite, total bytes = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 C:\Program Files\Microsoft SQL Server 2005 Mobile Edition\server\30.4E1B0DC71663_8B01FD62-37A2-8AD5-F4E5-B5FF8162902B 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=00000000 Synchronize prepped 0
<PARAMS RSCB="15" HostName="" Publisher="i-removed-this-for-the-post" PublisherNetwork="" PublisherAddress="" PublisherSecurityMode="1" PublisherLogin="" PublisherDatabase="CARSRBO_DB" Publication="CARSRBO_DB" ProfileName="DEFAULT" SubscriberServer="CARSRBO_DB - 4e1b0dc71663" SubscriberDatabasePath="Program Files\carsmr.ui\CARSMR_DB.sdf" Distributor="i-removed-this-for-the-post" DistributorNetwork="" DistributorAddress="" DistributorSecurityMode="1" DistributorLogin="" ExchangeType="3" ValidationType="0" QueryTimeout="300" LoginTimeout="15" SnapshotTransferType="0" DistributorSessionId="72"/>
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=8004563C An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. -2147199428
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=80045017 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. -2147201001
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=80004005 SyncCheck responding 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=00000000 Removing this RSCB 0

Note i noticed that the "MSMerge_rowtrack" does not exist in the snapshot folder only variations in the format MSMerge_rowtrack*.bcp such as MSMerge_rowtrack90.bcp

Any advice on this issue would be appreciated as i have not found anything solid through google.

Thanks in advance,
pdns

If looks like you have not configured the read permissions on the snapshot folder.
The error code 80045017 seems to indicate a permission problem.
Can you try the sync after you give read permissions to the snapshot folder/subfolder and all files.
And note that if you using absolute paths (instead of share) you will need to give NTFS permissions too.

80045017 The SQL Server CE Replication Provider must have read permissions to the snapshot folder. Read permission is needed so the SQL Server CE Replication Provider can download the initial subscription to the Windows CE-based device.

The identity under which the SQL Server CE Replication Provider runs depends upon how IIS authentication is configured.

|||Hi Mahesh,

I think you were right in it being a security problem.

i followed the tutorial at http://msdn2.microsoft.com/en-us/library/ms240364
and the issue is now resolved.

I am not sure of exactly where the permission problem was.

Could it have been that for the SQL Server 2005 security properties that the settings for Security -> Logins -> Computername/IUSR_*
did not have MSmerge_* database roles assigned for the database ?|||Glad that the issue is resolved.
I think the user ISUR* did not read permissions on the snapshot folder.|||

I have following error in propagate while subscription, the error like this.

Error messages:

The schema script 'C:\Program Files\Microsoft SQL Server\MSSQL.5\MSSQL\ReplData\unc\TOSHIBA$SQLSERVER2005ENT_TESTMOBILE_TESTSQLMOBILE\20060303170979\tblTest_2.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147024891)
Get help: http://help/MSSQL_REPL-2147024891

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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001

I try to synchronization from SQL Server 2005 Enterprise to SQL Mobile 2005. While add new subscription on SQL Mobile 2005 it raised error like this on synchronizing data :

- Synchronizing Data (100%) (Error)

Messages

Initializing SQL Server Reconciler has failed.
HRESULT 0x80045901 (29045)

The remote server "TOSHIBA\SQLSERVER2005ENT" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
HRESULT 0x00003700 (0)

{call sp_helpdistpublisher (N'TOSHIBA\SQLSERVER2005ENT') }
HRESULT 0x00000000 (0)

You do not have the required permissions to complete the operation.
HRESULT 0x0000372E (0)

The operation could not be completed.

Any way to fix this ? The both error are on the same scene (while add SQL Mobile Subscription).

Thanks.

|||

Hello...

I had the same problem the past few days...and what solved it for me was two things:

1. making sure that the windows user accounts for the replication had read/write control of the replication problems.

2. making sure that those windows user accounts (and my one sql login account that is used for anonymous access) were in the Publication Access List for the publication.

|||how do I check if the user account is in publication access list or not? Thx.|||should be somewhere on the publication properties page. Search books online for "merge publication access list" for more information.|||

I found the list and verified the the two things you mentioned. Yet I still have the exact same error message as you did. I am trying to snyc sql server 2005 standard to SQL mobile. Our IIS is on a seperate box. Did you use IIS on a seperate box too? Much obliged to your info.

|||We are also synchronizing between sql server 2005 standard and sql server Mobile. However, we are running IIS and SQL Server on the same box.|||We are experiencing the same symptoms. All was going fine until yesterday morning. Nobody has changed anything and the issue is not happening for all of the users. This makes me suspcious of the theory that permissions are at fault.

Can anyone who had this problem and resolved it recount what processes they went through?

Thanks|||Additionally you have to make sure that the user connecting to the IIS site has permissions to launch and execute the replisapi.dll. This can be done using the Configure Web Sync wizard.|||Also check if the snapshot is still valid and the files are not cleaned up. If they arent, then rerun the snapshot agent.|||Re-runnning the snapshot is what we do to get it going again - but this does not explain why there is different behaviour for individual users.

Each user has an individual snapshot - should they be updated? The normal snapshot gets run every night so shouldn't be out of date.

What we have established is that this only occurs for some users when the application has been re-installed. (Again, not for all users).|||

When a normal snapshot runs, it invalidates all the dynamic snapshots. Also if the snapshot is expired due to retention or other admin actions then the snapshot needs to be run to make the syncs succeed.

What do you mean by application has been re-installed? On what server, and what does it mean to the subscriber?

A call to SQL Server Reconciler failed. SQL Server 2005, SQL Server Mobile merge replication

Hi,

Iam trying to perform merge replication between SQL Server 2005 and SQL server mobile. It has previously been working. Recently something is causing the following problem when i try to perform the merge. I grabed the following output from the replication monitor.
Error messages:
An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQLServer, Error number: 2147767868)
Get help: http://help/2147767868

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. (Source: MSSQLServer, Error number: 2147766295)
Get help: http://help/2147766295

From Sql Server managment studio i:
--> right clicked on the publication
--> selected view snapshot agent status
--> i then pressed start
the result was [100%] A snapshot of 8 article(s) was generated.

I then retried to sync it and it had the same problem. I upped then logging to level 3. The log produced the following:

2005/10/02 20:56:18 Hr=00000000 Compression Level set to 1
2005/10/02 20:56:18 Hr=00000000 Count of active RSCBs = 0
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Compressed bytes in = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Uncompressed bytes in = 309
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Responding to OpenWrite, total bytes = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 C:\Program Files\Microsoft SQL Server 2005 Mobile Edition\server\30.4E1B0DC71663_8B01FD62-37A2-8AD5-F4E5-B5FF8162902B 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=00000000 Synchronize prepped 0
<PARAMS RSCB="15" HostName="" Publisher="i-removed-this-for-the-post" PublisherNetwork="" PublisherAddress="" PublisherSecurityMode="1" PublisherLogin="" PublisherDatabase="CARSRBO_DB" Publication="CARSRBO_DB" ProfileName="DEFAULT" SubscriberServer="CARSRBO_DB - 4e1b0dc71663" SubscriberDatabasePath="Program Files\carsmr.ui\CARSMR_DB.sdf" Distributor="i-removed-this-for-the-post" DistributorNetwork="" DistributorAddress="" DistributorSecurityMode="1" DistributorLogin="" ExchangeType="3" ValidationType="0" QueryTimeout="300" LoginTimeout="15" SnapshotTransferType="0" DistributorSessionId="72"/>
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=8004563C An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. -2147199428
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=80045017 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. -2147201001
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=80004005 SyncCheck responding 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=00000000 Removing this RSCB 0

Note i noticed that the "MSMerge_rowtrack" does not exist in the snapshot folder only variations in the format MSMerge_rowtrack*.bcp such as MSMerge_rowtrack90.bcp

Any advice on this issue would be appreciated as i have not found anything solid through google.

Thanks in advance,
pdns

If looks like you have not configured the read permissions on the snapshot folder.
The error code 80045017 seems to indicate a permission problem.
Can you try the sync after you give read permissions to the snapshot folder/subfolder and all files.
And note that if you using absolute paths (instead of share) you will need to give NTFS permissions too.

80045017 The SQL Server CE Replication Provider must have read permissions to the snapshot folder. Read permission is needed so the SQL Server CE Replication Provider can download the initial subscription to the Windows CE-based device.

The identity under which the SQL Server CE Replication Provider runs depends upon how IIS authentication is configured.

|||Hi Mahesh,

I think you were right in it being a security problem.

i followed the tutorial at http://msdn2.microsoft.com/en-us/library/ms240364
and the issue is now resolved.

I am not sure of exactly where the permission problem was.

Could it have been that for the SQL Server 2005 security properties that the settings for Security -> Logins -> Computername/IUSR_*
did not have MSmerge_* database roles assigned for the database ?|||Glad that the issue is resolved.
I think the user ISUR* did not read permissions on the snapshot folder.|||

I have following error in propagate while subscription, the error like this.

Error messages:

The schema script 'C:\Program Files\Microsoft SQL Server\MSSQL.5\MSSQL\ReplData\unc\TOSHIBA$SQLSERVER2005ENT_TESTMOBILE_TESTSQLMOBILE\20060303170979\tblTest_2.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147024891)
Get help: http://help/MSSQL_REPL-2147024891

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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001

I try to synchronization from SQL Server 2005 Enterprise to SQL Mobile 2005. While add new subscription on SQL Mobile 2005 it raised error like this on synchronizing data :

- Synchronizing Data (100%) (Error)

Messages

Initializing SQL Server Reconciler has failed.
HRESULT 0x80045901 (29045)

The remote server "TOSHIBA\SQLSERVER2005ENT" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
HRESULT 0x00003700 (0)

{call sp_helpdistpublisher (N'TOSHIBA\SQLSERVER2005ENT') }
HRESULT 0x00000000 (0)

You do not have the required permissions to complete the operation.
HRESULT 0x0000372E (0)

The operation could not be completed.

Any way to fix this ? The both error are on the same scene (while add SQL Mobile Subscription).

Thanks.

|||

Hello...

I had the same problem the past few days...and what solved it for me was two things:

1. making sure that the windows user accounts for the replication had read/write control of the replication problems.

2. making sure that those windows user accounts (and my one sql login account that is used for anonymous access) were in the Publication Access List for the publication.

|||how do I check if the user account is in publication access list or not? Thx.|||should be somewhere on the publication properties page. Search books online for "merge publication access list" for more information.|||

I found the list and verified the the two things you mentioned. Yet I still have the exact same error message as you did. I am trying to snyc sql server 2005 standard to SQL mobile. Our IIS is on a seperate box. Did you use IIS on a seperate box too? Much obliged to your info.

|||We are also synchronizing between sql server 2005 standard and sql server Mobile. However, we are running IIS and SQL Server on the same box.|||We are experiencing the same symptoms. All was going fine until yesterday morning. Nobody has changed anything and the issue is not happening for all of the users. This makes me suspcious of the theory that permissions are at fault.

Can anyone who had this problem and resolved it recount what processes they went through?

Thanks|||Additionally you have to make sure that the user connecting to the IIS site has permissions to launch and execute the replisapi.dll. This can be done using the Configure Web Sync wizard.|||Also check if the snapshot is still valid and the files are not cleaned up. If they arent, then rerun the snapshot agent.|||Re-runnning the snapshot is what we do to get it going again - but this does not explain why there is different behaviour for individual users.

Each user has an individual snapshot - should they be updated? The normal snapshot gets run every night so shouldn't be out of date.

What we have established is that this only occurs for some users when the application has been re-installed. (Again, not for all users).|||

When a normal snapshot runs, it invalidates all the dynamic snapshots. Also if the snapshot is expired due to retention or other admin actions then the snapshot needs to be run to make the syncs succeed.

What do you mean by application has been re-installed? On what server, and what does it mean to the subscriber?

A call to SQL Server Reconciler failed. SQL Server 2005, SQL Server Mobile merge replication

Hi,

Iam trying to perform merge replication between SQL Server 2005 and SQL server mobile. It has previously been working. Recently something is causing the following problem when i try to perform the merge. I grabed the following output from the replication monitor.
Error messages:
An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQLServer, Error number: 2147767868)
Get help: http://help/2147767868

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. (Source: MSSQLServer, Error number: 2147766295)
Get help: http://help/2147766295

From Sql Server managment studio i:
--> right clicked on the publication
--> selected view snapshot agent status
--> i then pressed start
the result was [100%] A snapshot of 8 article(s) was generated.

I then retried to sync it and it had the same problem. I upped then logging to level 3. The log produced the following:

2005/10/02 20:56:18 Hr=00000000 Compression Level set to 1
2005/10/02 20:56:18 Hr=00000000 Count of active RSCBs = 0
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Compressed bytes in = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Uncompressed bytes in = 309
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Responding to OpenWrite, total bytes = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 C:\Program Files\Microsoft SQL Server 2005 Mobile Edition\server\30.4E1B0DC71663_8B01FD62-37A2-8AD5-F4E5-B5FF8162902B 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=00000000 Synchronize prepped 0
<PARAMS RSCB="15" HostName="" Publisher="i-removed-this-for-the-post" PublisherNetwork="" PublisherAddress="" PublisherSecurityMode="1" PublisherLogin="" PublisherDatabase="CARSRBO_DB" Publication="CARSRBO_DB" ProfileName="DEFAULT" SubscriberServer="CARSRBO_DB - 4e1b0dc71663" SubscriberDatabasePath="Program Files\carsmr.ui\CARSMR_DB.sdf" Distributor="i-removed-this-for-the-post" DistributorNetwork="" DistributorAddress="" DistributorSecurityMode="1" DistributorLogin="" ExchangeType="3" ValidationType="0" QueryTimeout="300" LoginTimeout="15" SnapshotTransferType="0" DistributorSessionId="72"/>
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=8004563C An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. -2147199428
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=80045017 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. -2147201001
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=80004005 SyncCheck responding 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=00000000 Removing this RSCB 0

Note i noticed that the "MSMerge_rowtrack" does not exist in the snapshot folder only variations in the format MSMerge_rowtrack*.bcp such as MSMerge_rowtrack90.bcp

Any advice on this issue would be appreciated as i have not found anything solid through google.

Thanks in advance,
pdns

If looks like you have not configured the read permissions on the snapshot folder.
The error code 80045017 seems to indicate a permission problem.
Can you try the sync after you give read permissions to the snapshot folder/subfolder and all files.
And note that if you using absolute paths (instead of share) you will need to give NTFS permissions too.

80045017 The SQL Server CE Replication Provider must have read permissions to the snapshot folder. Read permission is needed so the SQL Server CE Replication Provider can download the initial subscription to the Windows CE-based device.

The identity under which the SQL Server CE Replication Provider runs depends upon how IIS authentication is configured.

|||Hi Mahesh,

I think you were right in it being a security problem.

i followed the tutorial at http://msdn2.microsoft.com/en-us/library/ms240364
and the issue is now resolved.

I am not sure of exactly where the permission problem was.

Could it have been that for the SQL Server 2005 security properties that the settings for Security -> Logins -> Computername/IUSR_*
did not have MSmerge_* database roles assigned for the database ?|||Glad that the issue is resolved.
I think the user ISUR* did not read permissions on the snapshot folder.|||

I have following error in propagate while subscription, the error like this.

Error messages:

The schema script 'C:\Program Files\Microsoft SQL Server\MSSQL.5\MSSQL\ReplData\unc\TOSHIBA$SQLSERVER2005ENT_TESTMOBILE_TESTSQLMOBILE\20060303170979\tblTest_2.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147024891)
Get help: http://help/MSSQL_REPL-2147024891

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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001

I try to synchronization from SQL Server 2005 Enterprise to SQL Mobile 2005. While add new subscription on SQL Mobile 2005 it raised error like this on synchronizing data :

- Synchronizing Data (100%) (Error)

Messages

Initializing SQL Server Reconciler has failed.
HRESULT 0x80045901 (29045)

The remote server "TOSHIBA\SQLSERVER2005ENT" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
HRESULT 0x00003700 (0)

{call sp_helpdistpublisher (N'TOSHIBA\SQLSERVER2005ENT') }
HRESULT 0x00000000 (0)

You do not have the required permissions to complete the operation.
HRESULT 0x0000372E (0)

The operation could not be completed.

Any way to fix this ? The both error are on the same scene (while add SQL Mobile Subscription).

Thanks.

|||

Hello...

I had the same problem the past few days...and what solved it for me was two things:

1. making sure that the windows user accounts for the replication had read/write control of the replication problems.

2. making sure that those windows user accounts (and my one sql login account that is used for anonymous access) were in the Publication Access List for the publication.

|||how do I check if the user account is in publication access list or not? Thx.|||should be somewhere on the publication properties page. Search books online for "merge publication access list" for more information.|||

I found the list and verified the the two things you mentioned. Yet I still have the exact same error message as you did. I am trying to snyc sql server 2005 standard to SQL mobile. Our IIS is on a seperate box. Did you use IIS on a seperate box too? Much obliged to your info.

|||We are also synchronizing between sql server 2005 standard and sql server Mobile. However, we are running IIS and SQL Server on the same box.|||We are experiencing the same symptoms. All was going fine until yesterday morning. Nobody has changed anything and the issue is not happening for all of the users. This makes me suspcious of the theory that permissions are at fault.

Can anyone who had this problem and resolved it recount what processes they went through?

Thanks|||Additionally you have to make sure that the user connecting to the IIS site has permissions to launch and execute the replisapi.dll. This can be done using the Configure Web Sync wizard.|||Also check if the snapshot is still valid and the files are not cleaned up. If they arent, then rerun the snapshot agent.|||Re-runnning the snapshot is what we do to get it going again - but this does not explain why there is different behaviour for individual users.

Each user has an individual snapshot - should they be updated? The normal snapshot gets run every night so shouldn't be out of date.

What we have established is that this only occurs for some users when the application has been re-installed. (Again, not for all users).|||

When a normal snapshot runs, it invalidates all the dynamic snapshots. Also if the snapshot is expired due to retention or other admin actions then the snapshot needs to be run to make the syncs succeed.

What do you mean by application has been re-installed? On what server, and what does it mean to the subscriber?

sql

A call to SQL Server Reconciler failed. SQL Server 2005, SQL Server Mobile merge replication

Hi,

Iam trying to perform merge replication between SQL Server 2005 and SQL server mobile. It has previously been working. Recently something is causing the following problem when i try to perform the merge. I grabed the following output from the replication monitor.
Error messages:
An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQLServer, Error number: 2147767868)
Get help: http://help/2147767868

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. (Source: MSSQLServer, Error number: 2147766295)
Get help: http://help/2147766295

From Sql Server managment studio i:
--> right clicked on the publication
--> selected view snapshot agent status
--> i then pressed start
the result was [100%] A snapshot of 8 article(s) was generated.

I then retried to sync it and it had the same problem. I upped then logging to level 3. The log produced the following:

2005/10/02 20:56:18 Hr=00000000 Compression Level set to 1
2005/10/02 20:56:18 Hr=00000000 Count of active RSCBs = 0
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Compressed bytes in = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Total Uncompressed bytes in = 309
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 Responding to OpenWrite, total bytes = 175
2005/10/02 20:56:18 Thread=C38 RSCB=15 Command=OPWC Hr=00000000 C:\Program Files\Microsoft SQL Server 2005 Mobile Edition\server\30.4E1B0DC71663_8B01FD62-37A2-8AD5-F4E5-B5FF8162902B 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=00000000 Synchronize prepped 0
<PARAMS RSCB="15" HostName="" Publisher="i-removed-this-for-the-post" PublisherNetwork="" PublisherAddress="" PublisherSecurityMode="1" PublisherLogin="" PublisherDatabase="CARSRBO_DB" Publication="CARSRBO_DB" ProfileName="DEFAULT" SubscriberServer="CARSRBO_DB - 4e1b0dc71663" SubscriberDatabasePath="Program Files\carsmr.ui\CARSMR_DB.sdf" Distributor="i-removed-this-for-the-post" DistributorNetwork="" DistributorAddress="" DistributorSecurityMode="1" DistributorLogin="" ExchangeType="3" ValidationType="0" QueryTimeout="300" LoginTimeout="15" SnapshotTransferType="0" DistributorSessionId="72"/>
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=8004563C An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. -2147199428
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SYNC Hr=80045017 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. -2147201001
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=80004005 SyncCheck responding 0
2005/10/02 20:56:19 Thread=E64 RSCB=15 Command=SCHK Hr=00000000 Removing this RSCB 0

Note i noticed that the "MSMerge_rowtrack" does not exist in the snapshot folder only variations in the format MSMerge_rowtrack*.bcp such as MSMerge_rowtrack90.bcp

Any advice on this issue would be appreciated as i have not found anything solid through google.

Thanks in advance,
pdns

If looks like you have not configured the read permissions on the snapshot folder.
The error code 80045017 seems to indicate a permission problem.
Can you try the sync after you give read permissions to the snapshot folder/subfolder and all files.
And note that if you using absolute paths (instead of share) you will need to give NTFS permissions too.

80045017The SQL Server CE Replication Provider must have read permissions to the snapshot folder. Read permission is needed so the SQL Server CE Replication Provider can download the initial subscription to the Windows CE-based device.

The identity under which the SQL Server CE Replication Provider runs depends upon how IIS authentication is configured.

|||Hi Mahesh,

I think you were right in it being a security problem.

i followed the tutorial at http://msdn2.microsoft.com/en-us/library/ms240364
and the issue is now resolved.

I am not sure of exactly where the permission problem was.

Could it have been that for the SQL Server 2005 security properties that the settings for Security -> Logins -> Computername/IUSR_*
did not have MSmerge_* database roles assigned for the database ?|||Glad that the issue is resolved.
I think the user ISUR* did not read permissions on the snapshot folder.|||

I have following error in propagate while subscription, the error like this.

Error messages:

The schema script 'C:\Program Files\Microsoft SQL Server\MSSQL.5\MSSQL\ReplData\unc\TOSHIBA$SQLSERVER2005ENT_TESTMOBILE_TESTSQLMOBILE\20060303170979\tblTest_2.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147024891)
Get help: http://help/MSSQL_REPL-2147024891

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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001

I try to synchronization from SQL Server 2005 Enterprise to SQL Mobile 2005. While add new subscription on SQL Mobile 2005 it raised error like this on synchronizing data :

- Synchronizing Data (100%) (Error)

Messages

Initializing SQL Server Reconciler has failed.
HRESULT 0x80045901 (29045)

The remote server "TOSHIBA\SQLSERVER2005ENT" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
HRESULT 0x00003700 (0)

{call sp_helpdistpublisher (N'TOSHIBA\SQLSERVER2005ENT') }
HRESULT 0x00000000 (0)

You do not have the required permissions to complete the operation.
HRESULT 0x0000372E (0)

The operation could not be completed.

Any way to fix this ? The both error are on the same scene (while add SQL Mobile Subscription).

Thanks.

|||

Hello...

I had the same problem the past few days...and what solved it for me was two things:

1. making sure that the windows user accounts for the replication had read/write control of the replication problems.

2. making sure that those windows user accounts (and my one sql login account that is used for anonymous access) were in the Publication Access List for the publication.

|||how do I check if the user account is in publication access list or not? Thx.|||should be somewhere on the publication properties page. Search books online for "merge publication access list" for more information.|||

I found the list and verified the the two things you mentioned. Yet I still have the exact same error message as you did. I am trying to snyc sql server 2005 standard to SQL mobile. Our IIS is on a seperate box. Did you use IIS on a seperate box too? Much obliged to your info.

|||We are also synchronizing between sql server 2005 standard and sql server Mobile. However, we are running IIS and SQL Server on the same box.|||We are experiencing the same symptoms. All was going fine until yesterday morning. Nobody has changed anything and the issue is not happening for all of the users. This makes me suspcious of the theory that permissions are at fault.

Can anyone who had this problem and resolved it recount what processes they went through?

Thanks|||Additionally you have to make sure that the user connecting to the IIS site has permissions to launch and execute the replisapi.dll. This can be done using the Configure Web Sync wizard.|||Also check if the snapshot is still valid and the files are not cleaned up. If they arent, then rerun the snapshot agent.|||Re-runnning the snapshot is what we do to get it going again - but this does not explain why there is different behaviour for individual users.

Each user has an individual snapshot - should they be updated? The normal snapshot gets run every night so shouldn't be out of date.

What we have established is that this only occurs for some users when the application has been re-installed. (Again, not for all users).|||

When a normal snapshot runs, it invalidates all the dynamic snapshots. Also if the snapshot is expired due to retention or other admin actions then the snapshot needs to be run to make the syncs succeed.

What do you mean by application has been re-installed? On what server, and what does it mean to the subscriber?