Error 18452

I have created a user (calladmin2) of a database in SQL Server Enterprise
Manager. When I load SQL Query Analyzer and attempt to File->Connect using
this user name I get:
Msg. 18452, Level 16, State 1
Login failed for user 'calladmin2'. reason: Not associated with a trusted
SQL Server connection.
It appears that I cannot connect to this instance of SQL Server, and am not
even getting to the single database to which I gave this new user access
rights. Is this correct?
How do I create the 'trusted SQL Server connection' that SQL Server wants
for this new user calladmin2?
Many thanks.
Andrew,
Here is link to the article about troubleshooting connectivity issues:
http://support.microsoft.com/default...;en-us;827422.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:eVdbwXjsEHA.2808@.TK2MSFTNGP14.phx.gbl...
> I have created a user (calladmin2) of a database in SQL Server Enterprise
> Manager. When I load SQL Query Analyzer and attempt to File->Connect using
> this user name I get:
> Msg. 18452, Level 16, State 1
> Login failed for user 'calladmin2'. reason: Not associated with a trusted
> SQL Server connection.
> It appears that I cannot connect to this instance of SQL Server, and am
not
> even getting to the single database to which I gave this new user access
> rights. Is this correct?
> How do I create the 'trusted SQL Server connection' that SQL Server wants
> for this new user calladmin2?
> Many thanks.
>
|||Thanks. That had the answer -- LoginMode in the registry.
- Andrew
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si > wrote in
message news:%23CMFB4nsEHA.820@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Andrew,
> Here is link to the article about troubleshooting connectivity issues:
> http://support.microsoft.com/default...;en-us;827422.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> www.SolidQualityLearning.com
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:eVdbwXjsEHA.2808@.TK2MSFTNGP14.phx.gbl...
Enterprise[vbcol=seagreen]
using[vbcol=seagreen]
trusted[vbcol=seagreen]
> not
wants
>

Error 18452

I have created a user (calladmin2) of a database in SQL Server Enterprise
Manager. When I load SQL Query Analyzer and attempt to File->Connect using
this user name I get:
Msg. 18452, Level 16, State 1
Login failed for user 'calladmin2'. reason: Not associated with a trusted
SQL Server connection.
It appears that I cannot connect to this instance of SQL Server, and am not
even getting to the single database to which I gave this new user access
rights. Is this correct?
How do I create the 'trusted SQL Server connection' that SQL Server wants
for this new user calladmin2?
Many thanks.Andrew,
Here is link to the article about troubleshooting connectivity issues:
http://support.microsoft.com/defaul...b;en-us;827422.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:eVdbwXjsEHA.2808@.TK2MSFTNGP14.phx.gbl...
> I have created a user (calladmin2) of a database in SQL Server Enterprise
> Manager. When I load SQL Query Analyzer and attempt to File->Connect using
> this user name I get:
> Msg. 18452, Level 16, State 1
> Login failed for user 'calladmin2'. reason: Not associated with a trusted
> SQL Server connection.
> It appears that I cannot connect to this instance of SQL Server, and am
not
> even getting to the single database to which I gave this new user access
> rights. Is this correct?
> How do I create the 'trusted SQL Server connection' that SQL Server wants
> for this new user calladmin2?
> Many thanks.
>|||Thanks. That had the answer -- LoginMode in the registry.
- Andrew
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:%23CMFB4nsEHA.820@.TK2MSFTNGP12.phx.gbl...
> Andrew,
> Here is link to the article about troubleshooting connectivity issues:
> http://support.microsoft.com/defaul...b;en-us;827422.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> www.SolidQualityLearning.com
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:eVdbwXjsEHA.2808@.TK2MSFTNGP14.phx.gbl...
Enterprise[vbcol=seagreen]
using[vbcol=seagreen]
trusted[vbcol=seagreen]
> not
wants[vbcol=seagreen]
>

Error 14258: ... SQL ServerAgent is starting

Whenever I attempt to edit/run/... a scheduled job, I get the error message:
"Error 14258: Cannot perform this operation while SQL ServerAgent is
starting. Try again later."
I also notice that all scheduled jobs have "Date/time not available" in
"Next Run Date".
Of course Agent is not starting now, it has already started (Alerts and
Operators can be edited without a problem). The server is SQL2000, SP4.
Check the status of the service from Administrative Tools -
is the service Running or Starting?
Alerts and operators can be edited without Agent running.
Also check your Agent.out file.
-Sue
On Thu, 16 Feb 2006 03:55:29 -0800, "vsiat"
<vsiat@.discussions.microsoft.com> wrote:

>Whenever I attempt to edit/run/... a scheduled job, I get the error message:
>"Error 14258: Cannot perform this operation while SQL ServerAgent is
>starting. Try again later."
>I also notice that all scheduled jobs have "Date/time not available" in
>"Next Run Date".
>Of course Agent is not starting now, it has already started (Alerts and
>Operators can be edited without a problem). The server is SQL2000, SP4.
|||The service IS running. I restarted it to make sure though, as I also did
with the server and the machine; nothing worked. The service is reported to
be running in both enterprise manager and windows services but no scheduled
jobs can be edited/run/...etc.
Also, when I stop the service I can edit jobs or create new ones, but there
is no way to run them.
There is no Agent.out file.
"Sue Hoegemeier" wrote:

> Check the status of the service from Administrative Tools -
> is the service Running or Starting?
> Alerts and operators can be edited without Agent running.
> Also check your Agent.out file.
> -Sue
|||ok, I checked SQLAgent.out file. It has one entry:
"... ? [393] Waiting for SQL Server to recover databases..."
but I don't understand which databases it is recovering as there is no such
indication in SQL server logs or Current activity.
"Sue Hoegemeier" wrote:

> Check the status of the service from Administrative Tools -
> is the service Running or Starting?
> Alerts and operators can be edited without Agent running.
> Also check your Agent.out file.
> -Sue
|||If you tried stopping and then restarting just the Agent
service and it won't start, reporting the same error then my
guess would be that you are running SQL Server in
lightweight pooling mode. Set it back to the default of
thread mode.
sp_configure 'allow updates', 1
go
reconfigure with override
go
sp_configure 'lightweight pooling', 0
go
reconfigure with override
go
-Sue
On Fri, 17 Feb 2006 00:41:28 -0800, "vsiat"
<vsiat@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>ok, I checked SQLAgent.out file. It has one entry:
>"... ? [393] Waiting for SQL Server to recover databases..."
>but I don't understand which databases it is recovering as there is no such
>indication in SQL server logs or Current activity.
>
>"Sue Hoegemeier" wrote:

Error "An attempt to attach an auto-named database for file"

Hello,

I have seen some solutions of which I tried on this form for the error I am receiving, but I still cannot get the issue resolved.

Here is my case:

I developed an app using SQL Express as the local data source. I published it to my server using the Once Click install feature. When I look in my project viewer, under settings, My db connection strings are listed as follows: Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\TAP_Master.mdf;Integrated Security=True;User Instance=True

From another computer, I navigate to the publish site, install and run the application with no problems. I have on another computer, the same app with an updated version number that I wish to publish, however the difference is is that this published version does not include the database as I do not want the end user to overwrite any existing data that they may have from the previous version.

I publish the updated version, install it but when the app runs, I receive the message, "An attempt to attach an auto-named database for file".

Any suggestions?

Thanks in advance.

Rashar wrote:

I have on another computer, the same app with an updated version number that I wish to publish, however the difference is is that this published version does not include the database as I do not want the end user to overwrite any existing data that they may have from the previous version.

Please explain what this means. What do you mean by "another computer" is this a different computer than your development computer and the end-user computer? How did you create this updated version of the application, did you just remove the database or did you create a copy of the project?

When you install this "update" is it really updating the original deployment or is it installing a completely separate copy of the program?

Shrot answer: I don't think ClickOnce works like this from a VS perspective. I know it doesn't work like this from a SQL perspective. If you remove the database from your project and redeploy, I believe the database will actually be removed. (I say "belive" because I've never tried this.) You might want to consider an alternate way to deploy your database, I've documented one alternative in my blog, start with this post.

Mike

|||

Yes... It is a different computer from my development computer. Basically, I have the same code on both the development pc and the other pc... The reason being is that on my development pc, I would publish the entire app the database included. The problem I ran in to was if I made a change to the database on the development PC, published it, then have the client pc update their app, it would for some reason give them a new database overwriting any existintg data. It actually worked for me this way, until I decided to establish 2 different publishing locations, and I think that is where my problem lies.

Thanks for your reply and advice Mike!

Regards.

|||

I found the problem. When I published the second time around, the publish created an empty folder under C:\Documents and Settings\username\Local Settings\Apps\2.0.

So I just copied my database into that folder and it worked.

|||

I hadt he same problem en found thefollowing sollution:

This is what I found in web.config

<connectionStrings>

<add name="JopieString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\Joop.mdf;Integrated Security=True;User Instance=True"

providerName="System.Data.SqlClient" />

</connectionStrings>

|DataDirectory| is the directory of visual webdeveloper.

Delete this and type the name of the path in which your database is stored (in my case c:\inetpub\wwwroot\etc.)

<connectionStrings>

<add name="JopieString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=C:\inetpub\wwwroot\App_Data\Joop.mdf;Integrated Security=True;User Instance=True"

providerName="System.Data.SqlClient" />

</connectionStrings>

This solved the problem for me, I hope it also solves yours.

Error "An attempt to attach an auto-named database for file"

Hello,

I have seen some solutions of which I tried on this form for the error I am receiving, but I still cannot get the issue resolved.

Here is my case:

I developed an app using SQL Express as the local data source. I published it to my server using the Once Click install feature. When I look in my project viewer, under settings, My db connection strings are listed as follows: Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\TAP_Master.mdf;Integrated Security=True;User Instance=True

From another computer, I navigate to the publish site, install and run the application with no problems. I have on another computer, the same app with an updated version number that I wish to publish, however the difference is is that this published version does not include the database as I do not want the end user to overwrite any existing data that they may have from the previous version.

I publish the updated version, install it but when the app runs, I receive the message, "An attempt to attach an auto-named database for file".

Any suggestions?

Thanks in advance.

Rashar wrote:

I have on another computer, the same app with an updated version number that I wish to publish, however the difference is is that this published version does not include the database as I do not want the end user to overwrite any existing data that they may have from the previous version.

Please explain what this means. What do you mean by "another computer" is this a different computer than your development computer and the end-user computer? How did you create this updated version of the application, did you just remove the database or did you create a copy of the project?

When you install this "update" is it really updating the original deployment or is it installing a completely separate copy of the program?

Shrot answer: I don't think ClickOnce works like this from a VS perspective. I know it doesn't work like this from a SQL perspective. If you remove the database from your project and redeploy, I believe the database will actually be removed. (I say "belive" because I've never tried this.) You might want to consider an alternate way to deploy your database, I've documented one alternative in my blog, start with this post.

Mike

|||

Yes... It is a different computer from my development computer. Basically, I have the same code on both the development pc and the other pc... The reason being is that on my development pc, I would publish the entire app the database included. The problem I ran in to was if I made a change to the database on the development PC, published it, then have the client pc update their app, it would for some reason give them a new database overwriting any existintg data. It actually worked for me this way, until I decided to establish 2 different publishing locations, and I think that is where my problem lies.

Thanks for your reply and advice Mike!

Regards.

|||

I found the problem. When I published the second time around, the publish created an empty folder under C:\Documents and Settings\username\Local Settings\Apps\2.0.

So I just copied my database into that folder and it worked.

|||

I hadt he same problem en found thefollowing sollution:

This is what I found in web.config

<connectionStrings>

<add name="JopieString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\Joop.mdf;Integrated Security=True;User Instance=True"

providerName="System.Data.SqlClient" />

</connectionStrings>

|DataDirectory| is the directory of visual webdeveloper.

Delete this and type the name of the path in which your database is stored (in my case c:\inetpub\wwwroot\etc.)

<connectionStrings>

<add name="JopieString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=C:\inetpub\wwwroot\App_Data\Joop.mdf;Integrated Security=True;User Instance=True"

providerName="System.Data.SqlClient" />

</connectionStrings>

This solved the problem for me, I hope it also solves yours.