Cannot create an instance of the .NEt Framework object

AitorEG

Hello everyone!

I am creatiang a development, and it crashes in the CU 6224 "XML DOM Management", whit the next message:



"Cannot create an instace of the .NET Framweork object ..."

If I debug, we can see that it cracshes here:




Any clue? Should I do something with the DLL files? Or anything to see with the .NET framework installation?

Thank you very much, any help is really appreciated!

Slawek_Guzek

We have similar problems but not with XML but with Microsoft Word interop dlls delivered with NAV. It all started with some security patch rolled out by IT, the error was the same, and showed up when the variable was initialized as in your case

In my case IT uninstalled the Office cleared the registry, reinstalled the Office and reinstalled NAV. Uninstalling the patches also was also solving the problem but IT wanted the patches to stay. in place.

There is a difference, however, the Word interop DLLs are supposed to work on the client, and the variables referring to them are declared as RunOnClient=Yes. XMLDocument .NET vars supposed to work on the NST as far as I know.

The XMLDocument is a part of the .NET framework, I don't think it should require anything in Add-In folder. I would rather try to reinstall the NST service, or install it on a separate machine, connect the client to it and see if the problem persists.

Slawek

RockWithNAV

Agree with the above comment, Adding DLL in the Addin folder only make sense when it's a custom dll.

AitorEG

Hello!
Anyone with a small hint for this issue? I've read that i should place the DLLs in te AddIn folder of the RTC. Is that right? SHould I restart the server or something? I've found several System.Xml.dll files all over the computer. Which one is the correct one?

Thank you again

RockWithNAV

Put the DLL in the Addin folder.
Got to the property of the DotNet variable and make Run on Client as YES
Instantiate the DotNet variable and now will be good to go

Slawek_Guzek

We have similar problems but not with XML but with Microsoft Word interop dlls delivered with NAV. It all started with some security patch rolled out by IT, the error was the same, and showed up when the variable was initialized as in your case

In my case IT uninstalled the Office cleared the registry, reinstalled the Office and reinstalled NAV. Uninstalling the patches also was also solving the problem but IT wanted the patches to stay. in place.

There is a difference, however, the Word interop DLLs are supposed to work on the client, and the variables referring to them are declared as RunOnClient=Yes. XMLDocument .NET vars supposed to work on the NST as far as I know.

The XMLDocument is a part of the .NET framework, I don't think it should require anything in Add-In folder. I would rather try to reinstall the NST service, or install it on a separate machine, connect the client to it and see if the problem persists.

Slawek

RockWithNAV

Agree with the above comment, Adding DLL in the Addin folder only make sense when it's a custom dll.

AitorEG

Thank you all for your answers. I've doen both things, copy the DLLs, and allowing in the properties of the .NET object to run in the client. It seems that is working, or at least, the error is showing me now is different.



"Error in the call System.... Timeout excedeed"


I'm trying to configure the timeout like this:

HttpWebRequest := WebRequest.Create(Uri.Uri('https://XXXXXXXXXXXXXX/shipping/ship'));
HttpWebRequest.Method := 'POST';
HttpWebRequest.ContentType := 'application/xml';
HttpWebRequest.Timeout := 30000;

But it doesn't work, and I don't know if the solution would be to increment the timoeut, I'll work on it. Could this be because the WebService isn't returning a response?

Really thanks again, appreciated!!!

AitorEG

Hi everyone again,
I've solved problems with different ,NET objects, copying the DLLs in the Add-In folder (it is supposed that this is not necesary, but just in case), and introducing "YES" in the RunOnClient property of ALL the DotNet variables in the different objects.
But I'm finding issues with one object, that I can't solve with the same process I have been doing until this moment.


I've copied all this DLLs:



And as I've said before, i've also changed to YES the RunOnClient property, but nothing...

How can i try to fix this issue in another way?

Thank you very much


edit:

I thought that the issue could be that the request turns me an error, and the node can't be created becasue directly, it doesn't exist in the response. The server returns me a format error, and in the documentation, I can see that the request stream should start with "xml_in=". How can I configure this? I'm trying to do this, but with the same problem:

ByteArray := Encoding.UTF8.GetBytes('xml_in=' + XMLDocDotNet.OuterXml);