webservice example generates internal error page

[andre.buurman@carya]

When trying to get the shipped webservice example "address book" to work I constanly get a page from the LV webserver "Access Error: 500 -- Internal Server Error". it is however able to display the addcontacts html page, but that in trn is not able to post the entered data, without resulting in the same error.

What could be the problem?

[ninlmartijn]

Hello Andre,

thank you for your post on our forum. I tried to reproduce your problem and got the same error. I used Labview 8.6, did you use a different version? I will try to reproduce it with another version where this example is included.

If I try to open the pages from the project explorer (so from C:\Program Files\National Instruments\LabVIEW 8.6\examples\comm\webservices\address book\data\new_contact.html ) I've got a security warning (with both pages). I tried to switch of all internet security but the warning wouldn't disappear. Maybe I'm looking to the wrong direction; but I'm looking to get rid of this warning.

Best regards,

[andre.buurman@carya]

Martijn, Restfull webservice functionality is introduced in LV 8.6.

[ninlmartijn]

Hello Andre,

thank you for your response. Does it give the same security warning when just opening the html file? I want to look how to resolve this, but if it is not giving the warning with you, then I'm going into the wrong direction. So please try to open addresses.xml and newcontact.html from the virtual data folder.

Best regards,

[andre.buurman@carya]

The files addresses.xml and newcontact.html pose no problem they are displayed as expected. The link "http://localhost/address/find/hoit" and the "Submit" button on newcontact.html display "Access Error: 500 -- Internal Server Error".

[ninlmartijn]

Hello Andre,

I did try the example at home; and there were no browser warnings. Before my first reply I looked up if this was a known problem. I couldn't find anything about this. Just before I wanted to forward this problem to a colleague I discovered a Corrective Action Request (CAR# 125724), which described exactly our problem. I'm sorry to say I can't solve your problem at this moment.

At this moment the R&D group is working to solve the problem; the target version will be the next release. You will find more information in the next release notes under the CAR ID.

Best regards,