Connect fails: Error 4064, Can not open user default DB

I just installed SQL Server 2005 CTP (9.00.1116) on Windows Server 2003 with SP1. Then I unzipped DotNetNuke portal site and tried to connect to it with various errors, generally relating to invalid login.

I never figured it out after many hours of exploring every SQL interface I could find, changing web.config's connection string, and editing the DotNetNuke ODBC Data Source. At one point I was able to intermittently sign in to the SQL Server Management Studio (but never to get DotNetNuke site to connect to the DB).

Late in this process I gave up, decided to reinstall DotNetNuke from scratch, and removed that directory with my default database. Maybe one isn't supposed to do this, but I did it and suspect that is the reason for the error message in the title of this post. I don't see a way to login in as another user either at this point.

If it is indeed possible for one to delete one's default database - and if so - is there any solution except a complete (multi-hour on my old system) reinstall of SQL Server?

If I try to connect using SQL user SA (user names are case insensative, right?!), I get error 18452: "The user is not associated with a trusted SQL Server Connection."

You can change default database for a user using ALTER LOGIN. You can check your current settings for all users using sys.server_principals.

As far as being unable to connect using ‘sa’ credentials, verify that you have mixed mode authentication enabled. If you do not that might explain why you are getting trusted connection error for ‘sa’.

This may also be affecting your inability to connect to the portal.

Overall, it is recommended that you upgrade to CTP 15 (build 1187), so reinstall might be the cleanest option. Make sure you select ‘mixed mode auth’ and set ‘sa’ password during setup.

Regards,

Boris.

|||Boris B is right , I had the same problem when i started using it and it turned out to be the default database i hat for the specific login .

Connect fails: Error 4064, Can not open user default DB

I just installed SQL Server 2005 CTP (9.00.1116) on Windows Server 2003 with SP1. Then I unzipped DotNetNuke portal site and tried to connect to it with various errors, generally relating to invalid login.

I never figured it out after many hours of exploring every SQL interface I could find, changing web.config's connection string, and editing the DotNetNuke ODBC Data Source. At one point I was able to intermittently sign in to the SQL Server Management Studio (but never to get DotNetNuke site to connect to the DB).

Late in this process I gave up, decided to reinstall DotNetNuke from scratch, and removed that directory with my default database. Maybe one isn't supposed to do this, but I did it and suspect that is the reason for the error message in the title of this post. I don't see a way to login in as another user either at this point.

If it is indeed possible for one to delete one's default database - and if so - is there any solution except a complete (multi-hour on my old system) reinstall of SQL Server?

If I try to connect using SQL user SA (user names are case insensative, right?!), I get error 18452: "The user is not associated with a trusted SQL Server Connection."

You can change default database for a user using ALTER LOGIN. You can check your current settings for all users using sys.server_principals.

As far as being unable to connect using ‘sa’ credentials, verify that you have mixed mode authentication enabled. If you do not that might explain why you are getting trusted connection error for ‘sa’.

This may also be affecting your inability to connect to the portal.

Overall, it is recommended that you upgrade to CTP 15 (build 1187), so reinstall might be the cleanest option. Make sure you select ‘mixed mode auth’ and set ‘sa’ password during setup.

Regards,

Boris.

|||Boris B is right , I had the same problem when i started using it and it turned out to be the default database i hat for the specific login .

Configuring Database mail with SMTP authentication

I try to configure database mail on SQL Server 2005 (June CTP)
All the services are running under the same domain account which has been also added to corporate Exchange server. When creating a database mail account on SQL Server, I check the "SMTP server requires authentication" check box and enter the account name and paassword. When trying to apply the changes I get the following error:
"An error occured during decryption (Microsoft SQL Server, Error 15466)"

Is there any workaround on this error?

Thanks.
Artem

Check this thread:

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1905071&SiteID=17

Configuring Database mail with SMTP authentication

I try to configure database mail on SQL Server 2005 (June CTP)
All the services are running under the same domain account which has been also added to corporate Exchange server. When creating a database mail account on SQL Server, I check the "SMTP server requires authentication" check box and enter the account name and paassword. When trying to apply the changes I get the following error:
"An error occured during decryption (Microsoft SQL Server, Error 15466)"

Is there any workaround on this error?

Thanks.
Artem

Check this thread:

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1905071&SiteID=17

Configuring Database Mail in Sept 05 version

I had no problems whatsoever configuring Database Mail in the April CTP.

In the September version, when I try to configure mail on a new (not an upgraded) server, I run into the following:

-- Set up Database Mail
-- trying to add profile, click on ADD to add an account, I get a:

Microsoft.SqlServer.Management.Common.ExecutionFailureException: An exception occurred while executing a Transact-SQL statement or batch. > System.Data.SqlClient.SqlException: Insert Error: Column name or number of supplied values does not match table definition.

I profiled it, and the setup tries to execute a script:
create table #tmp_sysmail_help_account(account_id int, name nvarchar(128), description nvarchar(256) null, email_address nvarchar(128) null, display_name nvarchar(128) null, replyto_address nvarchar(128) null, servertype nvarchar(128), servername nvarchar(128), port int, username nvarchar(128))

insert into #tmp_sysmail_help_account(account_id, name, description, email_address, display_name, replyto_address, servertype, servername, port, username) exec msdb.dbo.sysmail_help_account_sp

Which does not work since msdb.dbo.sysmail_help_account_sp returns 2 fields that are not accounted for in the temp table: user_default_credentials, and enable_ssl.

I altered the procedure to work, which gets me to the 'add account', but adding an will fail with:

TITLE: Microsoft SQL Server

This wizard will close because it encountered the following error:

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1187.07&EvtSrc=Microsoft.SqlServer.Management.UI.WizardFrameworkErrorSR&EvtID=UncaughtException&LinkId=20476

ADDITIONAL INFORMATION:

Object reference not set to an instance of an object. (DatabaseMailWizard)

So it seems like the database mail install is completely shot.... Is anyone else having this problem?

thanks.

ok -- found the problem.

was trying to configure Database Mail on the September version using client tools from the April version ( oops )

;)