Problem Getting to ESB Management Console

Topics: Developer Forum, Project Management Forum, User Forum
Jul 21, 2008 at 3:58 AM

Hello,

First time user and just started to use this product. I am not a strong technical person.  I've downloaded ESBDeploy_6.1.21.0.zip and ran the the setup_first.cmd file. I am running this on Windows 2003.  When I go to http://localhost/ESB/Source/Management/default.aspx I get the following error:



<title>Configuration Error</title> <style> body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon } pre {font-family:"Lucida Console";font-size: .9em} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; } </style>

Server Error in '/ESB/Source/Management' Application.

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Unrecognized configuration section 'connectionStrings'

Source Error:

Line 18: 		Adaptor specific configuration data should ideally be put in the Pipeline config file.
Line 19: 	-->
Line 20: 	<connectionStrings>
Line 21: 		<add name="ESBLogConnectionString" connectionString="Data Source=localhost\sqldev;Initial Catalog=ESBLog;Integrated Security=True;" providerName="System.Data.SqlClient"/>
Line 22: 	</connectionStrings>

Source File: C:\downloads\Keystroke ESB\ESBDeploy_6.1.21.0\Source\ESB\Base\Solutions\Main\Management\ESB.Management.Portal\web.config    Line: 20


Version Information: Microsoft .NET Framework Version:1.1.4322.2407; ASP.NET Version:1.1.4322.2407



I am not certain why I would get this right after doing a fresh install. Any thoughts? Thanks in advanced. By the way, my web.config looks like this:

<?xml version="1.0"?>
<configuration>
    <configSections>
        <!-- Configuration -->
        <section name="applicationConfigurationManagement" type="Microsoft.ApplicationBlocks.ConfigurationManagement.ConfigurationManagerSectionHandler,Microsoft.ApplicationBlocks.ConfigurationManagement, Culture=neutral,PublicKeyToken=9335555c83caba24"/>
        <section name="ESB.Core.Envelopes" type="ESB.Core.XMLSchemaClasses.CustomSectionHandler,ESB.Core.XMLSchemaClasses"/>
        <section name="ESB.Core.Services.Server" type="ESB.Core.Services.Server.CustomSectionHandler,ESB.Core.Services.Server, Culture=neutral,PublicKeyToken=9335555c83caba24"/>
        <!--<section name="ESB.Core.Services.Server.Wse"
             type="ESB.Core.Services.Server.CustomSectionHandler,ESB.Core.Services.Server, Culture=neutral,PublicKeyToken=9335555c83caba24" />-->
        <section name="ESB.Core.Services" type="ESB.Core.Services.CustomSectionHandler,ESB.Core.Services, Culture=neutral,PublicKeyToken=9335555c83caba24"/>
        <section name="ESB.Core.Pipeline" type="ESB.Core.Pipeline.CustomSectionHandler,ESB.Core.Pipeline, Culture=neutral,PublicKeyToken=9335555c83caba24"/>
        <!-- Exceptions -->
        <section name="exceptionManagement" type="Microsoft.ApplicationBlocks.ExceptionManagement.ExceptionManagerSectionHandler,Microsoft.ApplicationBlocks.ExceptionManagement"/>
        <section name="microsoft.web.services3" type="Microsoft.Web.Services3.Configuration.WebServicesConfiguration, Microsoft.Web.Services3, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
        <!--<section name="MicrosoftWebControls" type="System.Configuration.NameValueSectionHandler,System,Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>-->
    </configSections>
    <!-- The config file below holds config data for ESB core assemblies that cannot use the Configuration Management Data Block.
        Adaptor specific configuration data should ideally be put in the Pipeline config file.
    -->
    <connectionStrings>
        <add name="ESBLogConnectionString" connectionString="Data Source=localhost\sqldev;Initial Catalog=ESBLog;Integrated Security=True;" providerName="System.Data.SqlClient"/>
    </connectionStrings>
    <appSettings>
  <add key="ESBPiplineConfigurationPath" value="Base\Solutions\Main\Configuration\XMLConfigFiles\ServicePipeline.config" />
  <add key="ESBDocumentTransformConfigurationPath" value="Base\Solutions\Main\Configuration\XMLConfigFiles\DocumentTransformPipeline.config" />
  <add key="MsSqlLoggerConnectionString" value="Data Source=localhost\sqldev; Integrated Security=SSPI; Initial Catalog=ESBLog;" />
  <add key="MSMQLoggerQueuePathName_Detail" value=".\private$\esblogq" />
  <add key="AttachmentsSendPath" value="Attachments\Send" />
  <add key="AttachmentsReceivePath" value="Attachments\Receive" />
  <add key="SoapRpcTimeout" value="100000" />
  <add key="SoapDocumentTimeout" value="100000" />
  <add key="HttpTimeout" value="100000" />
  <add key="SystemTestPageUseLocalServer" value="1" />
  <add key="DestinationServerURL" value="http://localhost/ESB/Source/CoreInternetTransportAdaptors/Wcf/ESBSoapXmlDocTransport.svc/Default" />
  <add key="ESBSoapXmlDocumentUrlkey" value="http://192.168.1.101/ESB/Source/CoreInternetTransportAdaptors/Wse3/ESBSoapXmlDocTransport.asmx" />
  <add key="Transport" value="SOAP-WSE3" />
  <add key="ESB.ESBEnvelope.ValidationOnSerialize" value="0" />
  <add key="ESB.ESBEnvelope.ValidationOnDeserialize" value="0" />
  <add key="ESB.ESBEnvelope.IgnoreInputSchemaValidationErrors"
   value="0" />
  <add key="ESB.ESBEnvelope.XSDFilePath" value="Base\Solutions\Main\XMLSchemas\ESB.Core.XMLSchemas\ESBEnvelope\1.0.5" />
  <add key="ESB.ProxyServer.Enabled" value="1" />
  <add key="ESB.ProxyServer.IPAddress" value="20.139.226.18" />
  <add key="ESB.ProxyServer.Port" value="8080" />
  <add key="ESB.ProxyServer.Username" value="put your Keystroke Proxy username here" />
  <add key="ESB.ProxyServer.Password" value="put your Keystroke Proxy password here" />
  <add key="RequestListFilePath" value="\Authenticated\Testing\SystemTest.config" />
  <add key="ESB.ClientLogLevel" value="7" />
  <add key="ESB.ClientPolicy" value="" />
  <add key="ESB.Client.WcfClientEndPointName" value="ESBSoapXmlDocTransportSoap" />
 </appSettings>
    <system.web>
        <!--  DYNAMIC DEBUG COMPILATION
          Set compilation debug="true" to insert debugging symbols (.pdb information)
          into the compiled page. Because this creates a larger file that executes
          more slowly, you should set this value to true only when debugging and to
          false at all other times. For more information, refer to the documentation about
          debugging ASP.NET files.
    -->
        <compilation debug="true" defaultLanguage="vb">
            <assemblies>
                <add assembly="System.Messaging, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                <add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                <add assembly="System.Security, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                <add assembly="System.Configuration.Install, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                <add assembly="System.ServiceProcess, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                <add assembly="System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
                <add assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
                <add assembly="System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
                <add assembly="System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                <add assembly="System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                <add assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                <add assembly="System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                <add assembly="Microsoft.Web.Services3, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
                <add assembly="System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                <add assembly="System.Transactions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
                <add assembly="System.Web.RegularExpressions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                <add assembly="System.IdentityModel.Selectors, Version=3.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
                <add assembly="System.Runtime.Remoting, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
                <add assembly="System.Workflow.ComponentModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
                <add assembly="System.Workflow.Activities, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
                <add assembly="System.Workflow.Runtime, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
                <add assembly="System.Web, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                <add assembly="System, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
                <add assembly="System.Design, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                <add assembly="System.Drawing, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                <add assembly="System.Xml, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
                <add assembly="System.Windows.Forms, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
            </assemblies>
            <buildProviders>
                <add extension=".rdlc" type="Microsoft.Reporting.RdlBuildProvider, Microsoft.ReportViewer.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            </buildProviders>
        </compilation>
        <authentication mode="Forms">
            <forms loginUrl="Logon/LoginPage.aspx">
                <credentials passwordFormat="Clear">
                </credentials>
            </forms>
        </authentication>
        <!--  CUSTOM ERROR MESSAGES
          Set customErrors mode="On" or "RemoteOnly" to enable custom error messages, "Off" to disable.
          Add <error> tags for each of the errors you want to handle.
    -->
        <customErrors mode="Off"/>
        <!--  AUTHENTICATION
          This section sets the authentication policies of the application. Possible modes are "Windows",
          "Forms", "Passport" and "None"
    -->
        <!--  AUTHORIZATION
          This section sets the authorization policies of the application. You can allow or deny access
          to application resources by user or role. Wildcards: "*" mean everyone, "?" means anonymous
          (unauthenticated) users.
    -->
        <authorization>
            <allow users="*"/>
            <!-- Allow all users -->
            <!--  <allow     users="[comma separated list of users]"
                             roles="[comma separated list of roles]"/>
                  <deny      users="[comma separated list of users]"
                             roles="[comma separated list of roles]"/>
            -->
        </authorization>
        <!--  APPLICATION-LEVEL TRACE LOGGING
          Application-level tracing enables trace log output for every page within an application.
          Set trace enabled="true" to enable application trace logging.  If pageOutput="true", the
          trace information will be displayed at the bottom of each page.  Otherwise, you can view the
          application trace log by browsing the "trace.axd" page from your web application
          root.
    -->
        <trace enabled="true" requestLimit="100" pageOutput="false" traceMode="SortByTime" localOnly="true"/>
        <!--  SESSION STATE SETTINGS
          By default ASP.NET uses cookies to identify which requests belong to a particular session.
          If cookies are not available, a session can be tracked by adding a session identifier to the URL.
          To disable cookies, set sessionState cookieless="true".
    -->
        <sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa;password=" cookieless="false" timeout="300"/>
        <!--  GLOBALIZATION
          This section sets the globalization settings of the application.
    -->
        <globalization requestEncoding="utf-8" responseEncoding="utf-8"/>
        <pages validateRequest="false">
            <namespaces>
                <add namespace="Microsoft.VisualBasic"/>
                <add namespace="System.Data"/>
                <add namespace="System.Drawing"/>
                <add namespace="ESB.Core.Util"/>
                <add namespace="ESB.Core.Services.Logger"/>
                <add namespace="ESB.Core.Interfaces.Logging"/>
                <add namespace="Microsoft.ApplicationBlocks.ExceptionManagement"/>
            </namespaces>
        </pages>
        <webServices>
            <soapExtensionTypes>
            </soapExtensionTypes>
            <soapServerProtocolFactory type="Microsoft.Web.Services3.WseProtocolFactory, Microsoft.Web.Services3, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
            <soapExtensionImporterTypes>
                <add type="Microsoft.Web.Services3.Description.WseExtensionImporter, Microsoft.Web.Services3, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
            </soapExtensionImporterTypes>
        </webServices>
        <!-- <trust level="WSS_Minimal" originUrl="" processRequestInApplicationTrust="false"/> -WSS CRAP... -->
        <httpRuntime maxRequestLength="2097151"></httpRuntime>
    </system.web>
    <applicationConfigurationManagement defaultSection="ESB.Core.Services.Server">
        <configSection name="ESB.Core.Envelopes">
            <configCache enabled="true" refresh="* * * * *"/>
            <configProvider assembly="Microsoft.ApplicationBlocks.ConfigurationManagement,Culture=neutral,PublicKeyToken=9335555c83caba24" type="Microsoft.ApplicationBlocks.ConfigurationManagement.Storage.XmlFileStorage" signed="false" refreshOnChange="true" encrypted="false" path="..\..\Configuration\XMLConfigFiles\ESB.Core.Envelopes.config"/>
        </configSection>
        <configSection name="ESB.Core.Services">
            <configCache enabled="true" refresh="* * * * *"/>
            <configProvider assembly="Microsoft.ApplicationBlocks.ConfigurationManagement,Culture=neutral,PublicKeyToken=9335555c83caba24" type="Microsoft.ApplicationBlocks.ConfigurationManagement.Storage.XmlFileStorage" signed="false" refreshOnChange="true" encrypted="false" path="..\..\Configuration\XMLConfigFiles\ESB.Core.Services.Wcf.config"/>
        </configSection>
        <!--<configSection name="ESB.Core.Services.Server.Wse">
      <configCache enabled="true"
                   refresh="* * * * *" />
      <configProvider assembly="Microsoft.ApplicationBlocks.ConfigurationManagement,Culture=neutral,PublicKeyToken=9335555c83caba24"
                      type="Microsoft.ApplicationBlocks.ConfigurationManagement.Storage.XmlFileStorage"
                      signed="false"
                      refreshOnChange="true"
                      encrypted="false"
                      path="..\..\Configuration\XMLConfigFiles\ESB.Core.Services.Server.config" />
    </configSection>-->
        <configSection name="ESB.Core.Services.Server">
            <configCache enabled="true" refresh="* * * * *"/>
            <configProvider assembly="Microsoft.ApplicationBlocks.ConfigurationManagement,Culture=neutral,PublicKeyToken=9335555c83caba24" type="Microsoft.ApplicationBlocks.ConfigurationManagement.Storage.XmlFileStorage" signed="false" refreshOnChange="true" encrypted="false" path="..\..\Configuration\XMLConfigFiles\ESB.Core.Services.Server.Wcf.config"/>
        </configSection>
        <configSection name="ESB.Core.Pipeline">
            <configCache enabled="true" refresh="* * * * *"/>
            <configProvider assembly="Microsoft.ApplicationBlocks.ConfigurationManagement,Culture=neutral,PublicKeyToken=9335555c83caba24" type="Microsoft.ApplicationBlocks.ConfigurationManagement.Storage.XmlFileStorage" signed="false" refreshOnChange="true" encrypted="false" path="..\..\Configuration\XMLConfigFiles\ServicePipeline.config"/>
        </configSection>
    </applicationConfigurationManagement>
    <!--<MicrosoftWebControls>
        <add key="CommonFiles" value="/webctrl_client/1_0/"/>
    </MicrosoftWebControls>-->
    <exceptionManagement mode="on">
        <publisher assembly="Microsoft.ApplicationBlocks.ExceptionManagement" type="Microsoft.ApplicationBlocks.ExceptionManagement.DefaultPublisher" logname="ESB.NET Client" applicationname="ESB.NET Client"/>
    </exceptionManagement>
    <microsoft.web.services3>
        <diagnostics>
            <detailedErrors enabled="false"/>
            <trace enabled="false" input="InputTrace.webinfo" output="OutputTrace.webinfo"/>
        </diagnostics>
        <!--<filters>
            <output>
                <add type="WSETracingFilter.WSEOutputFilter,WSETracingFilter, Version=1.2.0.0, Culture=Neutral, PublicKeyToken=1c1f2f7177e1ff79" />
                <add type="WSEReorderPipelineFilter.WSETracingReorderOutputFilter, WSETracingReorderPipelineFilter, Version=1.2.0.0, Culture=Neutral, PublicKeyToken=1c1f2f7177e1ff79" />
            </output>
            <input>
                <add type="WSETracingFilter.WSEInputFilter,WSETracingFilter, Version=1.2.0.0, Culture=Neutral, PublicKeyToken=1c1f2f7177e1ff79" />
                <add type="WSEReorderPipelineFilter.WSETracingReorderInputFilter, WSETracingReorderPipelineFilter, Version=1.2.0.0, Culture=Neutral, PublicKeyToken=1c1f2f7177e1ff79" />
            </input>
        </filters>
        -->
        <tokenIssuer>
            <ttlInSeconds value="86400">
            </ttlInSeconds>
        </tokenIssuer>
        <messaging>
            <mtom clientMode="Off" serverMode="always"/>
            <!--<mtom clientMode="On" serverMode="always" />-->
        </messaging>
        <policy fileName="wse3policyCache.config"/>
    </microsoft.web.services3>
    <!-- WCF Settings -->
    <system.serviceModel>
        <behaviors/>
        <diagnostics wmiProviderEnabled="false" performanceCounters="Off">
            <messageLogging logEntireMessage="false" logMalformedMessages="false" logMessagesAtServiceLevel="false" logMessagesAtTransportLevel="false"/>
        </diagnostics>
        <serviceHostingEnvironment aspNetCompatibilityEnabled="true"/>
        <bindings>
            <basicHttpBinding>
                <binding name="ESBSoapXmlDocTransportSoapBindingConfig" closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00" allowCookies="false" bypassProxyOnLocal="true" hostNameComparisonMode="StrongWildcard" maxBufferSize="100000000" maxBufferPoolSize="100000000" maxReceivedMessageSize="100000000" messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered" useDefaultWebProxy="false">
                    <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" maxBytesPerRead="4096" maxNameTableCharCount="16384"/>
                    <security mode="None">
                        <transport clientCredentialType="None" proxyCredentialType="None" realm=""/>
                        <message clientCredentialType="UserName" algorithmSuite="Default"/>
                    </security>
                </binding>
            </basicHttpBinding>
            <wsHttpBinding>
                <binding name="ESBSoapXmlDocTransportSoapRMBindingConfig">
                    <reliableSession ordered="false" enabled="true"/>
                </binding>
            </wsHttpBinding>
        </bindings>
        <client>
            <endpoint address="http://localhost/ESB/Source/CoreInternetTransportAdaptors/Wcf/ESBSoapXmlDocTransport.svc/Default" binding="basicHttpBinding" bindingConfiguration="ESBSoapXmlDocTransportSoapBindingConfig" contract="ESBSoapXmlDocTransportWcfProxyClasses.IProcessMsg" name="ESBSoapXmlDocTransportSoap"/>
            <endpoint address="http://localhost/ESB/Source/CoreInternetTransportAdaptors/Wcf/ESBSoapXmlDocTransportRM.svc/Reliable" binding="wsHttpBinding" bindingConfiguration="ESBSoapXmlDocTransportSoapRMBindingConfig" contract="ESBSoapXmlDocTransportWcfProxyClasses.IProcessMsg" name="ESBSoapXmlDocTransportSoapRM"/>
        </client>
        <!--<client>
      <endpoint address="http://localhost/ESB/Source/CoreInternetTransportAdaptors/Wcf/ESBSoapXmlDocTransport.svc" binding="basicHttpBinding" bindingConfiguration="ESBSoapXmlDocTransportSoapBindingConfig" contract="ESBSoapXmlDocTransportWcfProxyClasses.IProcessMsg" name="ESBSoapXmlDocTransportSoap"/>
      <endpoint address="http://localhost/ESB/Source/CoreInternetTransportAdaptors/Wcf/ESBSoapXmlDocTransportRM.svc" binding="wsHttpBinding" bindingConfiguration="ESBSoapXmlDocTransportSoapRMBindingConfig" contract="ESBSoapXmlDocTransportWcfProxyClasses.IProcessMsg" name="ESBSoapXmlDocTransportSoapRM"/>
    </client>-->
    </system.serviceModel>
</configuration>

Coordinator
Jul 21, 2008 at 11:10 AM

Hi,

For basic installation troubleshooting, please review the 
    Keystroke ESB.NET Services - Installation Guide
that's part of the downloads.

In your case, looks like you don't have the Microsoft.NET Framework related pre-requisites. You need the .NET Frameworks 2.0 and 3.5.

It does NOT look like the problem is related to the SQL Server instance name.
...which incidentally, by default, this is set to:
         localhost\sqldev
If your SQL Server instance name differs, you will need to change the following 3 config files: 

  1. Source\ESB\Base\Solutions\Main\Management\ESB.Management.Portal\web.config
  2. Source\ESB\Base\Solutions\Main\TransportAdaptors\Esb.Core.Adaptors.Transport.Internet.Receive.Wcf\web.config
  3. Source\ESB\Base\Solutions\Main\TransportAdaptors\ESB.Core.Adaptors.Transport.Internet.Receive.WSE3\Web.config

You may wish to take the latest build - 6.1.23.0 - as the setup script has some minor fixes in this area. The patches apply to scenarios where the default SQL directory does not exist.


If you do not wish to use any of the SQL Server functionality (predominately logging at this stage), then you can remove it by making changes to the following config files
    C:\ESB\Dev\Source\ESB\Base\Solutions\Main\Configuration\XMLConfigFiles\ESB.Core.Services.Server.Wcf.config
    C:\ESB\Dev\Source\ESB\Base\Solutions\Main\Configuration\XMLConfigFiles\ESB.Core.Services.Server.config

Make the changes in BOLD to disable all SQL Server activity.
          <Logger>
            <ObjectName>ESB.Core.Loggers.MsSqlLogger</ObjectName>
            <AssemblyPath>Base\Solutions\Main\Logging\ESB.Core.Loggers\bin\ESB.Core.Loggers.dll</AssemblyPath>
            <Enabled>false</Enabled>
          </Logger>

        <SystemEntryPoint name="MSSqlSystemEntryPoint" enabled="false">
          <ObjectName>ESB.Core.Services.Server.MSSQLSystemEntryPoint</ObjectName>
          <AssemblyPath>ESB.Core.Services.Server</AssemblyPath>
          <Custom>
            <ParamName>LogRequestResponse</ParamName>
            <ParamValue>true</ParamValue>
          </Custom>
        </SystemEntryPoint>

Good luck.

Cheers
Minas

Jul 21, 2008 at 4:20 PM
Hi Minas,

Thanks for your reply.  I did install all the pre-requisites.  Just to be safe I reverted to my original image, I am using VMware, and installed MS NET Framework 3.5. I downloaded the lastest version but get the same
error message when trying to access the console.

Does it matter what version of SQL? I have SQL 2005 loaded on the server.
Coordinator
Jul 21, 2008 at 7:39 PM
SQL Server 2005 is fine. That's what most use with ESB.NET 6.x. I've not actually tried with 2008 yet :(.

The error doesn't look like an ESB.NET one. More of an ASP.NET type error.
Do you know if ASP.NET 2.0 is set at the version of IIS for that website (or Virtual Directory?).
Go into the settings for the website, and ensure the ASP.NET version is set to 2.0 (not 1.1).

Also, try to navigate to the
   http://localhost/ESB/Test/CoreInternetTransportAdaptors/Wcf/ESBSoapXmlDocTransport.svc
URL. This does not have the ConnectionStrings element, and MAY help in further troubleshooting if the above is not the cause.

Also, in terms of troubelshooting, you may wish to try to deploy another ASP.NET 2.0 application to see if you have the same problem. Aim is to determine whether the base pre-requisites are installed/configured correctly.

The aspnet_regiis.exe utility may be of help if it's an ASP.NET configuration related issue.

Good Luck.
Cheers
Minas

Jul 22, 2008 at 3:13 PM
Hi Minas,

It was the ASP.NET version on IIS. I switched it to 2.0 and worked. 

FYI, the URL you provided (http://localhost/ESB/Test/CoreInternetTransportAdaptors/Wcf/ESBSoapXmlDocTransport.svc) didn't come up though. Not sure why.

Thanks for your help.
Coordinator
Jul 22, 2008 at 7:47 PM
Great!
RE:
http://localhost/ESB/Test/CoreInternetTransportAdaptors/Wcf/ESBSoapXmlDocTransport.svc


OOps! Wrong Instance Name!
Sorry mate, should have been:

http://localhost/ESB/Source/CoreInternetTransportAdaptors/Wcf/ESBSoapXmlDocTransport.svc

The default instance name is "Source".
You can install multiple instances concurrently. Obviously I copied a URL from another instance without checking... Sorry about that. Once you put in the right instance name though, you should get something like the below (standard WCF service page...):

Cheers
Minas

--------------------------------------------------------------------------------------------------



ESBSoapXmlDocTransport Service


You have created a service.

To test this service, you will need to create a client and use it to call the service. You can do this using the svcutil.exe tool from the command line with the following syntax:


svcutil.exe http://pamela.home.casious.com.au/ESB/Source/CoreInternetTransportAdaptors/Wcf/ESBSoapXmlDocTransport.svc?wsdl

 

This will generate a configuration file and a code file that contains the client class. Add the two files to your client application and use the generated client class to call the Service. For example:

C#

class Test{
 static void Main()
    {
        ProcessMsgClient client = new ProcessMsgClient();

 // Use the 'client' variable to call operations on the service. // Always close the client.        client.Close();
    }
}

Visual Basic

Class Test Shared Sub Main()
 Dim client As ProcessMsgClient = New ProcessMsgClient()
 ' Use the 'client' variable to call operations on the service. ' Always close the client.        client.Close()
 End SubEnd Class