edratroubleshooting

SeeAlso: EDRAWiki

Summary: Helps answer questions on problems that might occur

Downloading (Workspace)

Releases link is not visible
You have to be approved for the workspace first. Click on the "Apply to Join Workspace" link. Once you have been approved, then you can access the Releases section.

If you have been approved but still cannot see the Releases link, then make sure you are signed into GotDotNet. Also, try deleting your cookies for the passport.net, passport.com and gotdotnet.com domains (or just delete all cookies using Tools/Internet Options/Delete Cookies).

Installation (MSI)

"Invalid Syntax" error, followed by installation rollback
Make sure IIS is installed on the machine you are installing EDRA on. The MSI creates a few web folders so that VS.NET can open the solution without giving errors about web folders not existing for the web service projects.

"Unknown Name" error, followed by installation rollback
One of the prerequisites for EDRA is not installed. Check for MSMQ, SQL Server, .NET 1.1, EIF.

Setup (wsf script)

MessageQueueInstaller.exe - Application Error after "Creating Message Queueing Interface transport queues..." message
Two possible problems are ""SP1"" for .NET Framework 1.1 isn't installed or mofcomp cannot be found on the path.

"SQL Server does not exist or access denied."
Make sure the tcp/ip network protocol for MSDE or SQL Server is enabled.

Wizards

"Service already exists" error
Usually you see this error when there is already a pipeline for a given service. Go to ServiceReferenceArchitecture.config and check the pipelines section.

Calling ""WebService"" interface transport

"Client found response content of type '', but expected 'text/xml'"
Some things to check in case of this error:
- Make sure your XML namespaces for the message definition XSD's/classes are in sync with the EDRA web service interface declaration. For example, if the message definition request/response are defined with the namespace of http://yourcompany.com/SampleRequest and http://yourcompany.com/SampleResponse, then make sure your webmethod declaration contains the same namespaces:
Public Function SomeAction(<XmlElement("SampleRequest",Namespace:="http://yourcompany.com/SampleRequest")> ""ByVal"" request As ""MessageDefinitions.SampleRequest"") As <XmlElement("SampleResponse",Namespace:="http://yourcompany.com/SampleResponse")> ""SampleResponse""

If this change is made, do not forget to update the client web references to pick up the new namespace definitions on the web service action method.

- Try opening the ASMX page directly in Internet Explorer to see if any issues are reported
- Make sure you are running EDRA v1.0b or v1.1. ""SP1"" of .NET 1.1 introduced a minor backward compatibility break that required a workaround in the code to be made from the original v1.0.
- Make sure the aspnet ID has access to the 'Solution Items' folder. Grant Read & Execute, and Read to it, then restart IIS.

Calling ""MSMQ"" interface transport

"Member Comparer was not found."

This error has been experienced when both of the following two conditions exist:

1. You are implementing an MSMQ Interface to your service but dispatching to a Web Service for the Implementation.
2. Your asp.net is configured to use a framework version other than 1.1.

To fix the problem, reconfigure asp.net to use version 1.1 by following these steps:
1. Open the Computer Management console (right-click on My Computer and select Manage).
2. Under 'Services and Applications', expand 'Internet Information Services' and locate 'Default Web Site'.
3. Right click on 'Default Web Site' and select Properties.
4. In the properties window, select the ASP.NET tab.
5. Select '1.1.4322.0' in the ASP.NET Version dropdown.
6. Click 'Ok' and retest. Your app should now be working.

DuplicateMessage Handler Null Reference Exception

Implementing the Duplicate Message Handler and getting an error?

The EDAF documentation, chapter 11 (Handlers), DuplicateMessage topic shows the following configuration block which is to be inserted in TemplateServices.config in the before and after sections:

<handler handlerName="DuplicateHandling">

		    [<duplicateHandlerSettings] lifeTime="60" messageHandlingOption="Cache"/>

</handler>

However, the ServicesReferenceArchitecture.config file by default calls this handler "DuplicateMessage", not "DuplicateHandling". Change the config section in TemplateServices.config (both before and after) to the following:

<handler handlerName="DuplicateMessage">

		    [<duplicateHandlerSettings] lifeTime="60" messageHandlingOption="Cache"/>

</handler>

SeeAlso: EDRAWiki