conflicts in data don't appear in conflicts for subscription

I have become aware that some database entries were not "syncd" from a
disconnected server when it came online. My only guess is that a conflict
resulted when the syncd finally happened. The problem is it was 5 days ago,
and when I look at the conflicts under the subscription, the box is empty.
How can I see conflicts from 5 days ago?
WB
Use the conflict viewer to view them. By default they are stored for 14
days or whatever you have set to be conflict_retention value to be in
sp_addmergepublication.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"WB" <none> wrote in message news:OjAYszpQIHA.4440@.TK2MSFTNGP06.phx.gbl...
>I have become aware that some database entries were not "syncd" from a
> disconnected server when it came online. My only guess is that a conflict
> resulted when the syncd finally happened. The problem is it was 5 days
> ago,
> and when I look at the conflicts under the subscription, the box is empty.
> How can I see conflicts from 5 days ago?
> WB
>
|||I am not sure what you mean when you say "use the conflict viewer..." I
open Enterprise Manager, then replication and right click on the
publication. A popup menu appears and one of the options is to view
conflicts. Is that what you mean? Is there some way to view conflicts? I
will look at the properties of the publication to see if I can locate the
days for which conflicts are kept.
WB
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23nZH2nrQIHA.2396@.TK2MSFTNGP02.phx.gbl...
> Use the conflict viewer to view them. By default they are stored for 14
> days or whatever you have set to be conflict_retention value to be in
> sp_addmergepublication.
> --
> http://www.zetainteractive.com - Shift Happens!
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "WB" <none> wrote in message news:OjAYszpQIHA.4440@.TK2MSFTNGP06.phx.gbl...
>
|||That is exactly what I mean. Conflict retention is not exposed in the
publication properties dialog.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"wb" <none> wrote in message news:ucqfHHyQIHA.2208@.TK2MSFTNGP06.phx.gbl...
>I am not sure what you mean when you say "use the conflict viewer..." I
>open Enterprise Manager, then replication and right click on the
>publication. A popup menu appears and one of the options is to view
>conflicts. Is that what you mean? Is there some way to view conflicts?
>I will look at the properties of the publication to see if I can locate the
>days for which conflicts are kept.
> WB
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23nZH2nrQIHA.2396@.TK2MSFTNGP02.phx.gbl...
>

Configuring SSIS in an Active\Active Cluster

OK so I am aware that the SSIS service can be clustered relatively easily but my problem is a bit more complex I believe.

I have an Active\Active\Active 3 node cluster running Windows 2003 sp1 all running SSIS packages. What I need is a solution to having an instance fail to another node and still be able to run scheduled SSIS packages through the SQL Agent.

The solution that I have come up with is to have a single network share for all three instances of SSIS running locally on the individual nodes. I have removed the ability for SSIS to look in MSDB by altering the config file and reference only the Packages share on the network for accessability. They all share the same config file on the share as well. The share structure looks something like this simplified example.

\\server1\SSIS\Configuration

\\server1\SSIS\Packages

\\server1\SSIS\Packages\Instance1\

\\server1\SSIS\Packages\Instance2\

\\server1\SSIS\Packages\Instance3\

Once I change the registry to point to the config file all three instances can access the Instance1, 2 or 3 directories.

This works ok for the jobs, and I can access the stored packages under the file system folder only if I'm remotely connected to that particular physical server hosting the service or on the console. The problem I am having though is when users or I attempt to access the SSIS Engine through SSMS from our locale machines. It seems as though SSMS is having trouble with the passthrough of the directory information. On the share I obviously have permissiosn to access the directory structure (full control to be exact) because I can get to it when I access it from SSMS on the server.

This is the error I get...

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

ADDITIONAL INFORMATION:

The storage location for the folder "File System\" cannot be accessed. (MsDtsSrvr)

DETAILS:

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

Program Location:

at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.BuildDynamicItemWithQuery(IList nodes, INodeInformation source, INavigableItem sourceItem, String urnQuery, Boolean registerBuilder, Boolean registerBuiltItems)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.BuildDynamicItem(IList nodes, INodeInformation source, INavigableItem sourceItem, IFilterProvider filter)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.Build(INodeInformation source, INavigableItem sourceItem, IFilterProvider filter)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItem.GetChildren()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ExplorerHierarchyNode.BuildChildren()

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

The storage location for the folder "File System\" cannot be accessed. (MsDtsSrvr)

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.GetDtsServerPackageInfos(String sPackageFolder, String sServerName)
at Microsoft.SqlServer.Dts.SmoEnum.PackageEnum.GetData(EnumResult erParent)
at Microsoft.SqlServer.Management.Smo.Environment.GetData()
at Microsoft.SqlServer.Management.Smo.Environment.GetData(Request req, Object ci)
at Microsoft.SqlServer.Management.Smo.Enumerator.GetData(Object connectionInfo, Request request)
at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request)

Any work around or suggestion would be appreciated.

Thanks,

Zach

Anyone have any thoughts on how to make this work?

Thanks for the look,

Zach