Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
XP SP2 not allowing shared dll to launch from .NET app
jprucha
Member
10-26-2004 12:57 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi All,
I have an application that I've created in LabVIEW 7.1 and turned it into a shared dll. I then created a .Net application that would call the shared dll and return back the output. This was working fine before installing XP SP2. I have tried unblocking pop-ups and also turning off the new firewall but to no avail.
I am not receiving any errors in the event view logs or the iis logs. Does anyone have any ideas as to why SP2 might be stopping a shared dll to be invoked or how to remedy the situation?
Thanks for any help you can give.
Jim
I have an application that I've created in LabVIEW 7.1 and turned it into a shared dll. I then created a .Net application that would call the shared dll and return back the output. This was working fine before installing XP SP2. I have tried unblocking pop-ups and also turning off the new firewall but to no avail.
I am not receiving any errors in the event view logs or the iis logs. Does anyone have any ideas as to why SP2 might be stopping a shared dll to be invoked or how to remedy the situation?
Thanks for any help you can give.
Jim
Matt_F
NI Employee (retired)
10-28-2004 02:55 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hello Jim,
I have not heard of SP2 having problems with shared DLLs in .NET. The first thing we need to figure out is where the issue is located.
For example:
Does the VI built into a DLL run in its VI state. If it does not, it would indicate that the VI is at fault and not the .NET / shared library interface.
What behavior do we see in the .NET application with XP SP2? Does the program hang or does it crash at the point the DLL is called?
Have you tried to rebuild and relink to the DLL after the upgrade?
What type of operations are you doing in the DLL? Is there anything that might conflict with the new security measures of SP2?
This information should help us in diagnosing the issue.
Regards,
Matt F
I have not heard of SP2 having problems with shared DLLs in .NET. The first thing we need to figure out is where the issue is located.
For example:
Does the VI built into a DLL run in its VI state. If it does not, it would indicate that the VI is at fault and not the .NET / shared library interface.
What behavior do we see in the .NET application with XP SP2? Does the program hang or does it crash at the point the DLL is called?
Have you tried to rebuild and relink to the DLL after the upgrade?
What type of operations are you doing in the DLL? Is there anything that might conflict with the new security measures of SP2?
This information should help us in diagnosing the issue.
Regards,
Matt F
10-28-2004 03:20 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi Matt,
The VI works fine in standalone. All the VI does is take a string and return the uppercase of the string sent to it.
What I have done to try and narrow this down is I have built a VB6 COM object that wraps the shared DLL. I have used this in a VB executable and it works fine. I have used it in a VBScript file and it works fine here also. It does not work when I incorporate it into an ASP or ASPX page.
I don't get any entries into the event viewer logs or even in the IIS logs. I have also turned off the new fire wall installed by SP2 and have even put the ASPNET user into the Administrators group to see if it is a permissions problem for the ASPNET user. This did not change the outcome at all.
Another engineer at work suggested uni
nstalling IIS and reinstalling it and registering .net with it again and then remapping the .NET apps and see if that works.
I'm kind of stuck as this was a proof of concept and the basis of our design to be able to send strings back and forth to a LabVIEW shared dll.
Any thoughts?
Jim
The VI works fine in standalone. All the VI does is take a string and return the uppercase of the string sent to it.
What I have done to try and narrow this down is I have built a VB6 COM object that wraps the shared DLL. I have used this in a VB executable and it works fine. I have used it in a VBScript file and it works fine here also. It does not work when I incorporate it into an ASP or ASPX page.
I don't get any entries into the event viewer logs or even in the IIS logs. I have also turned off the new fire wall installed by SP2 and have even put the ASPNET user into the Administrators group to see if it is a permissions problem for the ASPNET user. This did not change the outcome at all.
Another engineer at work suggested uni
nstalling IIS and reinstalling it and registering .net with it again and then remapping the .NET apps and see if that works.
I'm kind of stuck as this was a proof of concept and the basis of our design to be able to send strings back and forth to a LabVIEW shared dll.
Any thoughts?
Jim
Matt_F
NI Employee (retired)
10-29-2004 12:38 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hello Jim,
A search of google for "ASP.NET, dll, sp2" returned multiple people having issues with DLL calls after a SP2 install. In most of them they mentioned the uninstall and reinstall of IIS solved the issue.
Regards,
Matt F
A search of google for "ASP.NET, dll, sp2" returned multiple people having issues with DLL calls after a SP2 install. In most of them they mentioned the uninstall and reinstall of IIS solved the issue.
Regards,
Matt F
