Web Service Import Error - Can't Create Project Library

[ajckson]

Hello,

I'm haiving an issue importing a particular .NET web service using the import wizard.  I'm running .NET 2.0 framework and LV8.2.  I have followed this tutorial and successfully got a few simple services working.  I can successfully import an use simple web services like this one with no issues, but when I attempt to import a local web service I keep experienceing the same error at the end of the import, the error is:

The following errors/warnings occurred when generating the local proxy dll and VI wrappers for this web service.

Can't Create Project Library.
Project Library Generation Failed.
Possible Reasons:
1) The imported project library has a conflicting name with a project library already in memory.
2) The imported VIs have conflicting names with VIs already in memory.
Close the project library and VIs and reimport the Web Service.
ionService.lvlib

I seriously doubt that the error is actually caused by 1 or 2, I think this is just the default message for some other error.  I have cleaned all previous failed projects from the userlibs and opened and closed the program, restarted etc...  I have also tried this and got the same error with another machine running .NET 1.1 and LV8.2, same error.

The service's WSDL page seems to be working correctly, LV sees the availble functions and lists them correctly for import, it just always fails when creating the DLL wrappers.

I have included the WDSL XML file for reference.

Anyone have any ideas for fixing this?

Thanks,
Adam




Message Edited by ajckson on 05-20-2008 04:27 PM

[Aashish_M]

Hi Adam,

Some of the functions in your project library may have the same names as some of the inbuilt functions in LabVIEW or any loaded functions in the memory.

Try closing down all other programs and see if it works.

What are the names of the functions you are using?

You may have to rename them to remove the naming conflict, but you did mention that you don’t think that it’s because of one of those reflected conflicts!!

SubVIs being generated may have the same name as some LabVIEW inbuilt functions which may be causing the problem.

Could you please provide the header file to see the names of the functions?

Hopefully this helps!!