Login failed for user '(null)'

Hi,

I am using a Third Party software which depends on my SQL Server 2000 for storing data. When I use Windows Security in my Third Party software, I get the following message in the event viewer of my SQL Server 2000.

Description:

18452:
Login failed for user '(null)'. Reason: Not associated with trusted SQL Server connection.

When I user SA, I do not get the above error.

Any clarifications on the possibilites for getting the error is appreciated.
Also let me know if we can overcome the error without using SA.

I tried the article in http://support.microsoft.com/kb/840219. But it didn't make a difference.

I would check with the third party app. It seems like they are using an account that isn't authorized in SQL Server. It all depends on how they have implemented their connection.|||

Are the application and the SQL Server running on the same machine? If not, are the machines in the same domain?

If you search this forum for the text of the error, you will find additional related threads that may contain hints helpful to you.

Thanks
Laurentiu

|||

check the authentication of your SQL Server. which authentication r u using..

Madhu

|||

Hi Santhosh,

Santhosh Pallikara wrote:

Hi,

I am using a Third Party software which depends on my SQL Server 2000 for storing data. When I use Windows Security in my Third Party software, I get the following message in the event viewer of my SQL Server 2000.

Description:

18452:
Login failed for user '(null)'. Reason: Not associated with trusted SQL Server connection.

When I user SA, I do not get the above error.

Any clarifications on the possibilites for getting the error is appreciated.
Also let me know if we can overcome the error without using SA.

I tried the article in http://support.microsoft.com/kb/840219. But it didn't make a difference.

You have said that when you are using user "SA" you are not getting error, which means application connects using "SQL/Mixed Authentication Mode" , as Madhu said have you check the authentication mode for server , ensure your application connection string uses Windows Authentication based connection string while you are trying with windows users to login in your application refer http://www.connectionstrings.com for connection string and refer http://hemantgirisgoswami.blogspot.com/2006_11_01_hemantgirisgoswami_archive.html to know/change the Authentication Mode of Server.

Hemantgiri S. Goswami

Logical Disk Fragmentation on Database Drive

We are using Disk Keeper Server from Executive Software version 7.0.410.0.
I am trying to minimize the logical fragmentation on the drive where our
database (.MDF) is located.
The problem I am having is that I do not have the drive space to move
the .MDF to another drive in order to defragment.
I have tried to stop the MSSQLSERVER and SQLSERVERAGENT services and
then attempt to defrag without moving the file and this has not been
successful.
I thought I may be doing something wrong with Diskeeper or SQL 2000.
Any thoughts or ideas would be very helpful.
TIA,
-Ben
Ben wrote:
> We are using Disk Keeper Server from Executive Software version
> 7.0.410.0.
> I am trying to minimize the logical fragmentation on the drive where
> our database (.MDF) is located.
> The problem I am having is that I do not have the drive space to move
> the .MDF to another drive in order to defragment.
> I have tried to stop the MSSQLSERVER and SQLSERVERAGENT services and
> then attempt to defrag without moving the file and this has not been
> successful.
> I thought I may be doing something wrong with Diskeeper or SQL 2000.
> Any thoughts or ideas would be very helpful.
> TIA,
> -Ben
Diskeeper requires a good amount of free drive space to best defrag
files. Since the MDF file you are defragging is large (I assume) and
there is little drive space left, Diskeeper appears to be having
trouble. How much free space do you have and how much space is there in
total? Do you know for a fact that the MDF file is heavily fragmented?
You could try shrinking the file using DBCC SHRINKFILE.
Run sp_spaceused on the database in question and see if there is
unallocated space. If so, shrink the file size, defrag, and then expand
the database again from SQL EM before returning the database to
production.
David G.

Logical Disk Fragmentation on Database Drive

We are using Disk Keeper Server from Executive Software version 7.0.410.0.
I am trying to minimize the logical fragmentation on the drive where our
database (.MDF) is located.
The problem I am having is that I do not have the drive space to move
the .MDF to another drive in order to defragment.
I have tried to stop the MSSQLSERVER and SQLSERVERAGENT services and
then attempt to defrag without moving the file and this has not been
successful.
I thought I may be doing something wrong with Diskeeper or SQL 2000.
Any thoughts or ideas would be very helpful.
TIA,
-BenBen wrote:
> We are using Disk Keeper Server from Executive Software version
> 7.0.410.0.
> I am trying to minimize the logical fragmentation on the drive where
> our database (.MDF) is located.
> The problem I am having is that I do not have the drive space to move
> the .MDF to another drive in order to defragment.
> I have tried to stop the MSSQLSERVER and SQLSERVERAGENT services and
> then attempt to defrag without moving the file and this has not been
> successful.
> I thought I may be doing something wrong with Diskeeper or SQL 2000.
> Any thoughts or ideas would be very helpful.
> TIA,
> -Ben
Diskeeper requires a good amount of free drive space to best defrag
files. Since the MDF file you are defragging is large (I assume) and
there is little drive space left, Diskeeper appears to be having
trouble. How much free space do you have and how much space is there in
total? Do you know for a fact that the MDF file is heavily fragmented?
You could try shrinking the file using DBCC SHRINKFILE.
Run sp_spaceused on the database in question and see if there is
unallocated space. If so, shrink the file size, defrag, and then expand
the database again from SQL EM before returning the database to
production.
David G.

Logical Disk Fragmentation on Database Drive

We are using Disk Keeper Server from Executive Software version 7.0.410.0.
I am trying to minimize the logical fragmentation on the drive where our
database (.MDF) is located.
The problem I am having is that I do not have the drive space to move
the .MDF to another drive in order to defragment.
I have tried to stop the MSSQLSERVER and SQLSERVERAGENT services and
then attempt to defrag without moving the file and this has not been
successful.
I thought I may be doing something wrong with Diskeeper or SQL 2000.
Any thoughts or ideas would be very helpful.
TIA,
-BenBen wrote:
> We are using Disk Keeper Server from Executive Software version
> 7.0.410.0.
> I am trying to minimize the logical fragmentation on the drive where
> our database (.MDF) is located.
> The problem I am having is that I do not have the drive space to move
> the .MDF to another drive in order to defragment.
> I have tried to stop the MSSQLSERVER and SQLSERVERAGENT services and
> then attempt to defrag without moving the file and this has not been
> successful.
> I thought I may be doing something wrong with Diskeeper or SQL 2000.
> Any thoughts or ideas would be very helpful.
> TIA,
> -Ben
Diskeeper requires a good amount of free drive space to best defrag
files. Since the MDF file you are defragging is large (I assume) and
there is little drive space left, Diskeeper appears to be having
trouble. How much free space do you have and how much space is there in
total? Do you know for a fact that the MDF file is heavily fragmented?
You could try shrinking the file using DBCC SHRINKFILE.
Run sp_spaceused on the database in question and see if there is
unallocated space. If so, shrink the file size, defrag, and then expand
the database again from SQL EM before returning the database to
production.
David G.