Absolutely weird exception using COM Interop & VB.net

[ZaM]

Hi all,

We'd been developing some COM libraries in .net, one of them is a kind
of proxy who consumes some web services, traslates the XML output of
these WS to JSON using Newtonsoft.JSON, and then returns the parsed
JSON back to IIS/ASP 3.

Everything works fine in my development environment and QA also works
well. But in the production server, Server.CreateObject creates an
instance, but calling any method of the proxy throws this exception:
mscorlib error '80070005'

Access to the path '\Microsoft Corporation\Microsoft(R) Windows (R)
2000 Operating System\5.00.2195.6692' is denied.

/login_fs.asp, line 18
even if the method just returns a hard coded string (just for testing
purposes) the invocation always throws the same error.

..net framework 2.0 is installed in both QA and Production server, the
same Windows 2000 Advanced server, the same domain policies, but
something goes wrong in production.

I disabled the settings, the error log and everything that could try
to access any file in the server filesystem.

any idea??????

Thanks in advance.

[=?Utf-8?B?Um9nZXIgVHJhbmNoZXo=?=]

Hello,

Did you make the registration for the ASP.NET libraries (take care about its
version) on the production server ?

Also, do you have enough permissions to publish on the IIS folder ?

I hope it helps,

--
Roger Tranchez
MCTS
..NET 2005 and DB developer
"ZaM" wrote:

Hi all,

We'd been developing some COM libraries in .net, one of them is a kind
of proxy who consumes some web services, traslates the XML output of
these WS to JSON using Newtonsoft.JSON, and then returns the parsed
JSON back to IIS/ASP 3.

Everything works fine in my development environment and QA also works
well. But in the production server, Server.CreateObject creates an
instance, but calling any method of the proxy throws this exception:
mscorlib error '80070005'

Access to the path '\Microsoft Corporation\Microsoft(R) Windows (R)
2000 Operating System\5.00.2195.6692' is denied.

/login_fs.asp, line 18
even if the method just returns a hard coded string (just for testing
purposes) the invocation always throws the same error.

..net framework 2.0 is installed in both QA and Production server, the
same Windows 2000 Advanced server, the same domain policies, but
something goes wrong in production.

I disabled the settings, the error log and everything that could try
to access any file in the server filesystem.

any idea??????

Thanks in advance.

[ZaM]

Hi
AFAIK, the installation procedure was the same in preproduction and
production servers and, again AFAIK, both servers has the same
configuration.

I've found a very interesting fact. In our development server we have
found a file named dllhost.log in a folder called C:\Microsoft
Corporation\Microsoft® Windows® Operating System\5.1.2600.2180. The
file is empty.

Why dllhost is trying to make a log file? And why in that location??

Thanks in advance
On Apr 16, 3:59 am, Roger Tranchez <[e-mail]:

Hello,

Did you make the registration for the ASP.NET libraries (take care about its
version) on the production server ?

Also, do you have enough permissions to publish on the IIS folder ?

I hope it helps,

--
Roger Tranchez
MCTS
.NET 2005 and DB developer

"ZaM" wrote:

Hi all,

We'd been developing some COM libraries in .net, one of them is a kind
of proxy who consumes some web services, traslates the XML output of
these WS to JSON using Newtonsoft.JSON, and then returns the parsed
JSON back to IIS/ASP 3.

Everything works fine in my development environment and QA also works
well. But in the production server, Server.CreateObject creates an
instance, but calling any method of the proxy throws this exception:

mscorlib error '80070005'

Access to the path '\Microsoft Corporation\Microsoft(R) Windows (R)
2000 Operating System\5.00.2195.6692' is denied.

/login_fs.asp, line 18

even if the method just returns a hard coded string (just for testing
purposes) the invocation always throws the same error.

..net framework 2.0 is installed in both QA and Production server, the
same Windows 2000 Advanced server, the same domain policies, but
something goes wrong in production.

I disabled the settings, the error log and everything that could try
to access any file in the server filesystem.

any idea??????

Thanks in advance.