Interactive Resolver

Error message: "The process failed to get information about the Interactive Resolver from the registry".
I am using MSDE to subscribe to a central 2000 database using a pull subscription and the active X controls. However, the default resolver fails to operate. I have a call in with Product Support and sent them this:
Publication articles are all marked “Use the default resolver” and “Allow Subscribers to resolve conflicts interactively during on-demand synchronizations”. Note we are treating changes to the same column as being a conflict.
On the subscriber, “on demand synchronisations” are marked “Resolve Conflicts interactively…”
In my code to control the ActiveX objects, if I set the “UseInteractiveResolver” property to True, then the error message appears. If I leave this out, the default priority subscription happens.
We ARE NOT using any third party resolver, nor are we using any resolver aside from the interactive one.
However, I still cannot get the interactive resolver to display.
Is there something else. I have tried re-registering all DLLs back on the client after copying them from the 2000 CD ROM (SP3)
Hi Top,
From your descriptoin, I learnt that you the default resolver failed to operate when you subscribed to a
central 2000 database using a pull subscription and the active X controls.
Based on my experience (not 100% sure), the issue would occur if we manually or programmatically
change the Progid of conflict viewer from Wzconflict to CnfViewer. If so, the sync manager is unable to
launch the conflict viewer.
As you have call into Microsoft with Product Support, could you provide us with the Case ID so that we can
handle your post more gracefully and also for community benefits. In this way, we can address your
problem quickly and efficiently making headway to a solution.
We look forward to hearing from you.
Best regards,
Billy Yao
Microsoft Online Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
|||SRS040408600030
|||Hi Mark,
Thank you for your information! We have looked into the issue and found the causes of this issue as I
mentioned in my previous post.
When you tried to merge the data from your client which had MSDE installed you got following error 'The
process failed to get information about the interactive resolver component from the registry". This error was
due to missing DLL files or registry entries of the conflict viewer on your client system.
To solve the problem, we should check the following Registry Keys
------
HKCR\CLSID\{A2CA91F1-7328-4949-8611-8BEDB4AD503C}\InprocServer32 --> 'C:\Program Files
\Common Files\Microsoft Shared\Database Replication\Conflict Viewer\wzcnf.dll'
Check if the dll exists in the same location.
[INFO]Other Keys Accessed by conflict viewer:
HKCR\CLSID\{00000514-0000-0010-8000-00AA006D2EA4}\InprocServer32 -->'C:\Program Files\Common
Files\system\ado\msado15.dll'
HKCU\CLSID\{0BE35204-8F91-11CE-9DE3-00AA004BB851}\InprocServer32 -->'oleaut32.dll'
HKCR\CLSID\{0BE35204-8F91-11CE-9DE3-00AA004BB851}\InprocServer32 -->'oleaut32.dll'
------
and verify this steps
Steps:
======
1) The Following Files must be in the Directories mentioned for Interactive Conflict resolver to work.
\Program Files\Common Files\Microsoft Shared\Database Replication\Conflict Viewer: wzcnf.dll ,
wzcnfclt.exe
2) The following resource file should be installed in a language specific directory \Program Files\Common
Files\Microsoft Shared\Database Replication\Conflict Viewer\Resources\<LCID>: wzcnfrc.rll
The <LCID> is usually 1033.
IF these files are missing from these directories copy them from the same location on other systems where
the conflict viewer is working fine , or copy them from the Setup CD.Now go to the directory where "Wzcnf.dll
" is located and register it by typing "Regsvr32 wzcnf.dll".
NOTE: If we dont have the Resource file Wzcnfrc.rll, The Conflict viewer will still come up, but the Labels will
be missing from the Buttons on the User Interface.Once we have the Files in place and the Dll file registered,
we'll get the Interactive conflict viwer to come up normally on the MSDE Subscribers.
NOTE: The Conflict Viewer and Interactive Conflict Viewer uses the same exe and Dll.
We appreciated your time and efforts throughout the troubleshooting process. Thank you for posting in
newsgroup.
Best regards,
Billy Yao
Microsoft Online Support
Please reply to newsgroups only. Thanks.

Integration Services Considerations

We have about 150 SQL servers and basically we're considering the pros and cons of installing SSIS on a central SSIS server - that is responsible for all DTS jobs - as opposed to installing SSIS on the local SQL instance.

On the plus side so far:

1./ Central administration, alerting, change management etc

2./ Possible performance gain on the local instance not having SSIS installed?

On the negative side:

1./ Central point of failure

2./ Possibility that it would need to be a clustered...

3./ Compatibility issues may mean having to make the central SSIS server 32-bit?

4./ Possible performance cost of remote SSIS?

5./ With multiple DTS packages running at different times, when would we take the server down for maintenace...?

Would appreciate your thoughts.

First, you presented us a root whitout leafs, in other terms what are data transforming/changing with these 150 SQL Servers ?

SSIS server is used to run packages and, let's say you have 150 packages to run, can the central server resolve this workload ?

Depends on business logic i should build a SSIS grid with 10-15 nodes that can run the packages and haave many point of failures (not single).

To the other part, moving data from a SQL Servers network (that is homogenous and i guess it don't need data cleaning/transforming) to another can be made using replication or service broker.

I guess you have to build a DataWarehouse that centralize data from 150 SQL Servers. That is made obviously nightly when the people (OLTP applications) sleep so the SSIS operations can't affect performance.