Data Techniques Online Forums

Hi,

I have got problem in setup and deployment faxman service with our application. when i successfully set up application i issue command to install a faxman service (Faxman4.exe /install) in my application it works fine. But, when i uninstall my application it does not uninstall a faxman service. I defined command (Faxman4.exe /remove) in install class before uninstall my application in BeforeUnistall event handler. However, it does not uninstall faxman service. Faxman service can only uninstall if i does not uninstall my application and use path of my application where my application and faxman4.exe are resided and issue a Faxman4.exe /remove command than it works and remove a faxman service. i cannot understand how to solve this problem.

 Any one encounter this problem ?

Thank you

 Regards,

Sailung

 Hi,

Sorry I'm not 100% sure I understand your issue but make sure you are calling faxman4.exe /remove prior to having the files deleted.  We had a customer who ran into a similar problem in their install in that it removed all the files then called their code which tried to uninstall the exe which of course didnt work.

Hi sean,

 Thank you very much for your reply. Well, i found the problem why it is not uninstall but still i cannot understand, when i install my application i issue a command of install faxman service (faxman4.exe /install) it works fine and installed a faxman service but however it does not start faxman service automatically. it only start process faxman4.exe and if i try to start a faxman service from computer management it will not allow to start faxman service. if i stopped a faxman4.exe process from task manager or from a faxman process icon then it allow to start a faxman service. i am in contradiction of the faxman service and faxman4.exe process.

will you help me to clear my vague.

Thank you

Regards,

Sailung

Hi,

Concerning the Stopping/Starting of the service, are your running under Vista?

If so, please see this thread...

http://forums.data-tech.com/forums/t/3781.aspx

Hi,

Well, I test my application in windows server 2003, i solved this problem. Actually, it make me misunderstanding between system tray icon of faxman and faxman windows service. i think faxman guys should be carefully consider between this two things.

Anyway i solved this problem

Thank you guys for your help.

Regards,

Sailung

 Hi,

Glad its working but could you elaborate on what your misunderstanding was so we can help to clarify it ? 

Hi,

Thank you, Actually, what has happend in my application is when i first issue install command in the Installer Class it install a faxman service and when i start a program after install, my first start application a faxman exe icon show on system try. After it when i checked in task manager it show a Faxman4.exe user is Administrator. However, if i stoped a Faxman4.exe and restart a Faxman service it show a user is system, that what i want because i want to run Faxman service not only Faxman4.exe.

Finally, i write a code to kill the Faxman4.exe and start a Faxman Service which i want to work properly.

What i misunderstanding between Faxman4.exe  and Faxman Service  is if Faxman4.exe which i mentioned above after install will not allow to run faxman service until it stop a Faxman4.exe nor faxman service start automatically after install.

 Thank you

Regards

Sailung

Happy Programming

I think I know what he means... I've had the same or at least similar problem.  In my installer class, I instantiate FaxMan in order to tell the server to set the tray icon to hidden.  Originally I did this:

  DataTech.FaxManNet.FaxMan faxMan = new DataTech.FaxManNet.FaxMan();
  faxMan.Server["Hidden"] = "true";
  faxMan.Dispose();

But FaxMan would often remain in memory, with the tray icon still visible (the default behavior), and then Windows could not start the service because the executable was already in memory running under the installing user's context.

I ended up adding code before and after the lines above to first start the service, then run the above code, then stop the service.  That usually, but not always, works.  Occasionally it still exhibits the same symptoms.

During uninstall, my installer class runs faxman.exe /remove, but again, it occasionally just hangs and leaves the service in an invalid state, requiring a reboot to completely uninstall. 

I also noticed in the Vista thread you referenced that the .INI HIDDEN option is no longer supported, but it does definitely still work.  Even when running as a service, the icon is visible (and works) if that value is not in the .INI file.  I don't want it showing because I don't want to allow the non-admin user to stop the service.

 Hi,

Note that when you call the .Net interface then the client interface will start the FaxMan service or applicatio. Doing a Dispose on theinterface will not shut down the server, it only closes the connection the client had to the server. You would have to call the Shutdown method to close the service/application.

Note that under Vista  that a client application must run as admin to be able to startup the service sowe recommend thatthe service be set to Automatic starting under Vista.

Lee:

I also noticed in the Vista thread you referenced that the .INI HIDDEN option is no longer supported, but it does definitely still work.  Even when running as a service, the icon is visible (and works) if that value is not in the .INI file.  I don't want it showing because I don't want to allow the non-admin user to stop the service.

Lee, would you please confirm that you see the SystemTray Icon, when running FAXMAN4 as a SERVICE under VISTA. 

Thanks

support:

Note that when you call the .Net interface then the client interface will start the FaxMan service or applicatio. Doing a Dispose on theinterface will not shut down the server, it only closes the connection the client had to the server. You would have to call the Shutdown method to close the service/application. 

Note that under Vista  that a client application must run as admin to be able to startup the service sowe recommend thatthe service be set to Automatic starting under Vista.

Sorry, I should have been more clear.  In the past, I did use the Shutdown method, but that always caused it to hang too, so I removed that call.  Starting the service, making my changes, stopping the service has usually worked as a workaround. [Edit: FaxMan.Shutdown() didn't really make it hang, but it took a longer-than-acceptible time to return from that call - up to a minute or more if I remember correctly]

Also, I didn't mean to cloud the issue with the Vista comment - I'm not using FaxMan under Vista, but I had read that thread and the comment from support was that the Hidden option was no longer valid in V4, not that it was no longer valid under Vista.