Using ScriptStart in VC++ doesn't seems to be working.

[zzdx8n]

Message Edited by zzdx8n on 09-12-2008 03:32 PM

[zzdx8n]

Hi Matthias:

Unfortunately our analysis solution is put on hold.  I may not be able to try your suggestions.  I should know in a few days.  THANKS for your help!!

Tom

[90france]

Hi Mathias,

   This is Sudhakar A, currently analysing the problem.

The flow of the current processs is,

 .Net Webservice  ===calls===> COM DLL (ReportEngine.dll)  ===calls===> DiAdem.exe( thru Automation object of DIAdem application)

I tried the following approaches to narrow down where the problem is , whether in the .NET web service or in the COM DLL ,

I tried replacing the .NET web service client with the other clients,

1) calling COM DLL  from VC++ MFC client - it succeeds ( DIAdem.exe started without any error)
2) calling COM DLL  from .NET C# client (standalone application) - it succeeds ( DIAdem.exe started without any error)
3) calling COM DLL  from .NET Web service - this fails

Conclusion:
.NET web service is hosted by IIS.

I believe some settings of IIS might prevents the third party application (DIAdem.exe) coming up because my assumption is .NET Web service is running in the context of IIS, so it loads the COM DLL in the IIS context , which again tries to start the DIAdem.exe(a separate executable) in the context of IIS.
Pls. let us know whether there is any security settings or permissions that the DIAdem.exe expects when started from another process context i.e. IIS or there is any specific settings of IIS is needed.

Pls. let me know for any clarifications.

Thanks,

Sudhakar A

[Twigeater]

Hello Sudhakar!

As you describe the call to your ReportingEngine.dll fails?! If this it true DIAdem is out of the game?! OK, is the call from the Webservice to the COM DLL on the same machine or a DCOM call? Can you implement a custom function in the .NET webservice to return the user and query it?

I had similar problems with an Apache webserver running as service. This was running in the 'SYSTEM' user account with is limited in some ways e.g. network access. I was able to run the service in an normal user account and everything works fine (not realy recommended becaus of security reasons). Perhaps you are also able to test it this way.

Matthias

[90france]

Hi Matthias,
   The call to COM DLL suceeds, whereas from COM DLL to DIAdem  fails in the case of .NET web service but it works now.

By changing the "Identity" properties of the DIAdem to the local user, it works fine now.  I'm curios to know whether the DIAdem launched from COM DLL via .NET web service(hosted by IIS) has this kind of restrictions  i.e. it should be configured to run as local user who has admin rights ?

Thanks,
Sudhakar A

[Twigeater]

Hello Sudhakar!

I'm not familiar with the security system in windows so I can't explain you why it works now. In my case - an intranet soltuion - it was no real issue to run the app in a normal user account. Just to get a complete picture can you please say me what windows version you are working on?

Matthias