I have DTM 4.1.1 installed on my Win2000 pro dell with all or nearly all of the MS updates. I have trend AV. The machine gets some apps via citrix over a win2003 server.

we use ms exchange 2000 server which i access thru Outlook 2002.

My problem:

I initially ran DTM 3.6 with no trouble, using the redirector for email and cable sync for tasks, address book and calendar.

for whatever reason, i installed 4.1.1 and it has been a disaster.

Following first install, everything works fine. After the first restart, redirector works fine but DTM and the Device Manager are broken. When I try to start DTM (either by clicking the icon or from the startup folder) the window for DTM flashes on the screen then disappears. With the device manager, the icon is in the startup bar as loaded but clicks on the icon will not launch the properties of the device manager.

Thus, what is the beef with 4.1.1 and my setup?

It seems that something is causing DTM to quit before it starts - it does not appear to be the AV. Something in windows seems to quash it.

Any ideas?

Searching these forums has produced some hints but nothing that fits. I've tried to address access control list persmissions but no luck. Reinstall fixes until the next restart, of course. Reinstalling the software every restart is not an option.

I'd appreciate any thoughts about migrating back to 3.6 (how to do it) or to fix the install of 4.1.1. It doesn't make sense to quit on startup without something in the OS causing the trouble.

Hopefully, management and IT will decide that everyone needs BBs and they will install BES. I'm not confident that will happen sufficiently soon so a fix for this would be great.

THanks.

Happened to me with my users as well. 4.1 DTM had installed fine on a Friday, system downtime over the weekend with all servers getting MS updates applied. The following Monday, dtm did just as you describe - event log shows install successful but no matter what I did it would just flash and not run. I was told that it had to do with a "bad security patch" that was re-released a few days later. Finally after a few weeks it works here again - can't tell you why or what was done - we do seem to take our time applying MS updates to servers so maybe it was just the re-released security patch. I just went back to installing 4.0 until it was fixed (thank goodness before my roll out of 275 8700s!!!)

i've inquired and it broke after an XML update dated feb 2002 was installed as well, just recently.

I'm moving back to 4.1 but I'd like to know how to fix it because I'm contemplating an upgrade to the 8700 from cingular and want to deploy it to 15-30 staff.

thanks again.

Anyone else have any ideas?