Rollup 2 Installation Problems

Have been trying to install rollup 2 for MSCRM 3. Keep getting an
error as the installation checks the system configuration. The error
message box sez:

"Micorsoft.Crm.SE.TimeZoneUpdate.TimeZoneUpdatePatch.exe - Common
LanguageRuntime Debugging Services

Application has generated an exception that could not be handled.

Process id = 0xbb4 (2996), Thread id = 0x1198 (4504)

Click OK..."

Any ideas?

Thanks in advance,
Paul McBride

Merijn
Fri Oct 12 05:19:00 PDT 2007

Hi,

I believe rollup 2 is important and it should be possible to get it
installed without any problem. I have it running in many international
installations. Since the error message you receive is rare, I first recommend
carefully check all release notes that have to do with timezones. To ensure
every prereq is in place before you install this patch. If this doesn't help
I think it is worth spending a support call with the Microsoft Dynamics
support team on this. My experience is they will have a quick and reliable
result.

Best regards,
Merijn

"paulski.mcb@gmail.com" wrote:

> Have been trying to install rollup 2 for MSCRM 3. Keep getting an
> error as the installation checks the system configuration. The error
> message box sez:
>
> "Micorsoft.Crm.SE.TimeZoneUpdate.TimeZoneUpdatePatch.exe - Common
> LanguageRuntime Debugging Services
>
> Application has generated an exception that could not be handled.
>
> Process id = 0xbb4 (2996), Thread id = 0x1198 (4504)
>
> Click OK..."
>
> Any ideas?
>
> Thanks in advance,
> Paul McBride
>
>

matt
Thu Nov 01 02:02:30 PDT 2007

Did you resolve this problem? We have the same issue. MS reconmended
that we import the TimeZones registry entries from a system that
rollup 2 has been successfully applied to - however this hasn't help
and MS seem stumped.

DanBlakeAtNet
Fri Jan 11 10:50:04 CST 2008

Paul,
In case you didn't figure this out by now (or for the benefit of others
searching for a solution to this problem), the fix is to add OLEDBTimeout
value to MSCRM registry and set the value to a high number of seconds (e.g.
3600 decimal). The UR2 notes actually suggest that you might need to do
this. I have found that it is almost universally necessary.

1 Click Start, click Run, type regedit, and then click OK.

2 Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM

3 Right-click MSCRM, point to New, and then click DWORD Value to create a
new DWORD value.

4 Rename the DWORD value to the following value: OLEDBTimeout

5 Right-click the DWORD value, and then click Modify.

6 Click Decimal in the Base option, type 3600 in the Value data box, and
then click OK. (3600 Decimal is 60 minutes)

--
Dan Blake
At-Net Services (formerly Intelligix, Inc.)
http://www.at-net.net



"paulski.mcb@gmail.com" wrote:

> Have been trying to install rollup 2 for MSCRM 3. Keep getting an
> error as the installation checks the system configuration. The error
> message box sez:
>
> "Micorsoft.Crm.SE.TimeZoneUpdate.TimeZoneUpdatePatch.exe - Common
> LanguageRuntime Debugging Services
>
> Application has generated an exception that could not be handled.
>
> Process id = 0xbb4 (2996), Thread id = 0x1198 (4504)
>
> Click OK..."
>
> Any ideas?
>
> Thanks in advance,
> Paul McBride
>
>

GrizzlyTech
Wed Mar 19 08:15:02 CDT 2008

Getting the same error

I tried the res documented in the KB for the TimeZoneUpdate, but the Windif
tool says there are no differences in the Reg entries.

I tried changing the OLEDBtimout value, but no luck either.

We have rebuilt the Windows 2003 server, reinstalled CRM a couple of times
but no joy.
I've just opened a call with MS

Any Help appreciated.

--
Thanx
Grizz


"Dan Blake (At-Net)" wrote:

> Paul,
> In case you didn't figure this out by now (or for the benefit of others
> searching for a solution to this problem), the fix is to add OLEDBTimeout
> value to MSCRM registry and set the value to a high number of seconds (e.g.
> 3600 decimal). The UR2 notes actually suggest that you might need to do
> this. I have found that it is almost universally necessary.
>
> 1 Click Start, click Run, type regedit, and then click OK.
>
> 2 Locate the following registry subkey:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
>
> 3 Right-click MSCRM, point to New, and then click DWORD Value to create a
> new DWORD value.
>
> 4 Rename the DWORD value to the following value: OLEDBTimeout
>
> 5 Right-click the DWORD value, and then click Modify.
>
> 6 Click Decimal in the Base option, type 3600 in the Value data box, and
> then click OK. (3600 Decimal is 60 minutes)
>
> --
> Dan Blake
> At-Net Services (formerly Intelligix, Inc.)
> http://www.at-net.net
>
>
>
> "paulski.mcb@gmail.com" wrote:
>
> > Have been trying to install rollup 2 for MSCRM 3. Keep getting an
> > error as the installation checks the system configuration. The error
> > message box sez:
> >
> > "Micorsoft.Crm.SE.TimeZoneUpdate.TimeZoneUpdatePatch.exe - Common
> > LanguageRuntime Debugging Services
> >
> > Application has generated an exception that could not be handled.
> >
> > Process id = 0xbb4 (2996), Thread id = 0x1198 (4504)
> >
> > Click OK..."
> >
> > Any ideas?
> >
> > Thanks in advance,
> > Paul McBride
> >
> >

GrizzlyTech
Wed Mar 19 09:34:00 CDT 2008

ok, now I have to say - never mind. the OLEDBTimeout fixed it.
Thing is I thought I tried this yesterday and it didnâ??t work, but I think I
rebooted the server (5 times) since then.

--

Grizz


"GrizzlyTech" wrote:

> Getting the same error
>
> I tried the res documented in the KB for the TimeZoneUpdate, but the Windif
> tool says there are no differences in the Reg entries.
>
> I tried changing the OLEDBtimout value, but no luck either.
>
> We have rebuilt the Windows 2003 server, reinstalled CRM a couple of times
> but no joy.
> I've just opened a call with MS
>
> Any Help appreciated.
>
> --
> Thanx
> Grizz
>
>
> "Dan Blake (At-Net)" wrote:
>
> > Paul,
> > In case you didn't figure this out by now (or for the benefit of others
> > searching for a solution to this problem), the fix is to add OLEDBTimeout
> > value to MSCRM registry and set the value to a high number of seconds (e.g.
> > 3600 decimal). The UR2 notes actually suggest that you might need to do
> > this. I have found that it is almost universally necessary.
> >
> > 1 Click Start, click Run, type regedit, and then click OK.
> >
> > 2 Locate the following registry subkey:
> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
> >
> > 3 Right-click MSCRM, point to New, and then click DWORD Value to create a
> > new DWORD value.
> >
> > 4 Rename the DWORD value to the following value: OLEDBTimeout
> >
> > 5 Right-click the DWORD value, and then click Modify.
> >
> > 6 Click Decimal in the Base option, type 3600 in the Value data box, and
> > then click OK. (3600 Decimal is 60 minutes)
> >
> > --
> > Dan Blake
> > At-Net Services (formerly Intelligix, Inc.)
> > http://www.at-net.net
> >
> >
> >
> > "paulski.mcb@gmail.com" wrote:
> >
> > > Have been trying to install rollup 2 for MSCRM 3. Keep getting an
> > > error as the installation checks the system configuration. The error
> > > message box sez:
> > >
> > > "Micorsoft.Crm.SE.TimeZoneUpdate.TimeZoneUpdatePatch.exe - Common
> > > LanguageRuntime Debugging Services
> > >
> > > Application has generated an exception that could not be handled.
> > >
> > > Process id = 0xbb4 (2996), Thread id = 0x1198 (4504)
> > >
> > > Click OK..."
> > >
> > > Any ideas?
> > >
> > > Thanks in advance,
> > > Paul McBride
> > >
> > >