Errors/warnings occurred when generating the local proxy dll and VI wrappers for web service

[RSystems]

Hello,

I'm new to web services - trying to import a WSDL that was created by an outside vendor and placed on a company server.  I imported a previous version successfully.  The error I'm getting doesn't make a lot of sense to me, here it is:

The following errors/warnings occurred when generating the local proxy dll and VI wrappers for this web service.
Can't generate files.
Possible reasons are:
1. The output file(s) might be read-only.
Remove the read-only attribute and import the Web service again.
2. A proxy DLL that LabVIEW created under the same file path exists in memory.
Restart LabVIEW and import the Web service again.

I don't see any read-only attributes on the output files and I've tried restarting LabVIEW - no luck.  Any help is greatly appreciated.

Thanks,

Al Rauch

Merck & Co., Inc.

[Peñata]

Hi alsys,

Can you post a link to the WSDL you are using? I'd like to see if I get the error.

Thank you for choosing National Instruments.

Aaron Pena

National Instruments

Applications Engineer

http://www.ni.com/support

[RSystems]

Hi Aaron,

Unfortunately the WSDL is inside our firewall - however, I was able to import the WSDL and use the web service wrapper VIs that it created successfully with LabVIEW 8.6 on a different computer.  I'm still having the same problem with LabVIEW 2009 - I need to solve it with LV2009 since my current project is in development with this version.

Is there any known WSDL import bugs with LV2009?

Thanks,

Al

[Peñata]

Hi Al,

I could not find any known bugs with WSDL importing in LabVIEW 2009. Would it be possible for you to install LabVIEW 2009 on the same computer that you successfully imported the WSDL with LabVIEW 8.6 to see if you still see the error?

Thank you for choosing National Instruments.

Aaron Pena

National Instruments

Applications Engineer

http://www.ni.com/support

[RSystems]

Aaron,

I was able to successfully import and run the web services from the WSDL file in question in LV2009 on a different computer than the one on which I had the original problem.  Unfortunately I am still having the original problem on the project computer and will need to get it working there . . . still looking for a solution to that.  Apparently LV2009 is perfectly capable of importing and running this WSDL file, but there is something still in the way on the project PC.

Thanks,

Al