- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Problem connecting to 4.4 Business Objects using the UNC path
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
01-26-2012 05:51 AM
We need to run our module (that runs outside of Mas) on a client machine. For 200 4.5, everything works fine for us when using the UNC path to the server. But we can not get it to work for 200 4.4.
The error we get is “Exception has been thrown by the target of an invocation”, during the "NewObject" call for Business Object "SY_Session". We get this error when running the module from a client 200 4.4 machine.
When I try this same module on the 200 4.4 server machine, when using the UNC path, it still fails. But when I use the full local path (C:\Sage Software\MAS 90\Version4\MAS90), it works fine. The UNC path in question is valid from both the client and server machines.
Does anyone know what I need to do to the 4.4 server and/or client machines to get this to work. Below is the code I am running, and the error occurs with the last line...
DispatchObject _ProvideXScript = null;
DispatchObject _SY_Session = null;
_ProvideXScript = new DispatchObject("ProvideX.Script");
_ProvideXScript.InvokeMethod("Init", textBox1.Text);
_SY_Session = new DispatchObject(_ProvideXScript.InvokeMethod("NewOb


