Error while connection: application

Showing posts with label application. Show all posts

Thursday, March 29, 2012

Error: Data source name not found and No default driver specified

Hello all,
I have an application which was written in VB6. I used
DSNless connection for the odbc connection to access sql 8.0. The
application works fine on one machine and when I try to run the appl.
on another machine I got this error. Any idea why' Here is my
connection string:
DSNName = "Driver={SQL Server};" & _
"Server=dummy;" & _
"Database=sql_data;" & _
"Uid=crystal"
The user id does not require a password.. Thank you.
SherryThis is a question for a VB group, not a SQL server group, but it sounds
like your DSNName is empty. Are you getting this value from an INI file,
the registry, or is it hardcoded in your app? You will most likely find
that this value is missing, wherever you define it.
Put in a message box that shows DSNName just prior to creating the
connection, and confirm that it is actually populated (I don't think it is).
<sunpalozzi@.gmail.com> wrote in message
news:1138811193.427214.282490@.g43g2000cwa.googlegroups.com...
> Hello all,
> I have an application which was written in VB6. I used
> DSNless connection for the odbc connection to access sql 8.0. The
> application works fine on one machine and when I try to run the appl.
> on another machine I got this error. Any idea why' Here is my
> connection string:
> DSNName = "Driver={SQL Server};" & _
> "Server=dummy;" & _
> "Database=sql_data;" & _
> "Uid=crystal"
> The user id does not require a password.. Thank you.
> Sherry
>|||Maybe the other machine doesn't have MDAC installed?
http://www.aspfaq.com/2057
Once you have the most recent version installed, an OLEDB connection string
will be better in most cases:
ConnectionString = _
"Provider=SQLOLEDB.1; " & _
"Data Source=dummy; " & _
"Initial Catalog=sql_data; " & _
"User ID=crystal; " & _
"Password="
<sunpalozzi@.gmail.com> wrote in message
news:1138811193.427214.282490@.g43g2000cwa.googlegroups.com...
> Hello all,
> I have an application which was written in VB6. I used
> DSNless connection for the odbc connection to access sql 8.0. The
> application works fine on one machine and when I try to run the appl.
> on another machine I got this error. Any idea why' Here is my
> connection string:
> DSNName = "Driver={SQL Server};" & _
> "Server=dummy;" & _
> "Database=sql_data;" & _
> "Uid=crystal"
> The user id does not require a password.. Thank you.
> Sherry
>|||thank you for all replies.. I did post in the vb group as well.. The
wire part is the same application is work on one pc but not the
another... I will try to find out if there a MDAC install on the
problem pc.. thanks.
Sherry

Tuesday, March 27, 2012

Error: Application for .reportproj not installed

Getting error when try to open report project:
The application for D:\Documents and Settings\Administrator\My
Documents\Visual Studio Projects\WinfundsReports.rptproj is not installed.
Make surethe application for the project type (.rptproj) is installed.
Everything had been working fine for a year!
Note: Busuness Intelligence Projects no longer appears in the list of
available project types when setting up new project.
Is this controlled by something in the config files, or will I have to
reinstall Rptg Services?
Thanks.
AlanFollowup Question:
Is there a file that will re-register reporting services withou a complete
re-install?
Thanks.
Alan

Monday, March 26, 2012

Error: 7105, Severity: 22, State: 6

it is a SQL 2000 with SP4 on Windows server 2003 SP1.
"ME" <ME@.mail.com> wrote in message news:...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>
The affinity mask is set as default. The server is 2 dual core CPUs. SQL
sees and uses all of 4 CPUs.
"ME" <ME@.mail.com> wrote in message
news:egU%23OuT$GHA.1224@.TK2MSFTNGP04.phx.gbl...
> it is a SQL 2000 with SP4 on Windows server 2003 SP1.
>
> "ME" <ME@.mail.com> wrote in message news:...
>

Error: 7105, Severity: 22, State: 6

My SQL server logs this in Application log:
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.
Make the call, they will tell you up front if it will be a covered (free)
call.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>
|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>

Error: 7105, Severity: 22, State: 6

it is a SQL 2000 with SP4 on Windows server 2003 SP1.
"ME" <ME@.mail.com> wrote in message news:...
> My SQL server logs this in Application log:
>
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
>
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
>
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>
>The affinity mask is set as default. The server is 2 dual core CPUs. SQL
sees and uses all of 4 CPUs.
"ME" <ME@.mail.com> wrote in message
news:egU%23OuT$GHA.1224@.TK2MSFTNGP04.phx.gbl...
> it is a SQL 2000 with SP4 on Windows server 2003 SP1.
>
> "ME" <ME@.mail.com> wrote in message news:...
>> My SQL server logs this in Application log:
>> Error: 7105, Severity: 22, State: 6
>> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
>> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
>> for
>> a hot fix for this problem.
>> I believe this call is free because this is a bug. Can anyone confirm
>> this?
>> Thanks.
>>
>

Error: 7105, Severity: 22, State: 6

My SQL server logs this in Application log:
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.Make the call, they will tell you up front if it will be a covered (free)
call.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>> My SQL server logs this in Application log:
>> Error: 7105, Severity: 22, State: 6
>> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
>> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
>> for
>> a hot fix for this problem.
>> I believe this call is free because this is a bug. Can anyone confirm
>> this?
>> Thanks.
>>
>

Error: 7105, Severity: 22, State: 6

My SQL server logs this in Application log:
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.it is a SQL 2000 with SP4 on Windows server 2003 SP1.
"ME" <ME@.mail.com> wrote in message news:...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>|||The affinity mask is set as default. The server is 2 dual core CPUs. SQL
sees and uses all of 4 CPUs.
"ME" <ME@.mail.com> wrote in message
news:egU%23OuT$GHA.1224@.TK2MSFTNGP04.phx.gbl...
> it is a SQL 2000 with SP4 on Windows server 2003 SP1.
>
> "ME" <ME@.mail.com> wrote in message news:...
>|||Make the call, they will tell you up front if it will be a covered (free)
call.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>

Wednesday, March 21, 2012

Error: 18456 Severity: 14, State: 11

I have a SQL 2005 SP1 test server running Developer Edition on top of Windows Server 2003 SP1. We're testing out a 3rd party application that is using Windows Authentication to connect to SQL 2005. The SQL Error Log is saturated with the error message listed in the subject line. The text accompanying the message alternates between "Login failed for user 'MYDOMAIN\TESTDA1$'. [CLIENT: <named pipe>]" and "Login failed for user 'MYDOMAIN\TESTDA1$'. [CLIENT: xxx.xxx.xxx.xxx]".

There are two strange parts to this: 1) The application appears to be working fine on the surface, and, 2) The MYDOMAIN\TESTDA1$ account mentioned in the error text is not the user account that we are using to connect the application to SQL 2005. TESTDA1 is the server name that the 3rd party software is running remotely from.

I've looked up "error state 11" using the following resource:

http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

It describes error states 11 and 12 as "Valid login but server access failure" but I'm not sure what that means. Why would SQL care about the computer account hosting the application?

Thanks in advance for any help.

From your description it seems like the 3^rd party software is attempting to connect to SQL Server using the service account credentials, it is most likely running under “Network Service”, “Local System” or another local account and that’s why when trying to access resources (in this case connect to SQL Server) it uses the machine account (<domain>\<machine_name>$), and as this account doesn’t have privileges to connect to SQL Server it fails.

Check the 3^rd party product documentation, it may be possible that you need to run it using a domain account (I also recommend verifying with your domain administrator regarding your specific environment policies regarding running services under domain accounts).

Another potential workaround would be to grant permission to connect to this machine account, and granting it the minimum permissions required for the software you are testing. Bear in mind than any other service from the same machine will have the same privileges.

I hope this information helps,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Thanks Raul. You were correct - the software was indeed trying to connect using the "Local System" account. We changed this to a domain account that had permission to login to SQL and now everything is working well. No more errors in the SQL Error Log.

Thanks again!

|||I have the same error message in my logs for SQL Server 2005. I've set up a report, gave both the user and the group she belongs to full access to the reports and Content Manager and Browser. She can go through the folders, but if she gets the report and clicks on the link to open the report (on http://servername/reports etc) she gets the error message "cannot create connection to data source 'databasename' and in the error logs it says:

Error: 18456, Severity: 14, State: 11.
Login failed for user 'DOMAIN\User.Name'. [CLIENT: <local machine>]

where domain = an active directory (not local box) domain and User.Name is the actual name of the user who is in that domain.

The error being state 11 means Valid login but server access failure so where do I look to figure out why she can't get into the report? She's trying to access across the network so she's not physically logging onto that computer. Any idea what I need to check?

Thanks!

Linda
|||

Connect to SQL server using a sysadmin account and look if the Windows user has access to SQL Server. You can look first in sys.server_principals for example:

SELECT * FROM sys.server_principals

And look for your Windows principal name directly, or for a group she belongs to and grants permission to connect. If you cannot find the proper entry, you can grant permission to connect to SQL Server by adding a login.

On the other hand, if the login exists, it may be possible that that particular user doesn’t have permissions to connect in the right endpoint. To see all the permissions on the endpoints you can run the following query:

SELECT endpnt.name,

suser_name(perms.grantee_principal_id) as grantee_principal,

perms.permission_name, perms.state_desc

FROM

sys.server_permissions perms,

sys.endpoints endpnt

WHERE

perms.class = 105

AND perms.major_id = endpnt.endpoint_id

If there is a permission missing for this principal, just grant the CONNECT permission at the correct endpoint.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Raul Garcia - MS wrote:
From your description it seems like the 3^rd party software is attempting to connect to SQL Server using the service account credentials, it is most likely running under “Network Service”, “Local System” or another local account and that’s why when trying to access resources (in this case connect to SQL Server) it uses the machine account (<domain>\<machine_name>$), and as this account doesn’t have privileges to connect to SQL Server it fails.

Check the 3^rd party product documentation, it may be possible that you need to run it using a domain account (I also recommend verifying with your domain administrator regarding your specific environment policies regarding running services under domain accounts).

Another potential workaround would be to grant permission to connect to this machine account, and granting it the minimum permissions required for the software you are testing. Bear in mind than any other service from the same machine will have the same privileges.

I hope this information helps,

-Raul Garcia
SDE/T
SQL Server Engine

Hello there,

I got exactly the same scenario. Unfortunately I am not able to change the service account to any other thing than local system.

If I would like to add access to my database for the machine$ accounts, what exactly would I have to do ?

Could anyone give me a hint please ?

Thanks in advance

Gordon

|||

You can use the CREATE LOGIN DDL to create the login for the machine account, for example:

CREATE LOGIN [DOMAIN\machine_name$] FROM WINDOWS

Let us know if this information helped and/or if you have any additional questions.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

|||Thanks for the hint. This didn't solve my problem. Do I have to grant any special rights after creating those logins ?|||

After creating the logins I forgot to map a role to the users for my database.

I just followed the instructions found in another article here :

navigate through Security > Logins > Properties > User Mapping > Choose the Database > Map the user to the database (you will see that he will get the public role by default)

Error: 18456 Severity: 14, State: 11

I've looked up "error state 11" using the following resource:

http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

It describes error states 11 and 12 as "Valid login but server access failure" but I'm not sure what that means. Why would SQL care about the computer account hosting the application?

Thanks in advance for any help.

I hope this information helps,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Thanks again!

Error: 18456, Severity: 14, State: 11.
Login failed for user 'DOMAIN\User.Name'. [CLIENT: <local machine>]

where domain = an active directory (not local box) domain and User.Name is the actual name of the user who is in that domain.

Thanks!

Linda
|||

Connect to SQL server using a sysadmin account and look if the Windows user has access to SQL Server. You can look first in sys.server_principals for example:

SELECT * FROM sys.server_principals

SELECT endpnt.name,

suser_name(perms.grantee_principal_id) as grantee_principal,

perms.permission_name, perms.state_desc

FROM

sys.server_permissions perms,

sys.endpoints endpnt

WHERE

perms.class = 105

AND perms.major_id = endpnt.endpoint_id

If there is a permission missing for this principal, just grant the CONNECT permission at the correct endpoint.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Raul Garcia - MS wrote:

From your description it seems like the 3^rd party software is attempting to connect to SQL Server using the service account credentials, it is most likely running under “Network Service”, “Local System” or another local account and that’s why when trying to access resources (in this case connect to SQL Server) it uses the machine account (<domain>\<machine_name>$), and as this account doesn’t have privileges to connect to SQL Server it fails.

Check the 3^rd party product documentation, it may be possible that you need to run it using a domain account (I also recommend verifying with your domain administrator regarding your specific environment policies regarding running services under domain accounts).

Another potential workaround would be to grant permission to connect to this machine account, and granting it the minimum permissions required for the software you are testing. Bear in mind than any other service from the same machine will have the same privileges.

I hope this information helps,

-Raul Garcia

SDE/T

SQL Server Engine

Hello there,

I got exactly the same scenario. Unfortunately I am not able to change the service account to any other thing than local system.

If I would like to add access to my database for the machine$ accounts, what exactly would I have to do ?

Could anyone give me a hint please ?

Thanks in advance

Gordon

|||

You can use the CREATE LOGIN DDL to create the login for the machine account, for example:

CREATE LOGIN [DOMAIN\machine_name$] FROM WINDOWS

Let us know if this information helped and/or if you have any additional questions.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

|||Thanks for the hint. This didn't solve my problem. Do I have to grant any special rights after creating those logins ?|||

After creating the logins I forgot to map a role to the users for my database.

I just followed the instructions found in another article here :

navigate through Security > Logins > Properties > User Mapping > Choose the Database > Map the user to the database (you will see that he will get the public role by default)

Error: 18456 Severity: 14, State: 10

I have SQL 2005 Expess installed on Windows Server 2003 SP1.

My application is running as a service and is set to depend on SQL Server instance...
During the startup my app attempts to connect to the databes and it fails to do so,
after 30 retries (1second appart). SQL Server log has this error msg:
Error: 18456 "Severity: 14, State: 10"

Once the server has started, I cam manually start my application and it then sucesfully
opens a connection to the database.

What does this error mean?

Srdjan

Hi Srdjan,

Looks like you are getting a login failed error:

http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

How is your app connecting to your db? If you are using Windows authentication, it could be that the service account you are using when running your app as a service does not have permission to log on to the database.

Sung

|||

This error seems to only be reachable when using SQL Authentication, but I'm not sure what could cause it.

You can start SQL Server with "-y 18456", to produce a dump when the error occurs. As the dump will happen during authentication, the login password might appear in it, so you should use a bogus test password for the purpose of the creating this dump, just in case. Once you have the dump, please open a report at https://connect.microsoft.com/feedback/default.aspx?SiteID=68, attach the dump, and mention my name in the report, so it will get assigned to me.

If you can repro this issue with a smaller application that attempts the same connection on startup, you could attach that application as well, so we can attempt to repro the issue in our labs.

Thanks
Laurentiu

|||tried a couple of times to post a bug report...
but getting errors from the web site.

Anyway, new information:

if I run using Windows authentication, error is the ame but
state is now 16.

Still, after loging in - I have no problem starting the same service that failed during automatic startup.

Even the simplest windows servce that just opens connection
behaves the same...

Thanks,
Srdjan|||

State 16 means there was an error in determining the database to be used by the connection. Can you still connect if you start your application manually?

Thanks
Laurentiu

|||yes, as soon as I log in, I can start my application manually.
During Startup my application fails to start because of the unhandled exception thrown from Sql.Client:

System.Data.SqlClient.SqlException: Cannot open database "Db_260" requested by the login. The login failed.
Login failed for user 'NT AUTHORITY\SYSTEM'.
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()

Also here are couple of lines from the SQL errorlog file during machine startup:
2006-07-15 13:56:39.67 spid8s Clearing tempdb database.
2006-07-15 13:56:39.71 Logon Error: 18456, Severity: 14, State: 16.
2006-07-15 13:56:39.71 Logon Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
2006-07-15 13:56:39.95 Logon Error: 18456, Severity: 14, State: 16.
2006-07-15 13:56:39.95 Logon Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
2006-07-15 13:56:40.34 spid8s Starting up database 'tempdb'.
2006-07-15 13:56:40.45 spid5s Recovery is complete. This is an informational message only. No user action is required.
2006-07-15 13:56:40.46 spid11s The Service Broker protocol transport is disabled or not configured.
2006-07-15 13:56:40.46 spid11s The Database Mirroring protocol transport is disabled or not configured.
2006-07-15 13:56:40.56 spid11s Service Broker manager has started.
2006-07-15 13:56:44.78 spid51 Starting up database 'ReportServer$TRBR'.
2006-07-15 13:56:45.09 spid52 Starting up database 'Db_260'.
2006-07-15 13:57:38.96 Server Server resumed execution after being idle 25 seconds: user activity awakened the server. This is an informational message only. No user action is required.

Srdjan|||

You are trying to connect to database Db_260, but the database has not been started up yet. If you will look in the log, you'll see that the server is accepting connections before starting up the database Db_260, so the requests that you make before the database startup will fail. You should take this into account and retry to connect after a delay, to give time to the server to start up the database.

Thanks
Laurentiu

|||Laurentiu,

My code actually retries until it gets connection succesfully.
The problem is that after a couple of failed atempts, I actally get a success, but then it is the the next attempt to connect to database fails with the exception:

Now, I've tried to postpone the first call to database for up to
3 minutes (more is not practical) and nothing really changes,
I get the same behaviour (System.Data.SqlClient.SqlException) on the second call to database...

Srdjan

|||

Are you saying that you get login failure errors after the database is started up? The log excerpt from your previous message doesn't show that. Can you post your errorlog from beginning up to and including the first couple of login failures that you get AFTER the Db_260 database was started up?

Thanks
Laurentiu

|||Laurentiu,

I managed to get around this problem...
My original code that was checking if SQL is ready was simply opening a connection but didn't execute any dabase commands.

For some reason at one point one of these attempts would successed, but then on the first real database access, exception was thrown.

So, I now do retries on the first real access to datbase and that seems to work.

I appreciate your help.

Srdjan
|||

Hi Laurentiu,

I am having a similar problem when after programmatically creating a database I try to create a table, if I do not put an arbitrarily large delay before issuing the create table statement, I get this same "Error: 18456, Severity: 14, State: 16."

Is there any way to issue a SQL statement and block on the call until a new database has been fully initialized and started before continuing? Alternatively, is there a way to get a callback once the DB is online?, Finally, if neither of the previous are possible, is there any entry in the master DB that one could poll to see when the new DB is up and running? I've tried the ovbious state in sys.databases, and Database.Status in DMO with no luck.

Any ideas? Thanks in advance!

GDM

|||

If you are getting a login failed message, it sounds like you are executing the CREATE DATABASE and CREATE TABLE statements on two different connections. Have you considered executing these statements using the same connection? If you would execute the CREATE TABLE after the CREATE DATABASE, on the same connection, you would not see such a failure.

The state you can query is state_desc in sys.databases - if it is ONLINE, it means the database was started.

Thanks
Laurentiu

|||How do i start sql server with "-y 18456"|||

Start->Run...->services.msc

Then go to the SQL Server service and stop it. Then Click <Properties> and in the <Start Parameters> field enter -y 18456. You can then click <Start> to restart the server with that parameter and then press cancel to exit without saving the parameter, so that future restarts won't use it. If you press OK, then the server will be restarted with that parameter - you probably don't want that.

Thanks
Laurentiu

|||

Ok I have an issue here....I am trying to do a full system recovery and this is what I am getting...

File/minint/system32/biosinfo.inf could not be loaded the error is code 14 ?

And I do NOT have the Windows XP Disk either...so if theres a way around this please by all means help me .......

can some please help me with this please

Error: 18456 Severity: 14, State: 10

I have SQL 2005 Expess installed on Windows Server 2003 SP1.

Once the server has started, I cam manually start my application and it then sucesfully
opens a connection to the database.

What does this error mean?

Srdjan

Hi Srdjan,

Looks like you are getting a login failed error:

http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

Sung

|||

This error seems to only be reachable when using SQL Authentication, but I'm not sure what could cause it.

If you can repro this issue with a smaller application that attempts the same connection on startup, you could attach that application as well, so we can attempt to repro the issue in our labs.

Thanks
Laurentiu

|||tried a couple of times to post a bug report...
but getting errors from the web site.

Anyway, new information:

if I run using Windows authentication, error is the ame but
state is now 16.

Still, after loging in - I have no problem starting the same service that failed during automatic startup.

Even the simplest windows servce that just opens connection
behaves the same...

Thanks,
Srdjan|||

State 16 means there was an error in determining the database to be used by the connection. Can you still connect if you start your application manually?

Thanks
Laurentiu

|||yes, as soon as I log in, I can start my application manually.
During Startup my application fails to start because of the unhandled exception thrown from Sql.Client:

Srdjan|||

Thanks
Laurentiu

|||Laurentiu,

Srdjan

|||

Thanks
Laurentiu

|||Laurentiu,

I managed to get around this problem...
My original code that was checking if SQL is ready was simply opening a connection but didn't execute any dabase commands.

For some reason at one point one of these attempts would successed, but then on the first real database access, exception was thrown.

So, I now do retries on the first real access to datbase and that seems to work.

I appreciate your help.

Srdjan
|||

Hi Laurentiu,

Any ideas? Thanks in advance!

GDM

|||

The state you can query is state_desc in sys.databases - if it is ONLINE, it means the database was started.

Thanks
Laurentiu

|||How do i start sql server with "-y 18456"|||

Start->Run...->services.msc

Thanks
Laurentiu

|||

Ok I have an issue here....I am trying to do a full system recovery and this is what I am getting...

File/minint/system32/biosinfo.inf could not be loaded the error is code 14 ?

And I do NOT have the Windows XP Disk either...so if theres a way around this please by all means help me .......

can some please help me with this please

sql

Monday, March 19, 2012

Error: 17806, Severity: 20, State: 2

We installed SQL Server 2005 Std Ed and MSProject application uses the instance..

Getting following Eorr Message

SSPI handshake failed with error code 0x80090311 while establishing a connection with integrated security; the connection has been closed. [CLIENT: <named pipe>]

Appreciate your help to fix this

Thanks

Arul

This is an SSIS forum. Try here for Project - http://www.microsoft.com/office/community/en-us/default.mspx

|||Hi,

1.) Mention the servername in FQDN format or use ip address. This may be due to Named pipes
2.) Try changing the protocols, its better to use TCP/IP port. Try connect using servername,portnumber

Error: 17803, Severity: 20, State: 17

I have an application connected to a machine running MSSQL Server 2000 SP3a
Std Edition. Machine is 2.8GHZ, Windows Server 2000. This application runs
extensive query periodically. Over a period of time, I notice through Task
Manager the sqlservr.exe memory usage has grow to ~1.6GB. When this happen,
the application experience slowdown and eventually hang out.
SQL ERRORLog show
2005-04-22 07:16:36.45 spid1 LazyWriter: warning, no free buffers found.
2005-04-22 07:16:36.45 spid1 Buffer Distribution: Stolen=159182 Free=0
Procedures=22931
Inram=0 Dirty=24545 Kept=0
I/O=0, Latched=2022, Other=0
2005-04-22 07:16:36.45 spid1 Buffer Counts: Commited=208680
Target=208680 Hashed=26567
InternalReservation=2130 ExternalReservation=57 Min Free=512
2005-04-22 07:16:36.45 spid1 Procedure Cache: TotalProcs=3969
TotalPages=22931 InUsePages=22931
2005-04-22 07:16:36.45 spid1 Dynamic Memory Manager: Stolen=182112 OS
Reserved=2544
OS Committed=2487
OS In Use=2468
Query Plan=166599 Optimizer=3
General=14803
Utilities=7 Connection=2910
2005-04-22 07:16:36.45 spid1 Global Memory Objects: Resource=11637
Locks=147
SQLCache=1236 Replication=2
LockBytes=2 ServerGlobal=43
Xact=1862
2005-04-22 07:16:36.45 spid1 Query Memory Manager: Grants=1 Waiting=0
Maximum=13450 Available=13392
2005-04-22 07:16:36.70 server Error: 17803, Severity: 20, State: 17
2005-04-22 07:16:36.70 server Insufficient memory available..
I'm currently using SQL Server 2000 Driver for JDBC (with
SelectMethod=Cursor). From SQL Profiler, I do see alot of sp_cursorfetch
calls that don't have a corresponding sp_cursorclose.
Help is greatly appreaciated here!SQL ran out of free buffers (Free=0). You should probably apply the latest
SQL Server hotfix and update JDBC drivers to prevent problems such as 818095
and 837957. In addition, there are changes in the latest SQL hotfixes which
allow Lazy Writer to run more aggressively when it detects a low number of
free buffers.
If the problems persist engage MS product support and have them check your
server for additional leaks.
Adrian
"SS" <SS@.discussions.microsoft.com> wrote in message
news:884EB064-D4C5-4454-A8B4-A151EBC0ED11@.microsoft.com...
>I have an application connected to a machine running MSSQL Server 2000 SP3a
> Std Edition. Machine is 2.8GHZ, Windows Server 2000. This application runs
> extensive query periodically. Over a period of time, I notice through Task
> Manager the sqlservr.exe memory usage has grow to ~1.6GB. When this
> happen,
> the application experience slowdown and eventually hang out.
> SQL ERRORLog show
> 2005-04-22 07:16:36.45 spid1 LazyWriter: warning, no free buffers
> found.
> 2005-04-22 07:16:36.45 spid1 Buffer Distribution: Stolen=159182
> Free=0
> Procedures=22931
> Inram=0 Dirty=24545 Kept=0
> I/O=0, Latched=2022, Other=0
> 2005-04-22 07:16:36.45 spid1 Buffer Counts: Commited=208680
> Target=208680 Hashed=26567
> InternalReservation=2130 ExternalReservation=57 Min Free=512
> 2005-04-22 07:16:36.45 spid1 Procedure Cache: TotalProcs=3969
> TotalPages=22931 InUsePages=22931
> 2005-04-22 07:16:36.45 spid1 Dynamic Memory Manager: Stolen=182112 OS
> Reserved=2544
> OS Committed=2487
> OS In Use=2468
> Query Plan=166599 Optimizer=3
> General=14803
> Utilities=7 Connection=2910
> 2005-04-22 07:16:36.45 spid1 Global Memory Objects: Resource=11637
> Locks=147
> SQLCache=1236 Replication=2
> LockBytes=2 ServerGlobal=43
> Xact=1862
> 2005-04-22 07:16:36.45 spid1 Query Memory Manager: Grants=1 Waiting=0
> Maximum=13450 Available=13392
> 2005-04-22 07:16:36.70 server Error: 17803, Severity: 20, State: 17
> 2005-04-22 07:16:36.70 server Insufficient memory available..
> I'm currently using SQL Server 2000 Driver for JDBC (with
> SelectMethod=Cursor). From SQL Profiler, I do see alot of sp_cursorfetch
> calls that don't have a corresponding sp_cursorclose.
> Help is greatly appreaciated here!
>

Error: 17803, Severity: 20, State: 17

I have an application connected to a machine running MSSQL Server 2000 SP3a
Std Edition. Machine is 2.8GHZ, Windows Server 2000. This application runs
extensive query periodically. Over a period of time, I notice through Task
Manager the sqlservr.exe memory usage has grow to ~1.6GB. When this happen,
the application experience slowdown and eventually hang out.
SQL ERRORLog show
2005-04-22 07:16:36.45 spid1 LazyWriter: warning, no free buffers found.
2005-04-22 07:16:36.45 spid1 Buffer Distribution: Stolen=159182 Free=0
Procedures=22931
Inram=0 Dirty=24545 Kept=0
I/O=0, Latched=2022, Other=0
2005-04-22 07:16:36.45 spid1 Buffer Counts: Commited=208680
Target=208680 Hashed=26567
InternalReservation=2130 ExternalReservation=57 Min Free=512
2005-04-22 07:16:36.45 spid1 Procedure Cache: TotalProcs=3969
TotalPages=22931 InUsePages=22931
2005-04-22 07:16:36.45 spid1 Dynamic Memory Manager: Stolen=182112 OS
Reserved=2544
OS Committed=2487
OS In Use=2468
Query Plan=166599 Optimizer=3
General=14803
Utilities=7 Connection=2910
2005-04-22 07:16:36.45 spid1 Global Memory Objects: Resource=11637
Locks=147
SQLCache=1236 Replication=2
LockBytes=2 ServerGlobal=43
Xact=1862
2005-04-22 07:16:36.45 spid1 Query Memory Manager: Grants=1 Waiting=0
Maximum=13450 Available=13392
2005-04-22 07:16:36.70 server Error: 17803, Severity: 20, State: 17
2005-04-22 07:16:36.70 server Insufficient memory available..
I'm currently using SQL Server 2000 Driver for JDBC (with
SelectMethod=Cursor). From SQL Profiler, I do see alot of sp_cursorfetch
calls that don't have a corresponding sp_cursorclose.
Help is greatly appreaciated here!
SQL ran out of free buffers (Free=0). You should probably apply the latest
SQL Server hotfix and update JDBC drivers to prevent problems such as 818095
and 837957. In addition, there are changes in the latest SQL hotfixes which
allow Lazy Writer to run more aggressively when it detects a low number of
free buffers.
If the problems persist engage MS product support and have them check your
server for additional leaks.
Adrian
"SS" <SS@.discussions.microsoft.com> wrote in message
news:884EB064-D4C5-4454-A8B4-A151EBC0ED11@.microsoft.com...
>I have an application connected to a machine running MSSQL Server 2000 SP3a
> Std Edition. Machine is 2.8GHZ, Windows Server 2000. This application runs
> extensive query periodically. Over a period of time, I notice through Task
> Manager the sqlservr.exe memory usage has grow to ~1.6GB. When this
> happen,
> the application experience slowdown and eventually hang out.
> SQL ERRORLog show
> 2005-04-22 07:16:36.45 spid1 LazyWriter: warning, no free buffers
> found.
> 2005-04-22 07:16:36.45 spid1 Buffer Distribution: Stolen=159182
> Free=0
> Procedures=22931
> Inram=0 Dirty=24545 Kept=0
> I/O=0, Latched=2022, Other=0
> 2005-04-22 07:16:36.45 spid1 Buffer Counts: Commited=208680
> Target=208680 Hashed=26567
> InternalReservation=2130 ExternalReservation=57 Min Free=512
> 2005-04-22 07:16:36.45 spid1 Procedure Cache: TotalProcs=3969
> TotalPages=22931 InUsePages=22931
> 2005-04-22 07:16:36.45 spid1 Dynamic Memory Manager: Stolen=182112 OS
> Reserved=2544
> OS Committed=2487
> OS In Use=2468
> Query Plan=166599 Optimizer=3
> General=14803
> Utilities=7 Connection=2910
> 2005-04-22 07:16:36.45 spid1 Global Memory Objects: Resource=11637
> Locks=147
> SQLCache=1236 Replication=2
> LockBytes=2 ServerGlobal=43
> Xact=1862
> 2005-04-22 07:16:36.45 spid1 Query Memory Manager: Grants=1 Waiting=0
> Maximum=13450 Available=13392
> 2005-04-22 07:16:36.70 server Error: 17803, Severity: 20, State: 17
> 2005-04-22 07:16:36.70 server Insufficient memory available..
> I'm currently using SQL Server 2000 Driver for JDBC (with
> SelectMethod=Cursor). From SQL Profiler, I do see alot of sp_cursorfetch
> calls that don't have a corresponding sp_cursorclose.
> Help is greatly appreaciated here!
>

Sunday, March 11, 2012

Error: %1 is not a valid Win32 application

Hi,
This morning I tried to start my MSDE instance like I do everyday. But,
sadly, an error message raised, telling me that '%1 is not a valid Win32
application'.
At this point, as I didn't have anything important at this instance, I
removed the program through the control panel, and reinstalled it. But, when
it was finishing, it raised another error: "The installer could not
configure the server. Read the server's and installer's error registry for
more information".
Searching the directory, I found the cnfgsrv.out:
Iniciando servicio ... (Initiating service...)
Modern_Spanish_CI_AS
-m -Q -T4022 -T3659
Error al intentar iniciar el servicio (193) (Error trying to initiate the
service)
Error de configuracin del servidor SQL Server. (Configuration error of the
SQL Server)
Well, after that, I removed everything related to SQL Server, the Management
Console, the SQL Agent, everything. Deleted all the files, searched the
registry, deleting everything.
Then I reinstalled the MSDE instance again, getting the same error.
Then, I tried to install the SQL Server, but the installer told me that "The
SQL Server 2000 Standard Edition component is not compatible with this
operating system. Only the client components will be available".
My operating system is Windows 2000 Professional.
How can I reinstall SQL Server?
Thanks!!
Arnau.hi Arnau,
Arnau Font wrote:
> Hi,
> This morning I tried to start my MSDE instance like I do everyday.
> But, sadly, an error message raised, telling me that '%1 is not a
> valid Win32 application'.
> At this point, as I didn't have anything important at this instance, I
> removed the program through the control panel, and reinstalled it.
> But, when it was finishing, it raised another error: "The installer
> could not configure the server. Read the server's and installer's
> error registry for more information".
please have a look at
http://support.microsoft.com/defaul...kb;en-us;320873 and
http://support.microsoft.com/defaul...b;EN-US;Q290991 for 2 pieces
of information about properly manually unistall MSDE...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||Thanks Andrea,
I found an useful article at microsoft:
http://support.microsoft.com/defaul...kb;en-us;812486
I had a hidden file at Program Files named 'Microsoft' that didn't allow the
MSDE service to run!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribi en el mensaje
news:3ss810FpikjbU1@.individual.net...
> hi Arnau,
> Arnau Font wrote:
> please have a look at
> http://support.microsoft.com/defaul...kb;en-us;320873 and
> http://support.microsoft.com/defaul...b;EN-US;Q290991 for 2
pieces
> of information about properly manually unistall MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

Error: %1 is not a valid Win32 application

Hi,
This morning I tried to start my MSDE instance like I do everyday. But,
sadly, an error message raised, telling me that '%1 is not a valid Win32
application'.
At this point, as I didn't have anything important at this instance, I
removed the program through the control panel, and reinstalled it. But, when
it was finishing, it raised another error: "The installer could not
configure the server. Read the server's and installer's error registry for
more information".
Searching the directory, I found the cnfgsrv.out:
Iniciando servicio ... (Initiating service...)
Modern_Spanish_CI_AS
-m -Q -T4022 -T3659
Error al intentar iniciar el servicio (193) (Error trying to initiate the
service)
Error de configuración del servidor SQL Server. (Configuration error of the
SQL Server)
Well, after that, I removed everything related to SQL Server, the Management
Console, the SQL Agent, everything. Deleted all the files, searched the
registry, deleting everything.
Then I reinstalled the MSDE instance again, getting the same error.
Then, I tried to install the SQL Server, but the installer told me that "The
SQL Server 2000 Standard Edition component is not compatible with this
operating system. Only the client components will be available".
My operating system is Windows 2000 Professional.
How can I reinstall SQL Server?
Thanks!!
Arnau.hi Arnau,
Arnau Font wrote:
> Hi,
> This morning I tried to start my MSDE instance like I do everyday.
> But, sadly, an error message raised, telling me that '%1 is not a
> valid Win32 application'.
> At this point, as I didn't have anything important at this instance, I
> removed the program through the control panel, and reinstalled it.
> But, when it was finishing, it raised another error: "The installer
> could not configure the server. Read the server's and installer's
> error registry for more information".
please have a look at
http://support.microsoft.com/default.aspx?scid=kb;en-us;320873 and
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991 for 2 pieces
of information about properly manually unistall MSDE...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||Thanks Andrea,
I found an useful article at microsoft:
http://support.microsoft.com/default.aspx?scid=kb;en-us;812486
I had a hidden file at Program Files named 'Microsoft' that didn't allow the
MSDE service to run!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribió en el mensaje
news:3ss810FpikjbU1@.individual.net...
> hi Arnau,
> Arnau Font wrote:
> > Hi,
> >
> > This morning I tried to start my MSDE instance like I do everyday.
> > But, sadly, an error message raised, telling me that '%1 is not a
> > valid Win32 application'.
> >
> > At this point, as I didn't have anything important at this instance, I
> > removed the program through the control panel, and reinstalled it.
> > But, when it was finishing, it raised another error: "The installer
> > could not configure the server. Read the server's and installer's
> > error registry for more information".
> please have a look at
> http://support.microsoft.com/default.aspx?scid=kb;en-us;320873 and
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991 for 2
pieces
> of information about properly manually unistall MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

Error: %1 is not a valid Win32 application

Hi,
This morning I tried to start my MSDE instance like I do everyday. But,
sadly, an error message raised, telling me that '%1 is not a valid Win32
application'.
At this point, as I didn't have anything important at this instance, I
removed the program through the control panel, and reinstalled it. But, when
it was finishing, it raised another error: "The installer could not
configure the server. Read the server's and installer's error registry for
more information".
Searching the directory, I found the cnfgsrv.out:
Iniciando servicio ... (Initiating service...)
Modern_Spanish_CI_AS
-m -Q -T4022 -T3659
Error al intentar iniciar el servicio (193) (Error trying to initiate the
service)
Error de configuracin del servidor SQL Server. (Configuration error of the
SQL Server)
Well, after that, I removed everything related to SQL Server, the Management
Console, the SQL Agent, everything. Deleted all the files, searched the
registry, deleting everything.
Then I reinstalled the MSDE instance again, getting the same error.
Then, I tried to install the SQL Server, but the installer told me that "The
SQL Server 2000 Standard Edition component is not compatible with this
operating system. Only the client components will be available".
My operating system is Windows 2000 Professional.
How can I reinstall SQL Server?
Thanks!!
Arnau.
hi Arnau,
Arnau Font wrote:
> Hi,
> This morning I tried to start my MSDE instance like I do everyday.
> But, sadly, an error message raised, telling me that '%1 is not a
> valid Win32 application'.
> At this point, as I didn't have anything important at this instance, I
> removed the program through the control panel, and reinstalled it.
> But, when it was finishing, it raised another error: "The installer
> could not configure the server. Read the server's and installer's
> error registry for more information".
please have a look at
http://support.microsoft.com/default...b;en-us;320873 and
http://support.microsoft.com/default...;EN-US;Q290991 for 2 pieces
of information about properly manually unistall MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea,
I found an useful article at microsoft:
http://support.microsoft.com/default...b;en-us;812486
I had a hidden file at Program Files named 'Microsoft' that didn't allow the
MSDE service to run!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribi en el mensaje
news:3ss810FpikjbU1@.individual.net...
> hi Arnau,
> Arnau Font wrote:
> please have a look at
> http://support.microsoft.com/default...b;en-us;320873 and
> http://support.microsoft.com/default...;EN-US;Q290991 for 2
pieces
> of information about properly manually unistall MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

Error: %1 is not a valid Win32 application

Hi,
This morning I tried to start my MSDE instance like I do everyday. But,
sadly, an error message raised, telling me that '%1 is not a valid Win32
application'.
At this point, as I didn't have anything important at this instance, I
removed the program through the control panel, and reinstalled it. But, when
it was finishing, it raised another error: "The installer could not
configure the server. Read the server's and installer's error registry for
more information".
Searching the directory, I found the cnfgsrv.out:
Iniciando servicio ... (Initiating service...)
Modern_Spanish_CI_AS
-m -Q -T4022 -T3659
Error al intentar iniciar el servicio (193) (Error trying to initiate the
service)
Error de configuracin del servidor SQL Server. (Configuration error of the
SQL Server)
Well, after that, I removed everything related to SQL Server, the Management
Console, the SQL Agent, everything. Deleted all the files, searched the
registry, deleting everything.
Then I reinstalled the MSDE instance again, getting the same error.
Then, I tried to install the SQL Server, but the installer told me that "The
SQL Server 2000 Standard Edition component is not compatible with this
operating system. Only the client components will be available".
My operating system is Windows 2000 Professional.
How can I reinstall SQL Server?
Thanks!!
Arnau.
hi Arnau,
Arnau Font wrote:
> Hi,
> This morning I tried to start my MSDE instance like I do everyday.
> But, sadly, an error message raised, telling me that '%1 is not a
> valid Win32 application'.
> At this point, as I didn't have anything important at this instance, I
> removed the program through the control panel, and reinstalled it.
> But, when it was finishing, it raised another error: "The installer
> could not configure the server. Read the server's and installer's
> error registry for more information".
please have a look at
http://support.microsoft.com/default...b;en-us;320873 and
http://support.microsoft.com/default...;EN-US;Q290991 for 2 pieces
of information about properly manually unistall MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea,
I found an useful article at microsoft:
http://support.microsoft.com/default...b;en-us;812486
I had a hidden file at Program Files named 'Microsoft' that didn't allow the
MSDE service to run!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribi en el mensaje
news:3ss810FpikjbU1@.individual.net...
> hi Arnau,
> Arnau Font wrote:
> please have a look at
> http://support.microsoft.com/default...b;en-us;320873 and
> http://support.microsoft.com/default...;EN-US;Q290991 for 2
pieces
> of information about properly manually unistall MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

Thursday, March 29, 2012

Error: Data source name not found and No default driver specified

Tuesday, March 27, 2012

Error: Application for .reportproj not installed

Monday, March 26, 2012

Error: 7105, Severity: 22, State: 6

Error: 7105, Severity: 22, State: 6

Error: 7105, Severity: 22, State: 6

Error: 7105, Severity: 22, State: 6

Error: 7105, Severity: 22, State: 6

Error: 7105, Severity: 22, State: 6

Wednesday, March 21, 2012

Error: 18456 Severity: 14, State: 11

Error: 18456 Severity: 14, State: 11

Error: 18456 Severity: 14, State: 10

Error: 18456 Severity: 14, State: 10

Monday, March 19, 2012

Error: 17806, Severity: 20, State: 2

Error: 17803, Severity: 20, State: 17

Error: 17803, Severity: 20, State: 17

Error: 17803, Severity: 20, State: 17

Sunday, March 11, 2012

Error: %1 is not a valid Win32 application

Error: %1 is not a valid Win32 application

Error: %1 is not a valid Win32 application

Error: %1 is not a valid Win32 application

Error while connection

Blog Archive

About Me