Sage MAS 90 and 200 Sage MAS 500 blogs Product Feedback Support Training
Reply
Contributor
ebdeveloper
Posts: 15
Registered: 01-23-2012
0

Re: BOI & Shipment

Thanks again. It is working.

 

So my application is finally working fine in my local environment.

I think it is ready to be deployed on the client’s computer. I am checking the registry for SOTAMAS90

path and what a surprise? It is a network path. I am thinking it should not be any problem BUT big mistake ;-) It does not work. ;-(

 

Here is what I have tried:

DispatchObject pvx = new DispatchObject("ProvideX.Script")

pvx.InvokeMethod("Init", “\\networkpath\MAS90\Home”); <- Error

 

Error: Exception has been thrown by the target of an invocation.

InnerError: Failed to load the ProvideX library

Error: Unknown name. (Exception from HRESULT: 0x80020006 (DISP_E_UNKNOWNNAME))

 

So I have also tried:

DispatchObject pvx = new DispatchObject("ProvideX.Script")

pvx.InvokeMethod("Init", “C:\Program Files\Sage Software\MAS 200 Client\Version4\MAS90\Home”); ßno error this time but

DispatchObject oSS = new DispatchObject(pvx.InvokeMethod("NewObject", "SY_Session")) <- Error

 

Error: Exception has been thrown by the target of an invocation.<NewObject Error: 90>

 

What now? Are there any hidden tricks I have to do to make it work?

Please help.

George

Contributor
ebdeveloper
Posts: 15
Registered: 01-23-2012
0

Re: BOI & Shipment

I am looking on the first error (DISP_E_UNKNOWNNAME) and I have just realized one think.

My application is running as a service under “LocalSystem” account.

Could it be a problem? And what should I do to make it work?

George

Contributor
ebdeveloper
Posts: 15
Registered: 01-23-2012
0

Re: BOI & Shipment

Yap that was the problem. I have changed the user on the service and it is working.