Merge Replication Throwing Very Weird Error Messages

Mar 2, 2007

I've been setting up subscriptions to a merge publication for the past 3 days. All of a sudden, I'm getting a pile of very strange errors. Replication is configured. I have 16 subscribers to an existing publication configured and synchronizing changes without any issues. The script that I'm using to create all of the subscriptions is as follows:

use [PIC]

exec sp_addmergesubscription @publication = N'PIC', @subscriber = N'machinenameSQLEXPRESS',

@subscriber_db = N'MyDatabase', @subscription_type = N'Push', @sync_type = N'Automatic',

@subscriber_type = N'Global', @subscription_priority = 75, @description = N'', @use_interactive_resolver = N'False'

exec sp_addmergepushsubscription_agent @publication = N'PIC', @subscriber = N'machinenameSQLEXPRESS',

@subscriber_db = N'MyDatabase', @job_login = null, @job_password = null, @subscriber_security_mode = 1,

@publisher_security_mode = 1, @frequency_type = 64, @frequency_interval = 0, @frequency_relative_interval = 0,

@frequency_recurrence_factor = 0, @frequency_subday = 0, @frequency_subday_interval = 0, @active_start_time_of_day = 0,

@active_end_time_of_day = 235959, @active_start_date = 0, @active_end_date = 0

GO

The last one that I added #17, gives the following errors after successfully creating the subscription.

Command attempted:


{call sys.sp_MSmergesubscribedb ('true', 0) }

Error messages:


The merge process could not initialize the subscription. Ensure that the subscription registration exists at the publisher, and reregister the subscription if necessary. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201011)
Get help: http://help/MSSQL_REPL-2147201011

RegCreateKeyEx() returned error 5, 'Access is denied.' (Source: MSSQLServer, Error number: 22002)
Get help: http://help/22002

Could not add article resolver 'Microsoft SQL Server Additive Conflict Resolver' information to the registry (Source: MSSQLServer, Error number: 21713)
Get help: http://help/21713

Could not register article resolver: 'Microsoft SQL Server Additive Conflict Resolver'. (Source: MSSQLServer, Error number: 21715)
Get help: http://help/21715

The system tables for merge replication could not be created successfully. (Source: MSSQLServer, Error number: 20008)
Get help: http://help/20008

I've tried to manually create it using the GUI and get an even stranger error message as follows:

TITLE: New Subscription Wizard
------------------------------

Microsoft SQL Server Management Studio is unable to access replication components because replication is not installed on this instance of SQL Server. For information about installing replication, see the topic Installing Replication in SQL Server Books Online.

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=Microsoft.SqlServer.Management.UI.ReplUtilitiesErrorSR&EvtID=ReplicationNotInstalled&LinkId=20476

------------------------------
ADDITIONAL INFORMATION:

Replication components are not installed on this server. Run SQL Server Setup again and select the option to install replication. (Microsoft SQL Server, Error: 21028)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=21028&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------


I very obviously have replication installed by virtue of the fact that I have a publication and 16 subscriptions that are currently synchronizing. Any ideas?

View 3 Replies


ADVERTISEMENT

Weird Messages In Error Log

Mar 28, 2008

Hi,
I am getting these messages in error log. What do I needd to do?

2008-03-27 09:34:54.76 spid74 Using 'dbghelp.dll' version '4.0.5'
2008-03-27 09:34:54.76 spid74 ***Stack Dump being sent to C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGSQLDump0014.txt
2008-03-27 09:34:54.76 spid74 SqlDumpExceptionHandler: Process 74 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2008-03-27 09:34:54.76 spid74 * *******************************************************************************
2008-03-27 09:34:54.76 spid74 *
2008-03-27 09:34:54.76 spid74 * BEGIN STACK DUMP:
2008-03-27 09:34:54.76 spid74 * 03/27/08 09:34:54 spid 74
2008-03-27 09:34:54.76 spid74 *
2008-03-27 09:34:54.76 spid74 *
2008-03-27 09:34:54.76 spid74 * Exception Address = 7C80EEF0 Module(ntdll+0000EEF0)
2008-03-27 09:34:54.76 spid74 * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
2008-03-27 09:34:54.76 spid74 * Access Violation occurred reading address 00000001
2008-03-27 09:34:54.76 spid74 * Input Buffer 87 bytes -
2008-03-27 09:34:54.76 spid74 * C a m s _ V a l 15 00 43 00 61 00 6d 00 73 00 5f 00 56 00 61 00 6c 00
2008-03-27 09:34:54.76 spid74 * i d a t e P a s s 69 00 64 00 61 00 74 00 65 00 50 00 61 00 73 00 73 00
2008-03-27 09:34:54.76 spid74 * w o r d § 77 00 6f 00 72 00 64 00 00 00 00 00 a7 0f 00 09 04 00
2008-03-27 09:34:54.76 spid74 * 2 JFINCH § 01 32 06 00 4a 46 49 4e 43 48 00 00 a7 20 00 09 04 00
2008-03-27 09:34:54.76 spid74 * 2 JFINCH & 01 32 06 00 4a 46 49 4e 43 48 00 01 26 04 00
2008-03-27 09:34:54.76 spid74 *
2008-03-27 09:34:54.76 spid74 *
2008-03-27 09:34:54.76 spid74 * MODULE BASE END SIZE
2008-03-27 09:34:54.76 spid74 * sqlservr 01000000 02C09FFF 01c0a000
2008-03-27 09:34:54.76 spid74 * ntdll 7C800000 7C8BFFFF 000c0000
2008-03-27 09:34:54.76 spid74 * kernel32 77E40000 77F41FFF 00102000
2008-03-27 09:34:54.76 spid74 * MSVCR80 78130000 781CAFFF 0009b000
2008-03-27 09:34:54.76 spid74 * msvcrt 77BA0000 77BF9FFF 0005a000
2008-03-27 09:34:54.76 spid74 * MSVCP80 7C420000 7C4A6FFF 00087000
2008-03-27 09:34:54.76 spid74 * ADVAPI32 77F50000 77FEAFFF 0009b000
2008-03-27 09:34:54.76 spid74 * RPCRT4 77C50000 77CEEFFF 0009f000
2008-03-27 09:34:54.76 spid74 * Secur32 76F50000 76F62FFF 00013000
2008-03-27 09:34:54.76 spid74 * USER32 77380000 77410FFF 00091000
2008-03-27 09:34:54.76 spid74 * GDI32 77C00000 77C47FFF 00048000
2008-03-27 09:34:54.76 spid74 * CRYPT32 761B0000 76242FFF 00093000
2008-03-27 09:34:54.76 spid74 * MSASN1 76190000 761A1FFF 00012000
2008-03-27 09:34:54.76 spid74 * MSWSOCK 71B20000 71B60FFF 00041000
2008-03-27 09:34:54.76 spid74 * WS2_32 71C00000 71C16FFF 00017000
2008-03-27 09:34:54.76 spid74 * WS2HELP 71BF0000 71BF7FFF 00008000
2008-03-27 09:34:54.76 spid74 * USERENV 76920000 769E1FFF 000c2000
2008-03-27 09:34:54.76 spid74 * opends60 333E0000 333E6FFF 00007000
2008-03-27 09:34:54.76 spid74 * NETAPI32 71C40000 71C96FFF 00057000
2008-03-27 09:34:54.76 spid74 * SHELL32 7C8D0000 7D0CEFFF 007ff000
2008-03-27 09:34:54.76 spid74 * SHLWAPI 77DA0000 77DF1FFF 00052000
2008-03-27 09:34:54.76 spid74 * comctl32 77420000 77522FFF 00103000
2008-03-27 09:34:54.76 spid74 * psapi 76B70000 76B7AFFF 0000b000
2008-03-27 09:34:54.76 spid74 * instapi 48060000 48069FFF 0000a000
2008-03-27 09:34:54.76 spid74 * sqlevn70 4F610000 4F7B8FFF 001a9000
2008-03-27 09:34:54.76 spid74 * SQLOS 344D0000 344D4FFF 00005000
2008-03-27 09:34:54.76 spid74 * rsaenh 68000000 68034FFF 00035000
2008-03-27 09:34:54.76 spid74 * AUTHZ 76C40000 76C53FFF 00014000
2008-03-27 09:34:54.76 spid74 * MSCOREE 79000000 79045FFF 00046000
2008-03-27 09:34:54.76 spid74 * ole32 77670000 777A8FFF 00139000
2008-03-27 09:34:54.76 spid74 * msv1_0 76C90000 76CB6FFF 00027000
2008-03-27 09:34:54.76 spid74 * iphlpapi 76CF0000 76D09FFF 0001a000
2008-03-27 09:34:54.76 spid74 * kerberos 629A0000 629F7FFF 00058000
2008-03-27 09:34:54.76 spid74 * cryptdll 766E0000 766EBFFF 0000c000
2008-03-27 09:34:54.76 spid74 * schannel 76750000 76776FFF 00027000
2008-03-27 09:34:54.76 spid74 * COMRES 77010000 770D5FFF 000c6000
2008-03-27 09:34:54.76 spid74 * XOLEHLP 62A60000 62A65FFF 00006000
2008-03-27 09:34:54.76 spid74 * MSDTCPRX 62A70000 62AE8FFF 00079000
2008-03-27 09:34:54.76 spid74 * OLEAUT32 77D00000 77D8AFFF 0008b000
2008-03-27 09:34:54.76 spid74 * msvcp60 62AF0000 62B54FFF 00065000
2008-03-27 09:34:54.76 spid74 * MTXCLU 62B60000 62B78FFF 00019000
2008-03-27 09:34:54.76 spid74 * VERSION 77B90000 77B97FFF 00008000
2008-03-27 09:34:54.76 spid74 * WSOCK32 71BB0000 71BB8FFF 00009000
2008-03-27 09:34:54.76 spid74 * CLUSAPI 62B80000 62B91FFF 00012000
2008-03-27 09:34:54.76 spid74 * RESUTILS 62BA0000 62BB2FFF 00013000
2008-03-27 09:34:54.76 spid74 * DNSAPI 76ED0000 76EF9FFF 0002a000
2008-03-27 09:34:54.76 spid74 * winrnr 76F70000 76F76FFF 00007000
2008-03-27 09:34:54.76 spid74 * WLDAP32 76F10000 76F3DFFF 0002e000
2008-03-27 09:34:54.76 spid74 * rasadhlp 76F80000 76F84FFF 00005000
2008-03-27 09:34:54.76 spid74 * security 62FF0000 62FF3FFF 00004000
2008-03-27 09:34:54.76 spid74 * msfte 637D0000 63A28FFF 00259000
2008-03-27 09:34:54.76 spid74 * dbghelp 63A40000 63B54FFF 00115000
2008-03-27 09:34:54.76 spid74 * WINTRUST 76BB0000 76BDAFFF 0002b000
2008-03-27 09:34:54.76 spid74 * imagehlp 76C10000 76C37FFF 00028000
2008-03-27 09:34:54.76 spid74 * dssenh 68100000 68126FFF 00027000
2008-03-27 09:34:54.76 spid74 * hnetcfg 63DA0000 63DF9FFF 0005a000
2008-03-27 09:34:54.76 spid74 * wshtcpip 71AE0000 71AE7FFF 00008000
2008-03-27 09:34:54.76 spid74 * NTMARTA 77E00000 77E20FFF 00021000
2008-03-27 09:34:54.76 spid74 * SAMLIB 7E020000 7E02EFFF 0000f000
2008-03-27 09:34:54.76 spid74 * ntdsapi 766F0000 76703FFF 00014000
2008-03-27 09:34:54.76 spid74 * xpsp2res 63F40000 64204FFF 002c5000
2008-03-27 09:34:54.76 spid74 * CLBCatQ 777B0000 77832FFF 00083000
2008-03-27 09:34:54.76 spid74 * sqlncli 64210000 64433FFF 00224000
2008-03-27 09:34:54.76 spid74 * COMCTL32 77530000 775C6FFF 00097000
2008-03-27 09:34:54.76 spid74 * comdlg32 762B0000 762F8FFF 00049000
2008-03-27 09:34:54.76 spid74 * SQLNCLIR 007C0000 007F2FFF 00033000
2008-03-27 09:34:54.76 spid74 * msftepxy 64670000 64684FFF 00015000
2008-03-27 09:34:54.76 spid74 * xp_ctnhashproc 62910000 6292EFFF 0001f000
2008-03-27 09:34:54.76 spid74 * xplog70 63360000 6336BFFF 0000c000
2008-03-27 09:34:54.76 spid74 * xplog70 63380000 63382FFF 00003000
2008-03-27 09:34:54.76 spid74 * sqlvdi 645D0000 645F1FFF 00022000
2008-03-27 09:34:54.76 spid74 * xpstar90 630B0000 630F8FFF 00049000
2008-03-27 09:34:54.76 spid74 * SQLSCM90 633C0000 633C8FFF 00009000
2008-03-27 09:34:54.76 spid74 * ODBC32 64450000 6448CFFF 0003d000
2008-03-27 09:34:54.76 spid74 * BatchParser90 64490000 644AEFFF 0001f000
2008-03-27 09:34:54.76 spid74 * ATL80 7C630000 7C64AFFF 0001b000
2008-03-27 09:34:54.76 spid74 * odbcint 64DC0000 64DD6FFF 00017000
2008-03-27 09:34:54.76 spid74 * xpstar90 65330000 65355FFF 00026000
2008-03-27 09:34:54.76 spid74 * xpsqlbot 64DE0000 64DE5FFF 00006000
2008-03-27 09:34:54.76 spid74 * msxmlsql 78800000 788D4FFF 000d5000
2008-03-27 09:34:54.76 spid74 * msxml2 66030000 660DEFFF 000af000
2008-03-27 09:34:54.76 spid74 * msxml3 67040000 67156FFF 00117000
2008-03-27 09:34:54.76 spid74 * dbghelp 68930000 68A44FFF 00115000
2008-03-27 09:34:54.76 spid74 *
2008-03-27 09:34:54.76 spid74 * Edi: 62930000: 000000C8 00000187 EEFFEEFF 00001002 00000000 0000FE00
2008-03-27 09:34:54.76 spid74 * Esi: 1C3C2EE8: 010A50E8 00000001 1C3C2490 0000D333 1C3C2F10 1C3C2F08
2008-03-27 09:34:54.76 spid74 * Eax: 010A50E8: 010B7A71 01659AC6 01659ACE 018484D0 018484D8 01659ADE
2008-03-27 09:34:54.76 spid74 * Ebx: 00000000:
2008-03-27 09:34:54.76 spid74 * Ecx: 00000001:
2008-03-27 09:34:54.76 spid74 * Edx: 62930608: 00127668 FFFFFFFE 00000001 00000430 00000000 00000FA0
2008-03-27 09:34:54.76 spid74 * Eip: 7C80EEF0: 503B118B 56850F04 3B00031E 4E850FD6 8900031E 04488901
2008-03-27 09:34:54.76 spid74 * Ebp: 656DCD84: 00000020 6291ED76 62930000 00000000 1C3C2F08 3910C3B0
2008-03-27 09:34:54.76 spid74 * SegCs: 0000001B:
2008-03-27 09:34:54.76 spid74 * EFlags: 00010207: 47004900 5F005700 4F004C00 3D004300 3A004300 50005C00
2008-03-27 09:34:54.76 spid74 * Esp: 656DCCB4: 1C3C2F08 1C3C2F08 654E05E0 0100469B 656DCD74 78132C78
2008-03-27 09:34:54.76 spid74 * SegSs: 00000023:
2008-03-27 09:34:54.76 spid74 * *******************************************************************************
2008-03-27 09:34:54.76 spid74 * -------------------------------------------------------------------------------
2008-03-27 09:34:54.76 spid74 * Short Stack Dump
2008-03-27 09:34:54.77 spid74 7C80EEF0 Module(ntdll+0000EEF0)
2008-03-27 09:34:54.77 spid74 6291ED76 Module(xp_ctnhashproc+0000ED76)
2008-03-27 09:34:54.77 spid74 62911184 Module(xp_ctnhashproc+00001184)
2008-03-27 09:34:54.77 spid74 01660FEC Module(sqlservr+00660FEC)
2008-03-27 09:34:54.77 spid74 01662FCD Module(sqlservr+00662FCD)
2008-03-27 09:34:54.77 spid74 01662984 Module(sqlservr+00662984)
2008-03-27 09:34:54.77 spid74 01661920 Module(sqlservr+00661920)
2008-03-27 09:34:54.77 spid74 01661E2E Module(sqlservr+00661E2E)
2008-03-27 09:34:54.77 spid74 01C1BF0C Module(sqlservr+00C1BF0C)
2008-03-27 09:34:54.77 spid74 014B3FE1 Module(sqlservr+004B3FE1)
2008-03-27 09:34:54.77 spid74 012389B6 Module(sqlservr+002389B6)
2008-03-27 09:34:54.77 spid74 0123882D Module(sqlservr+0023882D)
2008-03-27 09:34:54.77 spid74 012386C2 Module(sqlservr+002386C2)
2008-03-27 09:34:54.77 spid74 010227F3 Module(sqlservr+000227F3)
2008-03-27 09:34:54.77 spid74 010293B5 Module(sqlservr+000293B5)
2008-03-27 09:34:54.77 spid74 010286DC Module(sqlservr+000286DC)
2008-03-27 09:34:54.77 spid74 01032A36 Module(sqlservr+00032A36)
2008-03-27 09:34:54.77 spid74 0102F1F4 Module(sqlservr+0002F1F4)
2008-03-27 09:34:54.77 spid74 010077A6 Module(sqlservr+000077A6)
2008-03-27 09:34:54.77 spid74 010078CC Module(sqlservr+000078CC)
2008-03-27 09:34:54.77 spid74 010075DC Module(sqlservr+000075DC)
2008-03-27 09:34:54.77 spid74 010B94A5 Module(sqlservr+000B94A5)
2008-03-27 09:34:54.77 spid74 010B939C Module(sqlservr+000B939C)
2008-03-27 09:34:54.77 spid74 010B9064 Module(sqlservr+000B9064)
2008-03-27 09:34:54.79 spid74 010B9201 Module(sqlservr+000B9201)
2008-03-27 09:34:54.79 spid74 781329BB Module(MSVCR80+000029BB)
2008-03-27 09:34:54.79 spid74 78132A47 Module(MSVCR80+00002A47)
2008-03-27 09:34:54.79 spid74 Stack Signature for the dump is 0xD5652648
2008-03-27 09:34:56.31 spid74 External dump process return code 0x20002001.
The error information has been submitted to Watson error reporting.

2008-03-27 09:34:56.31 spid74 Error: 18002, Severity: 20, State: 1.
2008-03-27 09:34:56.31 spid74 Exception happened when running extended stored procedure 'xp_ctnhash' in the library 'xp_ctnhashproc.dll'. SQL Server is terminating process 74. Exception type: Win32 exception; Exception code: 0xc0000005.

View 5 Replies View Related

Merge Replication - Weird Stuff

May 21, 2007

I'm implementing merge replication between SQL CE and sql server 2005 SP2. Here is the problem I'm facing



I have dynamic filters on some tables like

Select * from table1 inner join table2

ON table1.field1 = table2.field3

and table2.flag = true



When table2 flag turns true then all the matching records in table1 should be returned to the subscriber.



But that is not happening. The filter does not return any records to the subscriber even though i see records when i run the query on the server. My take on this is the publisher thinks there is no changes on table1 so there is nothing to update. So to fix that i run dummy updates like

update table1

set [name] = [name]

where table1.field1 in

(Select field2 from table2 where flag=true)



This updates the records and the publisher updates the subscriber the first time. When i set the flag to false, it is supposed to remove the data from the subscriber but i get this error.




The merge process failed because it detected a mismatch between the replication metadata of the two replicas, such that some changes could be lost leading to non-convergence. This could be due to the subscriber not having synchronized within the retention period, or because of one of the replicas being restored to a backup older than retention period, or because of the publisher performing more aggressive cleanup on articles of type download-only and articles with partition_options = 3. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199363)
Get help: http://help/MSSQL_REPL-2147199363

The common generation watermark is invalid at this replica since it does not exist or metadata for changes not yet propagated may have been cleaned up. (Source: MSSQLServer, Error number: 21800)
Get help: http://help/21800





I have no idea whats going on. Any clues, anyone? Thanks for your help.





Ramesh

View 13 Replies View Related

Merge Replication Weird Scenario?

Dec 15, 2005

 
On the national Server:           SQL 2005 Enterprise
On the mobile clients:             SQL 2005 Workgroup.
 
 
I was asked to find a solution to such scenario
 
2 mobile subscriber S1 and S2 to the same simple merge publication P1 on server N
 
Day 1,

S1 and S2 both synch up with N and both go off to do fieldwork
Day3,


S1 and S2 both synch up with N.

S1 goes back to work

S2  shutdown the laptop and goes on 2-week vacation.
2 Weeks late



S1 Synch up wit the server and goes off to do fieldwork.

S2 meets S1 in the field. Their workfield is in the North Pole.

S2 has the laptop with data 2-weeks old but no longer can have access to the master publisher N to synch the replica and get latest changes.

S2 will have to sync with S1 since S1 database is fresh. The challenge is to have S2 and S1 replica identical
 
The Questions:


Is it possible for S2 to sync with S1? 

if yes, How to go about it€¦ we need S1 and S2 to have identical replica on their machines?



Now that S1 and S2 are have identical databases and are both doing their fieldwork in the northpole. Can they both sync back with the national publisher N when they have access?
Keep in mind that S2 got its data updated from the replica on S1?
 
Thank you!
 
 
 
 

View 3 Replies View Related

Weird Conflicts - Merge Replication 2005 -&&> 2000

Aug 3, 2006

Publisher is 2005 x64, subscribers SS2000 (SP3) and SS2005 x64. Pull agents, no filters on subscriptions. We are seeing many seemingly random conflicts on between SS2000 subscriber and publisher. It happens on several different tables.

One table is never editted, only inserts happening everywhere and deletes happening on the SS2000 subscriber. Deletes will sometimes generate conflict. Reason is '"he row was deleted at 'CTS11.CTS' but could not be deleted at 'cts4a.cts'. Unable to synchronize the row because the row was updated by a different process outside of replication." CTS11 is SS2000 subscriber, CTS4A is publisher.

Probably unrelated bug but when looking at conflicts on this same table in SS2005 conflict viewer, get error "ID is neither a DataColumn nor a DataRelation for table summary (System.dATA)" and then "Column ID does not belong to table summary (System.Data)". ID column is rowguid, only unusual thing about table is that it has varchar(8000) field plus some other fields.


Other tables generate conflicts with this reason "The row was updated at 'CTS11.CTS' but could not be updated at 'cts4a.cts'. The merge process was unable to synchronize the row." I enabled verbose logging in the merge agent but the log file didn't contain any further explanation.

This same topology and schema worked fine when all publishers and subscribers were SS2000.

Any insight into how to fix this would be appreciated.





View 9 Replies View Related

HELP - Weird Error After Replication Setup

Feb 19, 2004

Hello guys,
Have any ever seen this error before?

Steps I made:
1) Created Publications by script - using Manual Sync. (Transacat Repl)
2) Created Subscriptions by script
3) Started Distribution Agent
THEN THIS ERROR MSG:

Violation of PRIMARY KEY constraint 'PK__@snapshot_seqnos__24F8BF73'. Cannot insert duplicate key in object '#24049B3A'.
(Source: SYD242 (Data source); Error number: 2627)
---------------------------------------------------------------------------------------------------------------


****Lost, has any got any ideas?

View 2 Replies View Related

Replication :: Error Details Or Messages Of Select Session Not Shown

Jul 10, 2015

Since I had a bad error in replication, my replication monitor won't show the tab "Error details or messages of the select session". 

I am not able to activate or to show this "tab", to get all information about my error.

I added two screeshots, one with the 3 tab, and the other, were the information about my error are missing. How i can my default view back?

Replication Monitor OK:

My Replication Monitor with missing tab:

I had to know, which ID is causing a primary key violation. Instead of Replication Monitor, I would use t-sql.

View 3 Replies View Related

Merge Replication Error

Aug 25, 2006

Replication-Replication Merge Subsystem: agent TRPSQL3-ThomsonResearch-TR Pub-TRPSQL2-4 failed. 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 log

I am getting the above error in Merge Replication. any one having any idea pls let me know.

Thanks & Regards,

Kasi.



View 1 Replies View Related

Merge Replication Error

Aug 25, 2006

In Merge Replication, I am not able to replicate one table having more than 5 GB data to the subscriber. If I have filter on the table I am able to do. I couldn't understand the problem? Any one having any idea on the same?

For your information.

I have 1.7GB free space in C drive. Is it a space problem in C drive? Actually my data base is storing in E drive. It has 30GB free space. But Sql Server installed in D drive it has 2 GB free space.

Thanks in advance

Kasi.





View 4 Replies View Related

Merge Replication Error

Jun 26, 2006

Hi,

We have an HTTPS merge publication which has been working fine, but all of a sudden the subscription for a subscriber is failing with the following message at the publisher:

Error messages: The process could not read the request message due to OS error
10054. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147014842) Get help:
http://help/MSSQL_REPL-2147014842 The format of a message during Web
synchronization was invalid. Ensure that replication components are properly
configured at the Web server. (Source: MSSQL_REPL, Error number: MSSQL_REPL-
2147199374) Get help: http://help/MSSQL_REPL-2147199374 The subscription to
publication 'yarraman main' could not be verified. Ensure that all Merge Agent
command line parameters are specified correctly and that the subscription is
correctly configured. If the Publisher no longer has information about this
subscription, drop and recreate the subscription. (Source: MSSQL_REPL, Error
number: MSSQL_REPL-2147201019) Get help: http://help/MSSQL_REPL-2147201019

We have 2 subscribers to this publication and it is working fine for the other subscriber..

Help !

thanks
Bruce

View 1 Replies View Related

Error In Merge Replication

Jul 3, 2006

Hi,

I have made two subscription in Merge Replication .

One Subscription is syncing data properly while other on is giving error

'The process could not enumerate changes at the 'Publisher'. error -2147200999

MS SQL Server Service Pack 4 is installed.

Now how can resolve it.

Thanks

Sanjay Tiwari

View 1 Replies View Related

Merge Replication Error - Help Required...

Apr 18, 2006

Dear Friends,
I am very new to replication, For learning purpose I am trying to setup merge replication. The given setup I am using.

1. Windows 2000 Server + SP4 (Publisher for SQL 2000)
2. Windows 2003 Server + SP1 (Subscriber For SQL 2000)

I am getting a replication error, I have taken this errors details from merge agent on publisher server.

Find enclosed replication error details in the microsoft document file format (.doc). The document is consist of three SQL Server snapshot rather three diffrent errors.

In the pictures you can find the red & white color cross (wrong sign) on replication monitor tab, I don't know why it is appearing. :confused:

Kindly, give me guidance to rectify this error & setup the marge replication between two SQL 2000 Servers.

View 2 Replies View Related

SQL 2000 Merge Replication Error

Apr 27, 2006

I have a merge replication publication that has been running for
months. This week the Snapshot started failing, reporting that an
article was not included in the publication. I checked and found
3 articles that mysteriously no longer show up as being in the
publication. When I attempt to add them it reports that it can't
add them because there is already an article by that name in the
publication. Apparently some table has lost its rows for these
articles while another table(s) still has its rows.



Has anyone had this problem? Is there a solution short of
dropping the publication and starting over - a solution that would
literally take weeks for us?



Thanks for any help.

View 4 Replies View Related

Merge Replication - Subscriber Error

Apr 20, 2007

Hi,

I have setup merge replication between SQL Server 2005 and SQL Server Express. The setup uses web synchronization. (And the setup uses dynamic filter HOST_NAME)

On some of the client machines, replication fails with the following error (when initializing the subscription):

from subscriber merge agent verbose log:
A dynamic snapshot will be applied from 'D:DOCUME~1JBAUMG~1.CORLOCALS~1TempDB101-EQA-SCL_BQDB_BQ_PUB_BQDB'

Validating dynamic snapshot
2007-04-1819:39:45.434 OLE DB Subscriber 'FRG-BAUMGARTENJSQLEXPRESS': sys.sp_MSregisterdynsnapseqno @snapshot_session_token=N'\XXX.XX.XX.XXSnapshotuncDB101-EQA-SCL_BQDB_BQ_PUB20070417180079dynsnap', @dynsnapseqno='5599F67E-A1A9-4573-A14F-9851F6FE4B51'

(Note: XXX.XX.XX.XX is a proper IP of DB, I have just masked it in the post)

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.

I enabled verbose logging for the snapshot agent for the subscriber, but there was no error there. It is obvious from the log info above that the error occurs only after downloading the snapshot to the client and during applying it to the subscriber by the merge agent.

After I got this error, I tried running the subscriber program again and it successfully replicated on the third attempt. But this behavior is not consistent and it fails for most of the time on some of the machines

Any info on this error?

View 6 Replies View Related

Merge Replication SQL2000 Error 2812

Feb 10, 2004

Hi !

When trying to start a Merge Replication agent I get the following Error message:

The process could not enumerate the changes at the subscriber. 2812

The snapshot agent works fine as far as I can see.

The replication is set up between a Win2000 / SQL7 / SP 4 and a Win2003 / SQL2000 / SP 3a machine. Sqlserveragent on both machines is run as a system account.

Any tip is welcome!

Thanks
VincentJS

View 6 Replies View Related

URGENT! Merge Replication Error 2812

Feb 12, 2004

Hi colleagues!

In trying to activate a merge replication between a Win2000/SQL7 distributor/publisher and a Win2003/SQL2000 subscriber I keep getting the following error:

Process could not enumerate changes at the subscriber (error 2812)

Merge publication works fine between the distributor and another subscriber (NT4/SQL7).

When i look at the details of the merge agent history i can see the process stopped with :

call sp_MSenumeratechanges(?,?,?,?,?)

I read article 308743 on microsoft/technet, and there they advise to install SP3a for SQL2000 on the subscriber. Ive done that but the error persists.

SQLServerAgent on the subscriber starts up with a local administrator account, the (physical) server itself is not a member of the local network; (outside the DMZ). The server is declared in the Client Network Utility of the distributor/publisher and is therefore known as a potential subscriber. In fact, the snapshot agent works perfectly (or so it seems).

Can anyone give me a helpfull hint?

Thanks!
VincentJS

View 1 Replies View Related

Merge Replication Identity Range Error

Jan 8, 2008

Hi all i have setup merge replication with one publisher and 3 subscribers



The replication worked fine for about 2 months then i recieved the following error on all my subscriptions



The Publisher failed to allocate a new set of identity ranges for the subscription.
This can occur when a Publisher or a republishing Subscriber has run out of identity
ranges to allocate to its own Subscribers or when an identity column data type does
not support an additional identity range allocation. If a republishing Subscriber has
run out of identity ranges, synchronize the republishing Subscriber to obtain more
identity ranges before restarting the synchronization. If a Publisher runs out of identit
(Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199417)
Get help: http://help/MSSQL_REPL-2147199417


I have updated my sql server to service pack 2

The publisher is sql Standard edition and the subscribers are Express edition



Any help would be great

Thanx

View 3 Replies View Related

Merge Replication IIS Worker Process Error

Feb 25, 2006

Everyday between 18:00 and 20:00 nearly 1000 PDA Subsriber anonymously
synchronise via Merge Replication and at least two time he have the error :

IIS Worker Process
Faulting application w3wp.exe, version 6.0.3790.1830,
faulting module sscerp20.dll, version 2.0.7331.0,
fault address 0x000110f4.


And subscriber which synchronising meanwhile becomes suspect.


Can someone offer a suggestion as to the cause of and correction for
this
error?


Thanks,


Hakan G


Here is some details about our system:


Client Side
OS: Windows Mobile 2003 4.21.1088
DB: SQL CE 2.0
Microsoft SQL Server CE (ssce20.dll) 2.00.4415.0
Microsoft SQL Server CE Client Agent (ssceca20.dll) 2.00.4415.0
Development Tools: VB.NET 2003
Service Pack: .NET Compact Framework 1.0 SP3


Server Side
OS: Microsoft 2003 SP1
Internet Information Services (INETINFO.EXE) 6.0.3790.1830
(srv03_sp1_rtm.050324-1447)
IIS Worker Process (w3wp.exe) 6.0.3790.1830 (srv03_sp1_rtm.050324-1447)
HW:IBM XSERIES_346 Intel(R) Xeon(TM) CPU 3.60GHZ (2CPU) 5,00 GB RAM DB:
SQL CE 2.0
DB:SQL Server Standart Edition 8.00.2039(SP4)

SQL CE Server 2.0
Microsoft SQL Server CE Server Agent (sscesa20.dll) 2.00.7331.0
Microsoft SQL Server CE Replication Provider (sscerp20.dll) 2.00.7331.0


Merge Replication Properties
-----------------------------
status : 1
retention : 21
sync_mode : 1
allow_push : 1
allow_pull : 1
allow_anonymous : 1
centralized_conflicts : 1
priority : 100.0
snapshot_ready : 1
publication_type : 1
enabled_for_internet : 0
dynamic_filters : 1
has_subscription : 0
snapshot_in_defaultfolder : 1
alt_snapshot_folder : NULL


Merge Agent Profile:
parameter_name value
-------------------------------- ---------
-BcpBatchSize 100000
-ChangesPerHistory 100
-DestThreads 4
-DownloadGenerationsPerBatch 500
-DownloadReadChangesPerBatch 500
-DownloadWriteChangesPerBatch 500
-FastRowCount 1
-HistoryVerboseLevel 1
-KeepAliveMessageInterval 300
-LoginTimeout 15
-MaxDownloadChanges 0
-MaxUploadChanges 0
-MetadataRetentionCleanup 1
-NumDeadlockRetries 5
-PollingInterval 60
-QueryTimeout 300
-SrcThreads 3
-StartQueueTimeout 300
-UploadGenerationsPerBatch 100
-UploadReadChangesPerBatch 100
-UploadWriteChangesPerBatch 100
-Validate 0
-ValidateInterval 60

View 3 Replies View Related

Error In Merge Replication The Schema Script...

Jun 25, 2007

I'm trying to set up a merge replication. Publication is created successfully and snapshot also, but when I create pull subscription on subscriber server and merge agent starts, after some time I get an error message of this type:

The schema script '\ANILREPLDATAuncANIL_BEJK_BEJK20070625142735dl_HF_vMSCene_3836.sch' could not be propagated to the subscriber.
It seams there is a problem with certain Views and SPs, because tables are successfully created, and some Views and SPs also.

I tried to exclude problematic articles, but every time another one pops up. Up until now, I excluded 7 articles from publication (1 Stored Procedure and 6 Views) but I still get errors.

I gave up because I can't exclude half of the Views and SPs just to make it work.

Is there something that can be done to solve this problem?

Thanks!

View 3 Replies View Related

Merge Replication Metedata Cleanup Error

Feb 15, 2006

Hi,

We have a merge subscription which is reporting the following error at the subscriber:

The Merge Agent failed after detecting the retention-based metadata cleanup has deleted metadata at the Publisher for changes not yet set to the Subscriber. You must reinitalize the subscription (without upload)

I'm a bit confused about this - there have been no changes made at the publisher - why would we be getting this message?



thanks
Bruce

View 1 Replies View Related

Merge Replication Error While Applying Snapshot

Jun 24, 2006

Hi,

i am getting the below error while applying running the Synchronization agent for the Subscriber. I have created replication topology with one central server and one subscriber. Here central server has windows server 2003 and subscriber has windows XP. Both are having SQL server 2005. After creating the merge subscriber, i am runnnig the Synchronization agent manually for the first time. While running that i am getting below error. Anybody aware of this error.

2006-06-24 00:26:00.175 Applying the snapshot to the Subscriber
2006-06-24 00:26:02.722 The schema script 'D_NUM_7.sch' could not be propagated to the subscriber.
2006-06-24 00:26:02.784 Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script 'D_NUM_7.sch' could not be propagated to the subscriber.
2006-06-24 00:26:02.816 Category:AGENT
Source: WMBT-07
Number: 0
Message: The process could not read file '\WMBT-01
epldatauncLTR-IN001_TEST_PUB20060624034804D_NUM_7.sch' due to OS error 1265.
2006-06-24 00:26:02.831 Category:OS
Source:
Number: 1265
Message: The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you.

View 8 Replies View Related

Error In Merge Replication While Server Syncs

Jun 22, 2006

At first we received error like

"The merge process could not retrieve identity range resource for table..."

then after solving this error we again started syncing of servers manually then we got some other error like

"the process could not enumerate changes to the subscriber".

We tried our best to solve this problem but some error appears each time like

"The process could not deliver the snapshot to the Subscriber."

"The schema script 'sync -t"Design" -o"dbo" -d"\ECOSYSTEMD$FTPMSSQLEcoSystemftpECOSYSTEM_MLEcosystem_MLEcosystem20060619204802Design_1337.bcp" -hORDER( [intDesignId] ASC)' could not be propagated to the subscriber"

again identity erroe emerges and agin we do the same process.

How to solve these problem?

View 1 Replies View Related

Merge Replication: Unique Index Error 1505

Mar 23, 2002

We are currently attempting to (Merge) replicate a database between 2 servers; distributor and subscriber. Apparently there are no Primary Keys in the database, and without the input of the developers, we can only assume that data integrity must be maintained by the application and the database is somewhat generic. In any case, what we are experiencing is that when we attempt to replicate, and you may know, you need PKs. Without any, SQL Server has utilized it's own (Row GUIDs). The Snapshot worked fine, but the merge agent reports error 1505.

The error is "CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID %d. Most significant primary key is '%S_KEY'."

The fix and workaround are SP2 and deselecting Unique in the index propoerties of the index raising the error. We already had SP2 on the system. Tried the other and still the same issue occurs.

Microsoft's Knowledgebase has nothing. Any suggestions or fixes would be greatly appreciated.

Regards,
Alex Cohen (MCSE, MCDBA, MCT)

View 1 Replies View Related

SQL 2012 :: Error In Conflicts Tables In Merge Replication

Feb 13, 2015

There is an error in one of my merge publication. The error is,

The change for the row with article nickname 2336003 (test), rowguidcol {436456F0-F5AD-E411-80CF-5CF3FC1D2D76} could not be applied at the destination. Further information about the failure reason can be found in the conflict logging tables.

When i checked my tables I got following values in rowguid column

publication 436456F0-F5AD-E411-80CF-5CF3FC1D2D76
subscriptionD824D120-23AD-E411-80E3-00155D0E1001
conflict tables 689C6A61-5359-4BB5-BECD-B03F5F94D79A

View 0 Replies View Related

SQL Server Compact Edition Merge Replication Error

Feb 27, 2007

Hi
I am trying to complete sql server compact edition book online walkthrough "Creating a Mobile Application with SQL Server Compact Edition". I am successful to complete it as guided using all default settings (e.g. anonymous access, windows authenticaion etc.) and the sample run on both emulator and my pocket pc svc5000. I have following configuration..

Windows 2000 professional sp4
Sql server 2005 standard edition sp1
VS 2005 profesional edition (sp1 not installed)
Sql server compact edition
Sql server compact edition server tools

But the problem is that in production environment i will not be able to connect to the sql server using named instance (e.g machine_nameinstance_name). i have to use ip address in that situation. so i tried to modify the sample to use ip address in place of named instance and then the problem starts.. I have configued my sql server to allow remote connections using tcp/ip and named pipes using sql surface area config tool.

When using named instance i used following code to Synchronize with sqlserver 2005 with and it worked perfectly :

Dim filename As New String("Program FilesTestTest.sdf")
Dim repl As New SqlCeReplication()
repl.InternetUrl = http://machine_name/Test/sqlcesa30.dll
repl.Publisher = "machine_nameinstance_name"
repl.PublisherDatabase = "Test"
repl.PublisherSecurityMode = SecurityType.NTAuthentication
repl.Publication = "Test"
repl.Subscriber = "Test"
repl.SubscriberConnectionString = "Data Source='" + filename + "';Password='';Max Database Size='128';Default Lock Escalation ='100';"
Try
repl.AddSubscription(AddOption.CreateDatabase)
repl.Synchronize()
Catch err As SqlCeException
MessageBox.Show(err.ToString)
End Try

When i tried to do replication using ip address it shows following error:

System.Data.SqlServerCe.SqlCeException was unhandled
  HResult=-2147467259
  Message="Failure to connect to SQL Server with provided connection information. SQL Server does not exist, access is denied because the IIS user is not a valid user on the SQL Server, or the password is incorrect."
  NativeError=29061
  Source="Microsoft SQL Server Compact Edition"
  StackTrace:
       at System.Data.SqlServerCe.SqlCeReplication.Synchronize()
       at TEST.MainModule.Sync()
       at Test.MainModule.Main()

I am using following code to connect using ip address:

Dim repl As New SqlCeReplication()
repl.InternetUrl = http://XXX.XXX.XXX.XXX/test/sqlcesa30.dll
repl.PublisherNetwork = NetworkType.TcpIpSockets
repl.PublisherAddress = "XXX.XXX.XXX.XXX,XXXX"
repl.Publisher = "SQL2005"      'instance name of sql in sql2005
repl.PublisherSecurityMode = SecurityType.NTAuthentication
repl.PublisherDatabase = "Test"
repl.Publication = "Test"
repl.Subscriber = "Test"
repl.SubscriberConnectionString = "Data Source='" + filename + "';Password='';Max Database Size='128';Default Lock Escalation ='100';"
repl.AddSubscription(AddOption.CreateDatabase)
repl.Synchronize()


I have give rights to iuser_manchine_name in the public access list of publication and on database also.

I don't have any idea on where i am wrong... Please help soon..
Many thanks in advance..

View 1 Replies View Related

Merge Replication Subscriber Error: Invalid Cursor State

Aug 13, 2004

These errors occur at the subscriber. First, "The merge process could
not query the last sent and received generations" is generated, then
immediately afterwards, "invalid cursor state" is generated. We are
trying to pull a new subscription snapshot from the republisher. The
subscriber has been added and removed from the replusher's pull
subscriptions a number of times for testing. Now, we cannot get the
subscriber to re-sync with the republisher.

Any ideas?

View 1 Replies View Related

Snapshot For Merge Replication Error: Discover Dependencies Failed

Mar 1, 2006

I'm converting an existing production replication process to SQL 2005 for testing. My snapshot for a merge replication is failing.

Environment: Single XP server, no filters, @schema_option = 0x000000000C034DD1

I have several snapshot jobs in my process, 2 for transactional replication and 2 for merge replications. In both types, I'm replicating from A to B and then from B to C. In the failing job, I'm merge replicating from B to C. In this failing snapshot job, the error messages are:

2006-03-01 18:42:17.22 [58%] Bulk copying snapshot data for article 'MyName1'
2006-03-01 18:42:17.34 [58%] Bulk copied snapshot data for article 'MyName2' (0 rows).
2006-03-01 18:42:17.41 [58%] Bulk copied snapshot data for article 'MyName1'(195 rows).
2006-03-01 18:42:29.84 [61%] Discovering dependencies among article objects in the specified publication
2006-03-01 18:42:33.66 [61%] The replication agent had encountered an exception.
2006-03-01 18:42:33.66 Source: Unknown
2006-03-01 18:42:33.66 Exception Type: Microsoft.SqlServer.Management.Smo.FailedOperationException
2006-03-01 18:42:33.66 Exception Message: Discover dependencies failed.
2006-03-01 18:42:33.66 Message Code: Not Applicable
2006-03-01 18:42:33.66


Does anyone have an idea what I could look for to try and fix this?

The A to B snapshot obviously uses the same tables. My snapshot for merge job (which worked) messages for the A to B snapshot are:

Message
2006-03-01 18:40:24.98 Time spent analyzing foreign key references (seconds): 0.00
2006-03-01 18:40:24.98 Time spent analyzing check and default constraint references (seconds): 0.19
2006-03-01 18:40:24.98 Time spent analyzing non-article object dependencies (seconds): 0.42
2006-03-01 18:40:24.98 Time spent preparing snapshot generation (seconds): 35.49
2006-03-01 18:40:24.98 Time spent generating merge replication procedures (seconds): 41.39
2006-03-01 18:40:24.98 Time spent generating merge replication stored procedure scripts for subscribers (seconds): 20.66
2006-03-01 18:40:24.98 Time spent bulk copying data (seconds): 1.25
2006-03-01 18:40:24.98 Time spent copying/compressing generated file (seconds): 0.00
2006-03-01 18:40:25.00 Time spent adding rowguid columns/creating merge triggers (seconds): 1.38
2006-03-01 18:40:25.00 Time spent posting snapshot commands (seconds): 25.97
2006-03-01 18:40:25.00 *******************************************************************************

 

I kicked off the job again and got a different error message:

Message
2006-03-01 19:17:30.32 ---------------------------------------------
2006-03-01 19:17:30.32 -BcpBatchSize 100000
2006-03-01 19:17:30.32 -HistoryVerboseLevel 2
2006-03-01 19:17:30.32 -LoginTimeout 15
2006-03-01 19:17:30.32 -QueryTimeout 1800
2006-03-01 19:17:30.32 ---------------------------------------------
2006-03-01 19:17:30.32 Connecting to Publisher 'xxx-xxxxxxxx'
2006-03-01 19:17:30.34 Publisher database compatibility level is set to 90.
2006-03-01 19:17:30.36 Retrieving publication and article information from the publisher database 'xxx-xxxxxxxx.xxxxxxxxx'
2006-03-01 19:17:30.54 [0%] The replication agent had encountered an exception.
2006-03-01 19:17:30.54 Source: Replication
2006-03-01 19:17:30.54 Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentSqlException
2006-03-01 19:17:30.54 Exception Message: Data is Null. This method or property cannot be called on Null values.
2006-03-01 19:17:30.54 Message Code: 52006
2006-03-01 19:17:30.54

Does that help provide a clue?


 

View 7 Replies View Related

Error While Propagating Initial Snapshot To Subscriber (Merge Replication)

Jun 27, 2006

Hi all.

I get the following error when trying to run a pull subscription from the subscriber:

The schema script '' could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
---------------------------------------------------------------------------------------------------------------
The process could not connect to FTP site 'ftp://ESOFTSERVER.NO-IP.INFO' using port 21.
(Source: ESOFT (Agent); Error number: 0)
---------------------------------------------------------------------------------------------------------------
The connection with the server was reset
(Source: (OS); Error number: 12031)
---------------------------------------------------------------------------------------------------------------


I've tried everything I could to solve this problem, but I can't get it working.

Thanks for any advise.

Fabio Reynoso

View 5 Replies View Related

Merge Replication Error: 'Failure To Connect To SQL Server With Provided Connection

Mar 6, 2007

Hi!I´m trying to create a merge replication publication for a SQL MobileApplication .Everything works fine creating the publication and I'm able to dothehttp://xxx.xxx.xxx.xxx/aaaaaaa/sqlcesa30.dll, and it display's the"sql server mobile server agent 3.0".But when I run the application on the PDA and it´s doing thereplication it appears the following error:'Failure to connect to SQL Server with provided connectioninformation . SQL Server does not exist , access is denied becausetheIIS user is not a valid user on the SQL Server , or the password isincorrect' .any idea of which could be the reason...?Thanks in advance!!!

View 1 Replies View Related

Merge Replication Sync Fails With Error Code 80040E19 On Handheld

Feb 14, 2007

Hi;

We are performing merge replication between SQL Server 2005 and SQL Server Mobile with more than 1100 handheld, and recently replications are terminating with eror code 80040E19.
We can only avoid the problem by deleting the related user's partition directory and reruning the related user's dynamic snapshot.

 

Any advice on this issue would be appreciated

Thanks,
Hakan Gümüs

View 4 Replies View Related

Weird Results Post Merge Agent Run (Automatic Identity Range Management)

Dec 1, 2005

I have implemented replication between 2 servers (SERVER1 AND SERVER2) and for test purposes i just have 1 table(Table1) in the publisher.

View 1 Replies View Related

Sql Agent Throwing Config Error I'm Not Using

Feb 20, 2008

OK so I have this SSIS package that uses a connection call "Conn1". I added this to my configuration file (which also contains connections called "Conn2" and "Conn3" which are used by other packages. Works fine in DEV when run via SQL Agent. I moved SSIS package and config file to prod server. SQL Agent now throws error on this package saying it cannot resolve path to "Conn3". This package doesn't use "Conn3"... I opened both the SSIS package and the Config file in notepad and verified Conn3 wasn't referenced in the package... HELP !!!!

View 3 Replies View Related

Analysis :: MDX-Query Throwing Error

Nov 18, 2015

I am new to SSAS and learning mdx, I am running the following query but it is throwing error "Parser: The syntax for 1 is incorrect",

Select [Measures].[Order Quantity] on axis(0),
[DimProduct].[Product By Category].[ProductCategory].members on axis(1)
From [ResellerSales]
where
Except({[DimProduct].[Product By Category].[ProductCategory].members},
{[DimProduct].[Product By Category].[ProductCategory].&[1]})

View 6 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved