Jump to content

This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.

MSM install problem on Terminal Server

1 reply to this topic


  • Members
  • 2 posts

Posted 25 November 2003 - 10:47


I've a problem installing my software on a Terminal Server. I hope someone
could help me with it. I'm an experienced user of Installshield Developer, but
I was not able to use that tool here.

I've developed an application using VB6. Target and development platform is W2K. It uses some ocx's and dll's. I created
an MSI installation package using VS installer. The dependencies to the dll's are
properly detected and the corresponding merge modules are included in
the installation.

If I install the software on my Terminal Server (Win2000 user compatibility, admin account, install mode etc) it succeeds. If I start my program as administrator,
things work fine. I've also some normal users configured who do not have full
access. If I start under such an acount, some dll's can't be found. They are there,
but not registered for the current user. These dll's are actually from a merge
sysinfo.ocx (sysinfo.msm)
msmapi32.ocx (msmapi32.msm)

It seems that the MSM's do not install for all users. What I see, is that when I
start my application, some MSI install is started for the current user.

Changing Terminal Services security compatibility to "TS user" solves the problem
but is not an option for me. (My admins will kill me). The normal users will
also not have the rights to register manually.

Does anyone know why the MSM's are not set up properly for all users?
All the other MSM's work fine.

I hope someone has ideas! Every wild guess may be helpful.




  • Members
  • 8 posts

Posted 05 February 2004 - 22:13

At least check what is triggering the repair. Check the application eventlog for 1001 and 1004 MsiInstaller messages to see what is kicking off the repair. The two merge modules you mention are writing to HKCR and installing to shared folders so there should not be any per-user component.