Problem when opening the sql server express in visual web developmer express edition

hi

i download free starter kit timetraker application( i downloaded both Visual web devaloper and sql server express from the Internet)

when i tried to run it it is showing the following error

An error has occurred while establishing a connection tothe server. When connecting to SQL Server 2005, this failure may becaused by the fact that under the default settings SQL Server does notallow remote connections. (provider: Shared Memory Provider, error: 40- Could not open a connection to SQL Server)

plz give me the solution above error

thanks in advance

vittal

The simplest thing have u checked the Sql Server Service is started or not... This is the simplest error which occur... 50% time

Satya

|||

Type inetmgr on run.
select the verual directory -> right click and select property -> go to ASP.NET tab -> click Edit Configuration

and then Edit the connection string accordingly.

Problem when Connection is not available

Hello!

I have problem when opening a package or running it through SQL Server Agent and the Server in the Connection is not available. (I have tried with (M) SSIS > Work Offline, it helps opening it, but not running it).

The package has a Foreach Loop Container that loop through several Companies. Each Company have different Connection.

It exist one ODBC and one OLEDB connection. They have the Expression “ConnectionString” set to an variable (@.[User::varODBCConnectionString]/ @.[User::varOLEDBConnectionString]).

The Foreach Loop Container property ForceExectionResult is set to Completion. This results in that if one company is not available when trying to access it, the loop will continue with the next Company.

But the variables have a value from the beginning. If the server in the variables is not available, it is not possible to open the package or execute it through SQL Server Agent.

I tried to set the Property DelayValidation to True on the Connections, but this did not help.

Dose anyone have any ide how get around this problem?

Best regards,

Tina

Hi Tina,

You need to set DelayValidation=TRUE on the tasks that use those connection managers, not on the connection managers themselves.

Regards

Jamie

|||

Hello Jamie!

Thank you very much, it works now, bouth SQL Server Agent and in SSIS. (I also need to set Delay Validation = TRUE for att least the ODBC connection.).

Best regards,

Tina