Robert, since the delivery address is being cut off in the SPS output, would you please verify the entry in your database. We record the subscriptions in a table called
EventSubscription. In your case, you should have 2 records - only 1 of which is SOAP related. Let's make sure that address is what we think it ought to be.
Also, while you're at it, let's also be sure your WCF service is active by attempting to visit
http://localhost/TGNotificationServiceL ... ervice.svc from a web browser that is on the same machine as your IIS installation.
There may be one other culprit. If that ASMX address was ever a registered subscriber to the OrderChanged event while you were developing/testing, and the event fired on our system, we would have queued up the notification in another table called
EventNotification. Perhaps that failed entry is still sitting in there being retried every time the event fires, creating the Error Log entry each time. Look in that table, too - essentially we "copy over" the subscription information into the queuing table as a new record at the time the event fired (so there will be a DeliveryAddress value to look at).
Mark