MattNC
Fri Dec 30 11:52:02 CST 2005
Glad to hear it! I'm getting ready to start upgrading our own system which
uses a number of c360 products, so I may run into the same difficulties.
Thanks for the tips.
--
Matt Wittemann
http://icu-mscrm.blogspot.com
"Bobby" wrote:
> Well thank you! I've added your blog pages concerning this issue to my
> documentation!
>
> To answer your question, I can't be certain. We installed c360 stuff and I
> can only speculate that those were the triggers that were preventing my
> upgrade.
>
> I spoke with Product Support and they told me that the specific triggers
> would be listed in my crm30svrsetup.log file located in
> <systemdrive>\Docs&Settings\<userprofilewhoinstalledCRM>Application
> Data\Microsoft\MSCRM\logs. I went in there, found the triggers, deleted
> them, and my upgrade was a success. Whew - I've been working on this for a
> week (off and on)...
>
>
> "MattNC" wrote:
>
> > Bobby, thanks for the plug! To clarify: So nobody has added any custom
> > triggers to the CRM SQL tables at any time?
> > --
> > Matt Wittemann
> >
http://icu-mscrm.blogspot.com
> >
> >
> > "Bobby" wrote:
> >
> > > So I've managed to get a Redeployment of my production server onto a test
> > > server using Redeployment Manager. Thanks to Matt Witteman's blog on filling
> > > in the holes on the Redeployment Documentation.
> > >
> > > I ran Upgrade Advisor and it failed with a Replication error. If you run
> > > into this, simply reference Article ID 872585 through CustomerSource on the
> > > Dynamics site and you should get through this pretty easily.
> > >
> > > So I have run Upgrade Advisor again and have now received a "Triggers are
> > > not consistent with CRM 1.2 triggers" - I am stumped and need help.
> > >
> > > The only thing I've added to my production server is c360 and I thought that
> > > was supported.