Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > Visual Studio .NET 2005 WebParts can't connect to SQL Server 2005

Reply
Thread Tools

Visual Studio .NET 2005 WebParts can't connect to SQL Server 2005

 
 
XJ
Guest
Posts: n/a
 
      12-26-2007
Hi All

I'm having problems creating WebParts in Visual Studio .NET 2005 with
SQL
Server 2005. I'm using Windows XP with Service Pack 2.

I've created a new web application and placed one WebPartManager
control on
the page and no other controls. Then I ran the application but
received the
following error message:

An error has occurred while establishing a connection to the server.
When
connecting to SQL Server 2005, this failure may be caused by the fact
that
under the default settings SQL Server does not allow remote
connections.
(provider: SQL Network Interfaces, error: 26 - Error Locating Server/
Instance
Specified)

Description: An unhandled exception occurred during the execution of
the
current web request. Please review the stack trace for more
information about
the error and where it originated in the code.

SQLExpress database file auto-creation error:

The connection string specifies a local Sql Server Express instance
using a
database location within the applications App_Data directory. The
provider
attempted to automatically create the application services database
because
the provider determined that the database does not exist. The
following
configuration requirements are necessary to successfully check for
existence
of the application services database and automatically create the
application
services database:

If the applications App_Data directory does not already exist, the
web
server account must have read and write access to the applications
directory.
This is necessary because the web server account will automatically
create
the App_Data directory if it does not already exist.
If the applications App_Data directory already exists, the web server
account only requires read and write access to the applications
App_Data
directory. This is necessary because the web server account will
attempt to
verify that the Sql Server Express database already exists within the
applications App_Data directory. Revoking read access on the App_Data
directory from the web server account will prevent the provider from
correctly determining if the Sql Server Express database already
exists. This
will cause an error when the provider attempts to create a duplicate
of an
already existing database. Write access is required because the web
server
accounts credentials are used when creating the new database.
Sql Server Express must be installed on the machine.
The process identity for the web server account must have a local
user
profile. See the readme document for details on how to create a local
user
profile for both machine and domain accounts.

Source Error:
An unhandled exception was generated during the execution of the
current web
request. Information regarding the origin and location of the
exception can
be identified using the exception stack trace below.

Stack Trace:
[SqlException (0x80131904): An error has occurred while establishing
a
connection to the server. When connecting to SQL Server 2005, this
failure
may be caused by the fact that under the default settings SQL Server
does not
allow remote connections. (provider: SQL Network Interfaces, error: 26
-
Error Locating Server/Instance Specified)]
System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, Boolean breakConnection) +735043

System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
stateObj) +188
System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner,
Boolean& failoverDemandDone, String host, String failoverPartner,
String
protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire,
Boolean
encrypt, Boolean trustServerCert, Boolean integratedSecurity,
SqlConnection
owningObject, Boolean aliasLookup) +820

System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String
newPassword,
Boolean redirectedUserInstance) +628

System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo,
String
newPassword, SqlConnection owningObject, Boolean
redirectedUserInstance) +170

System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool,
DbConnection
owningConnection) +130

System.Data.ProviderBase.DbConnectionFactory.Creat eNonPooledConnection(DbConnection
owningConnection, DbConnectionPoolGroup poolGroup) +27
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection) +47
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Web.Management.SqlServices.GetSqlConnection (String server,
String
user, String password, Boolean trusted, String connectionString) +68

[HttpException (0x80004005): Unable to connect to SQL Server
database.]
System.Web.Management.SqlServices.GetSqlConnection (String server,
String
user, String password, Boolean trusted, String connectionString) +124
System.Web.Management.SqlServices.SetupApplication Services(String
server,
String user, String password, Boolean trusted, String
connectionString,
String database, String dbFileName, SqlFeatures features, Boolean
install) +86
System.Web.Management.SqlServices.Install(String database, String
dbFileName, String connectionString) +25
System.Web.DataAccess.SqlConnectionHelper.CreateMd fFile(String
fullFileName, String dataDir, String connectionString) +397
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42;
ASP.NET
Version:2.0.50727.42


Any suggestions would be greatly appreciated.

Thanks!!
 
Reply With Quote
 
 
 
 
Adlai Maschiach
Guest
Posts: n/a
 
      12-26-2007
Hi

I think the problem is the fact that you didn't enable user instance
in the Sql Server 2005 Express instance

to do so run the following in the 'Query' window
------- Start T-SQL
exec sp_configure 'user instances enabled', 1
-------- End T-SQL
---------

Adlai Maschiach
http://blogs.microsoft.co.il/blogs/adlaim/


"XJ" wrote:

> Hi All
>
> I'm having problems creating WebParts in Visual Studio .NET 2005 with
> SQL
> Server 2005. I'm using Windows XP with Service Pack 2.
>
> I've created a new web application and placed one WebPartManager
> control on
> the page and no other controls. Then I ran the application but
> received the
> following error message:
>
> An error has occurred while establishing a connection to the server.
> When
> connecting to SQL Server 2005, this failure may be caused by the fact
> that
> under the default settings SQL Server does not allow remote
> connections.
> (provider: SQL Network Interfaces, error: 26 - Error Locating Server/
> Instance
> Specified)
>
> Description: An unhandled exception occurred during the execution of
> the
> current web request. Please review the stack trace for more
> information about
> the error and where it originated in the code.
>
> SQLExpress database file auto-creation error:
>
> The connection string specifies a local Sql Server Express instance
> using a
> database location within the applications App_Data directory. The
> provider
> attempted to automatically create the application services database
> because
> the provider determined that the database does not exist. The
> following
> configuration requirements are necessary to successfully check for
> existence
> of the application services database and automatically create the
> application
> services database:
>
> If the applications App_Data directory does not already exist, the
> web
> server account must have read and write access to the applications
> directory.
> This is necessary because the web server account will automatically
> create
> the App_Data directory if it does not already exist.
> If the applications App_Data directory already exists, the web server
> account only requires read and write access to the applications
> App_Data
> directory. This is necessary because the web server account will
> attempt to
> verify that the Sql Server Express database already exists within the
> applications App_Data directory. Revoking read access on the App_Data
> directory from the web server account will prevent the provider from
> correctly determining if the Sql Server Express database already
> exists. This
> will cause an error when the provider attempts to create a duplicate
> of an
> already existing database. Write access is required because the web
> server
> accounts credentials are used when creating the new database.
> Sql Server Express must be installed on the machine.
> The process identity for the web server account must have a local
> user
> profile. See the readme document for details on how to create a local
> user
> profile for both machine and domain accounts.
>
> Source Error:
> An unhandled exception was generated during the execution of the
> current web
> request. Information regarding the origin and location of the
> exception can
> be identified using the exception stack trace below.
>
> Stack Trace:
> [SqlException (0x80131904): An error has occurred while establishing
> a
> connection to the server. When connecting to SQL Server 2005, this
> failure
> may be caused by the fact that under the default settings SQL Server
> does not
> allow remote connections. (provider: SQL Network Interfaces, error: 26
> -
> Error Locating Server/Instance Specified)]
> System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
> exception, Boolean breakConnection) +735043
>
> System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
> stateObj) +188
> System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner,
> Boolean& failoverDemandDone, String host, String failoverPartner,
> String
> protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire,
> Boolean
> encrypt, Boolean trustServerCert, Boolean integratedSecurity,
> SqlConnection
> owningObject, Boolean aliasLookup) +820
>
> System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection
> owningObject, SqlConnectionString connectionOptions, String
> newPassword,
> Boolean redirectedUserInstance) +628
>
> System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdentity
> identity, SqlConnectionString connectionOptions, Object providerInfo,
> String
> newPassword, SqlConnection owningObject, Boolean
> redirectedUserInstance) +170
>
> System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions
> options, Object poolGroupProviderInfo, DbConnectionPool pool,
> DbConnection
> owningConnection) +130
>
> System.Data.ProviderBase.DbConnectionFactory.Creat eNonPooledConnection(DbConnection
> owningConnection, DbConnectionPoolGroup poolGroup) +27
> System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
> owningConnection) +47
> System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
> outerConnection, DbConnectionFactory connectionFactory) +105
> System.Data.SqlClient.SqlConnection.Open() +111
> System.Web.Management.SqlServices.GetSqlConnection (String server,
> String
> user, String password, Boolean trusted, String connectionString) +68
>
> [HttpException (0x80004005): Unable to connect to SQL Server
> database.]
> System.Web.Management.SqlServices.GetSqlConnection (String server,
> String
> user, String password, Boolean trusted, String connectionString) +124
> System.Web.Management.SqlServices.SetupApplication Services(String
> server,
> String user, String password, Boolean trusted, String
> connectionString,
> String database, String dbFileName, SqlFeatures features, Boolean
> install) +86
> System.Web.Management.SqlServices.Install(String database, String
> dbFileName, String connectionString) +25
> System.Web.DataAccess.SqlConnectionHelper.CreateMd fFile(String
> fullFileName, String dataDir, String connectionString) +397
> --------------------------------------------------------------------------------
> Version Information: Microsoft .NET Framework Version:2.0.50727.42;
> ASP.NET
> Version:2.0.50727.42
>
>
> Any suggestions would be greatly appreciated.
>
> Thanks!!
>

 
Reply With Quote
 
 
 
 
XJ
Guest
Posts: n/a
 
      12-26-2007
On Dec 26, 2:59*pm, Adlai Maschiach
<(E-Mail Removed)> wrote:
> Hi
>
> I think the problem is the fact that you didn't enable user instance
> in the Sql Server 2005 Express instance
>
> to do so run the following in the 'Query' window
> ------- Start T-SQL
> exec sp_configure 'user instances enabled', 1
> -------- End T-SQL
> ---------
>
> Adlai Maschiachhttp://blogs.microsoft.co.il/blogs/adlaim/
>
>
>
> "XJ" wrote:
> > Hi All

>
> > I'm having problems creating WebParts in Visual Studio .NET 2005 with
> > SQL
> > Server 2005. I'm using Windows XP with Service Pack 2.

>
> > I've created a new web application and placed one WebPartManager
> > control on
> > the page and no other controls. Then I ran the application but
> > received the
> > following error message:

>
> > An error has occurred while establishing a connection to the server.
> > When
> > connecting to SQL Server 2005, this failure may be caused by the fact
> > that
> > under the default settings SQL Server does not allow remote
> > connections.
> > (provider: SQL Network Interfaces, error: 26 - Error Locating Server/
> > Instance
> > Specified)

>
> > Description: An unhandled exception occurred during the execution of
> > the
> > current web request. Please review the stack trace for more
> > information about
> > the error and where it originated in the code.

>
> > SQLExpress database file auto-creation error:

>
> > The connection string specifies a local Sql Server Express instance
> > using a
> > database location within the applications App_Data directory. The
> > provider
> > attempted to automatically create the application services database
> > because
> > the provider determined that the database does not exist. The
> > following
> > configuration requirements are necessary to successfully check for
> > existence
> > of the application services database and automatically create the
> > application
> > services database:

>
> > If the applications App_Data directory does not already exist, the
> > web
> > server account must have read and write access to the applications
> > directory.
> > This is necessary because the web server account will automatically
> > create
> > the App_Data directory if it does not already exist.
> > If the applications App_Data directory already exists, the web server
> > account only requires read and write access to the applications
> > App_Data
> > directory. This is necessary because the web server account will
> > attempt to
> > verify that the Sql Server Express database already exists within the
> > applications App_Data directory. Revoking read access on the App_Data
> > directory from the web server account will prevent the provider from
> > correctly determining if the Sql Server Express database already
> > exists. This
> > will cause an error when the provider attempts to create a duplicate
> > of an
> > already existing database. Write access is required because the web
> > server
> > accounts credentials are used when creating the new database.
> > Sql Server Express must be installed on the machine.
> > The process identity for the web server account must have a local
> > user
> > profile. See the readme document for details on how to create a local
> > user
> > profile for both machine and domain accounts.

>
> > Source Error:
> > An unhandled exception was generated during the execution of the
> > current web
> > request. Information regarding the origin and location of the
> > exception can
> > be identified using the exception stack trace below.

>
> > Stack Trace:
> > [SqlException (0x80131904): An error has occurred while establishing
> > a
> > connection to the server. When connecting to SQL Server 2005, this
> > failure
> > may be caused by the fact that under the default settings SQL Server
> > does not
> > allow remote connections. (provider: SQL Network Interfaces, error: 26
> > -
> > Error Locating Server/Instance Specified)]
> > System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
> > exception, Boolean breakConnection) +735043

>
> > System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObje*ct
> > stateObj) +188
> > System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner,
> > Boolean& failoverDemandDone, String host, String failoverPartner,
> > String
> > protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire,
> > Boolean
> > encrypt, Boolean trustServerCert, Boolean integratedSecurity,
> > SqlConnection
> > owningObject, Boolean aliasLookup) +820

>
> > System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnectio*n
> > owningObject, SqlConnectionString connectionOptions, String
> > newPassword,
> > Boolean redirectedUserInstance) +628

>
> > System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdenti*ty
> > identity, SqlConnectionString connectionOptions, Object providerInfo,
> > String
> > newPassword, SqlConnection owningObject, Boolean
> > redirectedUserInstance) +170

>
> > System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOpt*ions
> > options, Object poolGroupProviderInfo, DbConnectionPool pool,
> > DbConnection
> > owningConnection) +130

>
> > System.Data.ProviderBase.DbConnectionFactory.Creat eNonPooledConnection(DbCo*nnection
> > owningConnection, DbConnectionPoolGroup poolGroup) +27
> > System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
> > owningConnection) +47
> > System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
> > outerConnection, DbConnectionFactory connectionFactory) +105
> > System.Data.SqlClient.SqlConnection.Open() +111
> > System.Web.Management.SqlServices.GetSqlConnection (String server,
> > String
> > user, String password, Boolean trusted, String connectionString) +68

>
> > [HttpException (0x80004005): Unable to connect to SQL Server
> > database.]
> > System.Web.Management.SqlServices.GetSqlConnection (String server,
> > String
> > user, String password, Boolean trusted, String connectionString) +124
> > System.Web.Management.SqlServices.SetupApplication Services(String
> > server,
> > String user, String password, Boolean trusted, String
> > connectionString,
> > String database, String dbFileName, SqlFeatures features, Boolean
> > install) +86
> > System.Web.Management.SqlServices.Install(String database, String
> > dbFileName, String connectionString) +25
> > System.Web.DataAccess.SqlConnectionHelper.CreateMd fFile(String
> > fullFileName, String dataDir, String connectionString) +397
> > ---------------------------------------------------------------------------*-----
> > Version Information: Microsoft .NET Framework Version:2.0.50727.42;
> > ASP.NET
> > Version:2.0.50727.42

>
> > Any suggestions would be greatly appreciated.

>
> > Thanks!!- Hide quoted text -

>
> - Show quoted text -


Hi,
thanks for ur reply, however my SQL 2005 version is "Microsoft SQL
Server Developer Edition" and also when i trying to run for the
exec sp_configure 'user instances enabled', 1 give give me
failed, and i have chked for the sp_configure, that is no record under
this parameter.

best regards
 
Reply With Quote
 
Adlai Maschiach
Guest
Posts: n/a
 
      12-26-2007

Hi

then try to run first this

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspn et_regsql.exe

and "rediret" it to this Sql Server ( by default is searches for
".\SqlExpress" )
---------


Adlai Maschiach
http://blogs.microsoft.co.il/blogs/adlaim/


"XJ" wrote:

> On Dec 26, 2:59 pm, Adlai Maschiach
> <(E-Mail Removed)> wrote:
> > Hi
> >
> > I think the problem is the fact that you didn't enable user instance
> > in the Sql Server 2005 Express instance
> >
> > to do so run the following in the 'Query' window
> > ------- Start T-SQL
> > exec sp_configure 'user instances enabled', 1
> > -------- End T-SQL
> > ---------
> >
> > Adlai Maschiachhttp://blogs.microsoft.co.il/blogs/adlaim/
> >
> >
> >
> > "XJ" wrote:
> > > Hi All

> >
> > > I'm having problems creating WebParts in Visual Studio .NET 2005 with
> > > SQL
> > > Server 2005. I'm using Windows XP with Service Pack 2.

> >
> > > I've created a new web application and placed one WebPartManager
> > > control on
> > > the page and no other controls. Then I ran the application but
> > > received the
> > > following error message:

> >
> > > An error has occurred while establishing a connection to the server.
> > > When
> > > connecting to SQL Server 2005, this failure may be caused by the fact
> > > that
> > > under the default settings SQL Server does not allow remote
> > > connections.
> > > (provider: SQL Network Interfaces, error: 26 - Error Locating Server/
> > > Instance
> > > Specified)

> >
> > > Description: An unhandled exception occurred during the execution of
> > > the
> > > current web request. Please review the stack trace for more
> > > information about
> > > the error and where it originated in the code.

> >
> > > SQLExpress database file auto-creation error:

> >
> > > The connection string specifies a local Sql Server Express instance
> > > using a
> > > database location within the applications App_Data directory. The
> > > provider
> > > attempted to automatically create the application services database
> > > because
> > > the provider determined that the database does not exist. The
> > > following
> > > configuration requirements are necessary to successfully check for
> > > existence
> > > of the application services database and automatically create the
> > > application
> > > services database:

> >
> > > If the applications App_Data directory does not already exist, the
> > > web
> > > server account must have read and write access to the applications
> > > directory.
> > > This is necessary because the web server account will automatically
> > > create
> > > the App_Data directory if it does not already exist.
> > > If the applications App_Data directory already exists, the web server
> > > account only requires read and write access to the applications
> > > App_Data
> > > directory. This is necessary because the web server account will
> > > attempt to
> > > verify that the Sql Server Express database already exists within the
> > > applications App_Data directory. Revoking read access on the App_Data
> > > directory from the web server account will prevent the provider from
> > > correctly determining if the Sql Server Express database already
> > > exists. This
> > > will cause an error when the provider attempts to create a duplicate
> > > of an
> > > already existing database. Write access is required because the web
> > > server
> > > accounts credentials are used when creating the new database.
> > > Sql Server Express must be installed on the machine.
> > > The process identity for the web server account must have a local
> > > user
> > > profile. See the readme document for details on how to create a local
> > > user
> > > profile for both machine and domain accounts.

> >
> > > Source Error:
> > > An unhandled exception was generated during the execution of the
> > > current web
> > > request. Information regarding the origin and location of the
> > > exception can
> > > be identified using the exception stack trace below.

> >
> > > Stack Trace:
> > > [SqlException (0x80131904): An error has occurred while establishing
> > > a
> > > connection to the server. When connecting to SQL Server 2005, this
> > > failure
> > > may be caused by the fact that under the default settings SQL Server
> > > does not
> > > allow remote connections. (provider: SQL Network Interfaces, error: 26
> > > -
> > > Error Locating Server/Instance Specified)]
> > > System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
> > > exception, Boolean breakConnection) +735043

> >
> > > System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObjeย*ct
> > > stateObj) +188
> > > System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner,
> > > Boolean& failoverDemandDone, String host, String failoverPartner,
> > > String
> > > protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire,
> > > Boolean
> > > encrypt, Boolean trustServerCert, Boolean integratedSecurity,
> > > SqlConnection
> > > owningObject, Boolean aliasLookup) +820

> >
> > > System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnectioย*n
> > > owningObject, SqlConnectionString connectionOptions, String
> > > newPassword,
> > > Boolean redirectedUserInstance) +628

> >
> > > System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdentiย*ty
> > > identity, SqlConnectionString connectionOptions, Object providerInfo,
> > > String
> > > newPassword, SqlConnection owningObject, Boolean
> > > redirectedUserInstance) +170

> >
> > > System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptย*ions
> > > options, Object poolGroupProviderInfo, DbConnectionPool pool,
> > > DbConnection
> > > owningConnection) +130

> >
> > > System.Data.ProviderBase.DbConnectionFactory.Creat eNonPooledConnection(DbCoย*nnection
> > > owningConnection, DbConnectionPoolGroup poolGroup) +27
> > > System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
> > > owningConnection) +47
> > > System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
> > > outerConnection, DbConnectionFactory connectionFactory) +105
> > > System.Data.SqlClient.SqlConnection.Open() +111
> > > System.Web.Management.SqlServices.GetSqlConnection (String server,
> > > String
> > > user, String password, Boolean trusted, String connectionString) +68

> >
> > > [HttpException (0x80004005): Unable to connect to SQL Server
> > > database.]
> > > System.Web.Management.SqlServices.GetSqlConnection (String server,
> > > String
> > > user, String password, Boolean trusted, String connectionString) +124
> > > System.Web.Management.SqlServices.SetupApplication Services(String
> > > server,
> > > String user, String password, Boolean trusted, String
> > > connectionString,
> > > String database, String dbFileName, SqlFeatures features, Boolean
> > > install) +86
> > > System.Web.Management.SqlServices.Install(String database, String
> > > dbFileName, String connectionString) +25
> > > System.Web.DataAccess.SqlConnectionHelper.CreateMd fFile(String
> > > fullFileName, String dataDir, String connectionString) +397
> > > ---------------------------------------------------------------------------ย*-----
> > > Version Information: Microsoft .NET Framework Version:2.0.50727.42;
> > > ASP.NET
> > > Version:2.0.50727.42

> >
> > > Any suggestions would be greatly appreciated.

> >
> > > Thanks!!- Hide quoted text -

> >
> > - Show quoted text -

>
> Hi,
> thanks for ur reply, however my SQL 2005 version is "Microsoft SQL
> Server Developer Edition" and also when i trying to run for the
> exec sp_configure 'user instances enabled', 1 give give me
> failed, and i have chked for the sp_configure, that is no record under
> this parameter.
>
> best regards
>

 
Reply With Quote
 
Adlai Maschiach
Guest
Posts: n/a
 
      12-26-2007
Hi

I have tried on my Sql 2005 Developer Edition and it worked

again the T-SQL

sp_configure 'user options' , 1

try it after the reconfiguration using the EXE tool I have toled you
--
---------
"ื”ืื ื”ื•ื“ืขื” ื–ื• ื”ื•ืขื™ืœื” ืœืš?" , ืื*ื ื”ืฆื‘ืข "ื›ืŸ" ืœืžื˜ื”

Adlai Maschiach
http://blogs.microsoft.co.il/blogs/adlaim/
 
Reply With Quote
 
XJ
Guest
Posts: n/a
 
      12-26-2007
On Dec 26, 5:35ย*pm, Adlai Maschiach
<(E-Mail Removed)> wrote:
> Hi
>
> I have tried on my Sql 2005 Developer Edition and it worked
>
> again the T-SQL
>
> sp_configure 'user options' , 1
>
> try it after the reconfiguration using the EXE tool I have toled you
> --
> ---------
> "ื”ืื ื”ื•ื“ืขื” ื–ื• ื”ื•ืขื™ืœื” ืœืš?" ย*, ืื*ื ื”ืฆื‘ืข "ื›ืŸ" ืœืžื˜ื”
>
> Adlai Maschiachhttp://blogs.microsoft.co.il/blogs/adlaim/


Hi,
thanks for ur advice; yes after i run for the aspnet_regsql.exe
and poping a dialog , from there i have configured for the SQL
setting. and also im able to run for the 'user options' .
However the error still the same ( even i have restart my SQL Server
service ).

 
Reply With Quote
 
Adlai Maschiach
Guest
Posts: n/a
 
      12-26-2007
Hi

two more things

1. try for the test to stop the WinXP SP2 Firewall
2. take a look and see if the SqlServer-Agent is running , if not start it
3. I would re-run the "EXE"

and now try again
---------
Adlai Maschiach

http://blogs.microsoft.co.il/blogs/adlaim/


"XJ" wrote:

> On Dec 26, 5:35 pm, Adlai Maschiach
> <(E-Mail Removed)> wrote:
> > Hi
> >
> > I have tried on my Sql 2005 Developer Edition and it worked
> >
> > again the T-SQL
> >
> > sp_configure 'user options' , 1
> >
> > try it after the reconfiguration using the EXE tool I have toled you
> > --
> > ---------
> > "ื”ืื ื”ื•ื“ืขื” ื–ื• ื”ื•ืขื™ืœื” ืœืš?" , ืื*ื ื”ืฆื‘ืข "ื›ืŸ" ืœืžื˜ื”
> >
> > Adlai Maschiachhttp://blogs.microsoft.co.il/blogs/adlaim/

>
> Hi,
> thanks for ur advice; yes after i run for the aspnet_regsql.exe
> and poping a dialog , from there i have configured for the SQL
> setting. and also im able to run for the 'user options' .
> However the error still the same ( even i have restart my SQL Server
> service ).
>
>

 
Reply With Quote
 
XJ
Guest
Posts: n/a
 
      12-28-2007
On Dec 26, 6:40ย*pm, Adlai Maschiach
<(E-Mail Removed)> wrote:
> Hi
>
> two more things
>
> 1. try for the test to stop the WinXP SP2 Firewall
> 2. take a look and see if the SqlServer-Agent is running , if not start it
> 3. I would re-run the "EXE"
>
> and now try again
> ---------
> ย*Adlai Maschiach
>
> http://blogs.microsoft.co.il/blogs/adlaim/
>
>
>
> "XJ" wrote:
> > On Dec 26, 5:35 pm, Adlai Maschiach
> > <(E-Mail Removed)> wrote:
> > > Hi

>
> > > I have tried on my Sql 2005 Developer Edition and it worked

>
> > > again the T-SQL

>
> > > sp_configure 'user options' , 1

>
> > > try it after the reconfiguration using the EXE tool I have toled you
> > > --
> > > ---------
> > > "ื”ืื ื”ื•ื“ืขื” ื–ื• ื”ื•ืขื™ืœื” ืœืš?" ย*, ืื*ื ื”ืฆื‘ืข "ื›ืŸ" ืœืžื˜ื”

>
> > > Adlai Maschiachhttp://blogs.microsoft.co.il/blogs/adlaim/

>
> > Hi,
> > ย* ย* thanks for ur advice; yes after i run for the aspnet_regsql.exe
> > and poping a dialog , from there i have configured for the SQL
> > setting. and also im able to run for the 'user options' .
> > However the error still the same ( even i have restart my SQL Server
> > service ).- Hide quoted text -

>
> - Show quoted text -


no brother, still no luck .
 
Reply With Quote
 
XJ
Guest
Posts: n/a
 
      01-07-2008
On Dec 26 2007, 6:40ย*pm, Adlai Maschiach
<(E-Mail Removed)> wrote:
> Hi
>
> two more things
>
> 1. try for the test to stop the WinXP SP2 Firewall
> 2. take a look and see if the SqlServer-Agent is running , if not start it
> 3. I would re-run the "EXE"
>
> and now try again
> ---------
> ย*Adlai Maschiach
>
> http://blogs.microsoft.co.il/blogs/adlaim/
>
>
>
> "XJ" wrote:
> > On Dec 26, 5:35 pm, Adlai Maschiach
> > <(E-Mail Removed)> wrote:
> > > Hi

>
> > > I have tried on my Sql 2005 Developer Edition and it worked

>
> > > again the T-SQL

>
> > > sp_configure 'user options' , 1

>
> > > try it after the reconfiguration using the EXE tool I have toled you
> > > --
> > > ---------
> > > "ื”ืื ื”ื•ื“ืขื” ื–ื• ื”ื•ืขื™ืœื” ืœืš?" ย*, ืื*ื ื”ืฆื‘ืข "ื›ืŸ" ืœืžื˜ื”

>
> > > Adlai Maschiachhttp://blogs.microsoft.co.il/blogs/adlaim/

>
> > Hi,
> > ย* ย* thanks for ur advice; yes after i run for the aspnet_regsql.exe
> > and poping a dialog , from there i have configured for the SQL
> > setting. and also im able to run for the 'user options' .
> > However the error still the same ( even i have restart my SQL Server
> > service ).- Hide quoted text -

>
> - Show quoted text -


Hey! i found the solution !

http://forums.asp.net/p/897765/972711.aspx


cheers!!!
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Can't connect to SQL Server in an IIS web application after installing Visual Studio 2005 sim0n ASP .Net 0 03-16-2006 02:55 PM
Re: "Certifications for Visual Studio 2005 and SQL Server 2005 wil Pedro Simoes MCSD 0 11-24-2005 07:52 PM
"Certifications for Visual Studio 2005 and SQL Server 2005 will be available in early 2006" Pedro Simoes MCSD 0 11-24-2005 07:52 PM
"Certifications for Visual Studio 2005 and SQL Server 2005 will be available in early 2006" DST MCSD 8 10-28-2005 02:50 AM
New Exams for SQL Server 2005 and Visual Studio 2005 gemeaux | tt Microsoft Certification 1 10-25-2004 06:59 PM



Advertisments