Hi Paul,

I think you need to try and find out some more information first as it could be any number of issues causing this.

When you want more information about HTTP errors like the infamous "500 - Internal Server Error":

Please check and change the following settings in order to get more helpful error details.

1. Firstly check to make sure "Show friendly HTTP error messages" is UN-TICKED by going to Internet Explorers "Internet Settings" and clicking on the "Advanced" tab. Scroll down and make sure that "Show friendly HTTP error messages" is un-ticked. Click on "OK" button to commit changes

2. Next we need to change some settings within IIS on the webserver. Open up IIS Manager, select the "CRM" webserver and the double click on the "ASP" icon

3. Make sure that "Send Errors To Browser" is set to "True" and then click on "Apply"

4. Go back to the main website by clicking on the "CRM" website and double click on "Error Pages"

5. Now click on "Edit Feature Settings…"

6. Make sure that "Detailed errors" is selected and then click on "OK" to commit the changes

7. Try and re-create the error in your browser which should now display more information about the error

This should give you more to go.

Kind Regards

Julian

Hi Paul,

I failed to mention that there should also be extra information in your ewaresystem.log.

It may be worth turning logging up to maximum first though.

Kind Regards

Julian

Thanks, Julian, for the detailed reply. I followed your instructions and was able to get the error details in the browser. However, I'm none the wiser for it.

>Internal Application Error Access violation at address 1A14DB3C in module 'eware.dll'. Read of address 00000000 /webservices/webservice.wsdl<

I have a fresh install that is working, so I think I'll recreate the schema changes and test after each one...

This has been resolved so I wanted to include the resolution details here. Thanks, Julian for your help!

The ewaresystem log (log level set to 5) captured the exception, indicating two 'IsValidXMLField' errors.

I looked back at the fields added to the two new entities and found 2 fields that did not have a prefix (xxxx_). I remember reading that this can cause problems with web services - sure enough. These were the 'Company Id' and 'User Id' fields that were added using the 'Create Table' feature. I must have not included the prefix at that step. Repeating the process correctly in another database corrected the problem and the wsdl file generates without errors.

A side issue with the malformed company and user fields is that I couldn't delete them because the 'Delete' button is not available for those fields. I got the Delete button back by editing custom_edits.colp_candelete, but clicking Delete raised an error about many view dependencies which have nothing to do with the new entity. I suspect the fields being named 'CompanyId' and 'UserId' triggered armageddon in the code. I suspect there's a way to delete the fields cleanly, which would need to be done if this were a live system.

You will also get this error if your fields 'start' with a number i.e. comp_2ndfield.

Check your database table "custom_table" there might be issue regards [bord_WebServiceTable] that cause the schema not form properly. Try to set them as NULL, you should be able to get the schema up again.