This project is read-only.

cannot connect SQL Server

Topics: User Forum
Jun 18, 2012 at 9:39 AM

i follow this steps

http://keystrokeesbnet.codeplex.com/wikipage?title=%5bESB.NET%20installation%5d&referringTitle=Installation

but i can create the database

so. when i login the esb management . System.Data.SqlClient.SqlException will appear

Jun 18, 2012 at 12:59 PM

Hi Sen,

Please run through the Post setup tasks at:

http://keystrokeesbnet.codeplex.com/wikipage?title=%5bPost%20setup%20tasks%20-%20First%20time%20install%5d&referringTitle=Installation

Cheers, Minas

Jun 19, 2012 at 2:53 AM

thanks,

but i had follow the Post setup tasks,and i found that the esb.net use "esb" for sql instance name,should i build the  sql instance by myself?

Jun 19, 2012 at 10:40 AM

Hi Sen,

No need to change the SQL Server instancing/DB.

Just modify the DB connection configuration in this file.

"C:\ESB\Dev\Source\ESB\Base\Configuration\ASP.NET\web.config"

Cheers, Minas

ps. During the installation procedure, there's a step to enter the SQL server instance name.

Jun 20, 2012 at 4:51 AM

Thanks for your replies.

i can login the esb management successful.

but i found another question.

i create a Service, and i test it.

it will has respone xml

but when i  click the “View log for request” link, no row in request list.

and then,i click

Core System Test
 

frist row was fail.

and click the “View log for request” link, no row in request list too.

Jun 20, 2012 at 5:30 PM
Edited Jun 20, 2012 at 5:38 PM

Hi Sen,

Check the logger settings.

Instrumentation and Logging Management --> Log and System Entry Point Settings --> Wcf Transport --> Logging levels

- enable all logging to start with (by clicking Set all log levels)

Instrumentation and Logging Management --> Log and System Entry Point Settings --> Wcf Transport --> Log Device & System Entry Point Settings

- Server Log Device Settings - enable: ESB.Core.Loggers.MsmqLogger

- Server Entry Point Settings - enable: MSMQSystemEntryPoint

Also,

In case the async logger hasn't started automatically... you can start it manually by going to:

 Instrumentation and Logging Management --> SQL Server Log --> Start Async Logger

and click Start Async Logger

 

Cheers, Minas