Cannot open user default database, login fails

hi:
I got the problem, which lots of people might encounter before.

In my case, I use login control and sqlexpress to build a login page.
when password & user name were entered. It gave me:
"Cannot open user default database, login fails"

The solution given by msdn is:

SQL Server 2005

You can use the sqlcmd utility to change the default database in SQL Server 2005. To do this, follow these steps:

1.Click Start, click Run, type cmd, and then press ENTER. 2.Use one of the following methods, depending on the kind of authentication that the SQL Server login uses:

?If

the SQL Server login uses Microsoft Windows authentication to connect

to the instance, type the following at the command prompt, and then

press ENTER:

sqlcmd –E -S InstanceName –d master

?If

the SQL Server login uses SQL Server authentication to connect to the

instance, type the following at the command prompt, and then press

ENTER:

sqlcmd -S InstanceName -d master -U SQLLogin -P Password

Note InstanceName is a placeholder for the name of the SQL Server 2005 instance to which you are connecting. SQLLogin is a placeholder for the SQL Server login whose default database has been dropped. Password is a placeholder for the SQL Server login password.3.At the sqlcmd prompt, type the following, and then press ENTER:

ALTER LOGIN SQLLogin WITH DEFAULT_DATABASE = AvailDBName

Note AvailDBName is a placeholder for the name of the existing database that can be accessed by the SQL Server login in the instance.4.At the sqlcmd prompt, type GO, and then press ENTER.

I wonder what are InstanceName, SQLLogin & AvailDBName. It would be nice if someone can give me a specific example, since I am not sure how to type them in a command line. :)

You're in the wrong forum. Try here: http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=84&SiteID=1

-Jamie

Cannot open database requested in login '-u'

How do I fix this error:
Cannot open database requested in login '-u'. Login fails. Login
failed for user 'INTERN3\ASPNET'.
I was trying to fix a rsFailedToDecryptConfigInformation error and did
something like "rsconfig -c -s intern3 -d -u IUSR_INTERN3 -a Windows".
Now, I can't view any reports. I just get the above error. I tried
"rsconfig -c -s intern3 -d -u ASPNET -a Windows", but no luck.
I'd rather not reinstall. Please help...Do I need to reinstall'|||No, you do not need to reinstall. You most likely don't want to use the
ASPNET account to talk to the DB. Instead you should use either a low
privlage sql account or domain account. Is your SQL server on the same box?
If not then the ASPNET account is not known to the sql box.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Steven" <montgoss@.hotmail.com> wrote in message
news:a73f4c07.0408160516.7bb409fd@.posting.google.com...
> Do I need to reinstall'

Cannot open database requested in login 'northwind'. Login fails.

I work for DataDirect-Technologies. My customer is using our Connect for ODBC
5.00.0059 driver on Solaris 8 to connect to SQL Server 7 on Win 2000. When he
tries to connect using a simple C application he gets the error
"[DataDirect][ODBC SQL Server Driver][SQL Server]Cannot open database
requested in login 'northwind'. Login fails." The customer has tried using
the IP Address and the machine name. He has tried connecting to Northwind and
Master. He is using the sa login with a password. He is able to connect with
the same information from a Windows machine either using Windows
Authentication or SQL Server authentication.
There must be some setting within his SQL Server database that does not
allow remote connections, is anyone aware of something like this?
Actually, to update the issue: the customer can connect from a remote Windows
client to his SQL Server 7 database using the MS ODBC driver. However, if he
takes that same data source on his remote Windows client and changes the
connection info to point to the machine name and port number of the Solaris
box where a TCP/IP packet sniffer
(ftp://ftp.datadirect.com/download/da...ools/snoop.jar) is running and
the packet sniffer re-routes the connection to the SQL Server database, he
sees the same error that he gets with the DataDirect ODBC driver on Solaris.
So it appears that SQL Server must be configured only to disallow connections
coming from that Solaris machine, not necessarily all remote connections.
Does anyone know what setting is controlling this?
"Pat Frost" wrote:

> I work for DataDirect-Technologies. My customer is using our Connect for ODBC
> 5.00.0059 driver on Solaris 8 to connect to SQL Server 7 on Win 2000. When he
> tries to connect using a simple C application he gets the error
> "[DataDirect][ODBC SQL Server Driver][SQL Server]Cannot open database
> requested in login 'northwind'. Login fails." The customer has tried using
> the IP Address and the machine name. He has tried connecting to Northwind and
> Master. He is using the sa login with a password. He is able to connect with
> the same information from a Windows machine either using Windows
> Authentication or SQL Server authentication.
> There must be some setting within his SQL Server database that does not
> allow remote connections, is anyone aware of something like this?

Cannot open database requested in login 'northwind'. Login fails.

I work for DataDirect-Technologies. My customer is using our Connect for ODB
C
5.00.0059 driver on Solaris 8 to connect to SQL Server 7 on Win 2000. When h
e
tries to connect using a simple C application he gets the error
"[DataDirect][ODBC SQL Server Driver][SQL Server]Cannot open dat
abase
requested in login 'northwind'. Login fails." The customer has tried using
the IP Address and the machine name. He has tried connecting to Northwind an
d
Master. He is using the sa login with a password. He is able to connect with
the same information from a Windows machine either using Windows
Authentication or SQL Server authentication.
There must be some setting within his SQL Server database that does not
allow remote connections, is anyone aware of something like this?Actually, to update the issue: the customer can connect from a remote Window
s
client to his SQL Server 7 database using the MS ODBC driver. However, if he
takes that same data source on his remote Windows client and changes the
connection info to point to the machine name and port number of the Solaris
box where a TCP/IP packet sniffer
(ftp://ftp.datadirect.com/download/d...tools/snoop.jar) is running an
d
the packet sniffer re-routes the connection to the SQL Server database, he
sees the same error that he gets with the DataDirect ODBC driver on Solaris.
So it appears that SQL Server must be configured only to disallow connection
s
coming from that Solaris machine, not necessarily all remote connections.
Does anyone know what setting is controlling this?
"Pat Frost" wrote:

> I work for DataDirect-Technologies. My customer is using our Connect for O
DBC
> 5.00.0059 driver on Solaris 8 to connect to SQL Server 7 on Win 2000. When
he
> tries to connect using a simple C application he gets the error
> "[DataDirect][ODBC SQL Server Driver][SQL Server]Cannot open d
atabase
> requested in login 'northwind'. Login fails." The customer has tried using
> the IP Address and the machine name. He has tried connecting to Northwind
and
> Master. He is using the sa login with a password. He is able to connect wi
th
> the same information from a Windows machine either using Windows
> Authentication or SQL Server authentication.
> There must be some setting within his SQL Server database that does not
> allow remote connections, is anyone aware of something like this?

Cannot open database requested in login dbName. Login fails. Login failed for user machine

Been looking through the forums for a solution to this problem.
I already tried granting access through statements such as:
exec sp_grantloginaccess N1'machineName\ASPNET'
But they don't seem to work.. i vaguely remember seeing somewhere a DOS command line statement that grants access to the ASPNET_WP and that fixed my problem before on another computer.. but this is a new computer and i forgot to write down the command.
Can anyone help explain and propose a solution to my problem. Many thanxs.

osql -E -SInstanceName -C -Q "sp_grantlogin 'computer\ASPNET'"
osql -E -SInstanceName -ddatabase -Q "sp_grantdbaccess 'computer\ASPNET'"
osql -E -SInstanceName -ddatabase -Q "sp_addrolemember 'db_owner', 'computer\ASPNET'"InstanceName -C -Q "sp_grantlogin 'computer\ASPNET'"
InstanceName is optional if you only installed the default instance.
|||You need to grant login permissions to the ASPNET account as well asdatabase permissions. Do you have Enterprise Manager? Thiswould help you to set permissions using a GUI tool. Assuming youdo not, then you could use the osql commandline utility. I amalso further assuming this is a local instance of SQL Server.
Usingosql, from the command prompt, this will connect you to your instanceof SQL Server and put you into an interactive mode with osql:

osql -E -S (local)

Now you can enter the commands in the interactive mode:

1>EXEC sp_grantlogin 'machineName\ASPNET'

2>GO

1>USE yourDatabase

2>GO

1>EXEC sp_grantdbaccess 'machineName\ASPNET'

2>GO

1>EXIT

Edit: sorry, didn't see Darrell's post :-)
|||That just shows there's more than one way to do it!
|||Thanxs '%orton'
I went with tmorton's instructions because it looked easier and more straightforward. I enabled me to get my app running after a few minor adjustments. I described what I did below but don't fully understand why it worked. Could you please help clarify?
I was able to grantlogin to 'machineName\ASPNET', however, got an error stating that permissions already existed for 'machineName\ASPNET' when I tried to grantdbaccess. I do have EnterpriseManager and went into the Users of the database I needed to use. I deleted the 'machineName\ASPNET' from that list. Then ran the sp_grantdbaccess 'machineName\ASPNET' again. This time succeeding. Thus my application has permissions to run. But when I went back ino the database/users, I didn't see 'machineName\ASPNET' in the User list. Why is that?
Where can I look to see the results of executing the sp_grantlogin & sp_grantdbaccess? Shouldn't there be a list for that somewhere?
And just to make sure that I understand what is happening. The sp_grantlogin simply gives the user 'machineName\ASPNET' permission to login into the SQLServer (1st level). Then sp_grantdbacess gives the user 'machineName\ASPNET' permission to access the specified database (from the use yourDatabase)
Thanxs again!!!|||After referring someone else to this post I realized that I never answered your questions. I am sorry!

MEight wrote:

Thanxs '%orton'
I was able to grantlogin to'machineName\ASPNET', however, got an error stating that permissionsalready existed for 'machineName\ASPNET' when I tried to grantdbaccess.

Then you really didn't need to do anything further with *that* command.

MEight wrote:

I do have EnterpriseManager<snip>
But when I wentback ino the database/users, I didn't see 'machineName\ASPNET' in theUser list. Why is that?

Enterprise Manager is not good about refreshing data. Eitherclose Enterprise Manager completely and reopen it, or start at yourserver right-clicking and choosing Refresh on each node all of the waydown until you get to the node for the data you are concernedwith.

MEight wrote:

Where can I look to see the results ofexecuting the sp_grantlogin & sp_grantdbaccess? Shouldn't there bea list for that somewhere?

You can see this in Enterprise Manager (after forcing the data to refresh), or you can execute thesp_helplogins system stored procedure from Query Analyzer (or the osql commandline utility):

EXEC sp_helplogins

MEight wrote:

And just to make sure that Iunderstand what is happening. The sp_grantlogin simply gives the user'machineName\ASPNET' permission to login into the SQLServer (1stlevel). Then sp_grantdbacess gives the user 'machineName\ASPNET'permission to access the specified database (from the use yourDatabase)

Yes, you've got it! You can read up on what MSDN has to say aboutsp_grantlogin andsp_grantdbaccess for more information.
If you haven't done so already, you should installSQL Server 2000 Books Online. This is a great free SQL Server reference.


|||

i can not do anything with sql. This is what i got :

----------------------------

C:\Users\User>osql -E -S
[SQL Native Client]VIA Provider: The specified module could not be found.
[SQL Native Client]Login timeout expired
[SQL Native Client]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.

---------------------------

also, i cant create database directly from SQL Server Management Studio Express!

the error is The permission denied in database 'master'. What should i do?

Cannot open database requested in login . Login fails.

Hey gang. Trying to figure out where to start troubleshooting this error message while my boss (he who is better with SQL Server than I am) is on vacation. Can someone point me in the right direction?

I'm getting the "Cannot open database requested in login '--'. Login fails." error on a query to a MS-SQL database in a ColdFusion app. Can't even make it go with the sa user. I know the login and password are just fine; when I give it a different, incorrect password, the error message is different ("Login failed for user 'sa'."). Also, I'm able to get into the console and run my query via Enterprise Manager with no problem.

For what it's worth, my boss re-created this database right before he left and I'm thinking he just missed setting a property somewhere; on the old version of the database this ColdFusion page and this query worked fine under the same username/pass.

Any suggestions? Hope this isn't too incoherent.Are you connecting via ODBC? I sometimes get this error message if the default database is improperly set in the ODBC source.

Dirk|||Via a ColdFusion ODBC datasource--all the settings there look good.|||Hey Sapphireblue,

This article can be helpful, I experienced the same problem with my app.
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B283860

Cannot install Workstation components, fails on report server upgrade

I have hard time installing July CTP as it is failing on workstation component and fails on report server upgrade.

Any ideas for ther resolution.

Property(S): AdministratorsGroup = BUILTIN\Administrators
Property(S): PerformanceMontiorUsersGroup = BUILTIN\Performance Monitor Users
Property(S): PerformanceLogUsersGroup = BUILTIN\Performance Log Users
Property(S): UsersGroup = BUILTIN\Users
Property(S): SCMNetworkServiceAccount = NT AUTHORITY\NetworkService
Property(S): SCMLocalServiceAccount = NT AUTHORITY\LocalService
Property(S): IISCHECKED = 1
Property(S): SqlIISInstalled = 1
Property(S): SqlASPNETInstalled = 1
Property(S): SqlCOMPlusInstalled = 1
Property(S): RSPREREQUISITECHECKED = 1
Property(S): RSSqlPoolLimit = 100
Property(S): RSGUIDVALUE = {ec3b61d7-2813-485b-a55d-e0c931740946}
Property(S): RemoveFeatureList = Client_Components,Connectivity,SQL_Tools,SQL_WarehouseDevWorkbench,SDK,SQLXML,Tools_Legacy,TOOLS_BC_DEP,SQL_Documentation,SQL_Samples,SQL_BooksOnline,SQL_DatabaseSamples
Property(S): SqlOriginalMachineName = TAHITI
Property(S): Namechecksumcommon_32 = Developer Edition
Property(S): SqlSubDir = \MSSQL
Property(S): EditionTypechecksumcommon_32 = Developer Edition
Property(S): Namechecksumtools = Developer Edition
Property(S): EditionTypechecksumtools = Developer Edition
Property(S): ValidMOFInstanceName = 1
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer
Property(S): RSVirtualDirectoryManager = Reports
Property(S): SQLStatusBeforeInstall = 3
Property(S): SOURCEDIR = Z:\Tools\Setup\
Property(S): SourcedirProduct = {D6251ACA-3FD4-49D1-8FCF-182B980B19E3}
Property(S): HxDs_Tmp_3643236F_FC70_11D3_A536_0090278A1BB8 = C:\DOCUME~1\abahl\LOCALS~1\Temp\HxEA.tmp
Property(S): HxDs_Tmp_Hash_3643236F_FC70_11D3_A536_0090278A1BB8 = B40B0DC6C3C19C68E0101E0E2A647F0C3A18F6
Property(S): InstallNgenTicks = 1750000
Property(S): ProductToBeRegistered = 1
MSI (s) (38:20) [17:31:47:165]: Note: 1: 1708
MSI (s) (38:20) [17:31:47:165]: Product: Microsoft SQL Server 2008 Tools -- Installation failed.

You shouldn't be able to upgrade your report server. We don't support upgrade in the July CTP. Can you install a new instance?|||

No I am not trying to upgrade, but trying to install a clean install on windows 2003 box and I cannot.

Any thoughts, ideas.

Atul

|||What if you don't install the workstation tools? Just install the Report Server and see if you can configure it. Can you install the relational database by itself?|||

I am able to install the report server as well as the db from the looks of it.

But since management studio does not gets installed, I cannot verify or do anything with the DB.

I need to evaluate reporting services so it is very crucial to get this up and running.

Atul

|||You don't need Management Studio to use Reporting Services. But if you really need it on this machine, I would recommend you post the question over in the Katmai setup forum.

Cannot install Workstation components, fails on report server upgrade

I have hard time installing July CTP as it is failing on workstation component and fails on report server upgrade.

Any ideas for ther resolution.

Property(S): AdministratorsGroup = BUILTIN\Administrators
Property(S): PerformanceMontiorUsersGroup = BUILTIN\Performance Monitor Users
Property(S): PerformanceLogUsersGroup = BUILTIN\Performance Log Users
Property(S): UsersGroup = BUILTIN\Users
Property(S): SCMNetworkServiceAccount = NT AUTHORITY\NetworkService
Property(S): SCMLocalServiceAccount = NT AUTHORITY\LocalService
Property(S): IISCHECKED = 1
Property(S): SqlIISInstalled = 1
Property(S): SqlASPNETInstalled = 1
Property(S): SqlCOMPlusInstalled = 1
Property(S): RSPREREQUISITECHECKED = 1
Property(S): RSSqlPoolLimit = 100
Property(S): RSGUIDVALUE = {ec3b61d7-2813-485b-a55d-e0c931740946}
Property(S): RemoveFeatureList = Client_Components,Connectivity,SQL_Tools,SQL_WarehouseDevWorkbench,SDK,SQLXML,Tools_Legacy,TOOLS_BC_DEP,SQL_Documentation,SQL_Samples,SQL_BooksOnline,SQL_DatabaseSamples
Property(S): SqlOriginalMachineName = TAHITI
Property(S): Namechecksumcommon_32 = Developer Edition
Property(S): SqlSubDir = \MSSQL
Property(S): EditionTypechecksumcommon_32 = Developer Edition
Property(S): Namechecksumtools = Developer Edition
Property(S): EditionTypechecksumtools = Developer Edition
Property(S): ValidMOFInstanceName = 1
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer
Property(S): RSVirtualDirectoryManager = Reports
Property(S): SQLStatusBeforeInstall = 3
Property(S): SOURCEDIR = Z:\Tools\Setup\
Property(S): SourcedirProduct = {D6251ACA-3FD4-49D1-8FCF-182B980B19E3}
Property(S): HxDs_Tmp_3643236F_FC70_11D3_A536_0090278A1BB8 = C:\DOCUME~1\abahl\LOCALS~1\Temp\HxEA.tmp
Property(S): HxDs_Tmp_Hash_3643236F_FC70_11D3_A536_0090278A1BB8 = B40B0DC6C3C19C68E0101E0E2A647F0C3A18F6
Property(S): InstallNgenTicks = 1750000
Property(S): ProductToBeRegistered = 1
MSI (s) (38:20) [17:31:47:165]: Note: 1: 1708
MSI (s) (38:20) [17:31:47:165]: Product: Microsoft SQL Server 2008 Tools -- Installation failed.

You shouldn't be able to upgrade your report server. We don't support upgrade in the July CTP. Can you install a new instance?|||

No I am not trying to upgrade, but trying to install a clean install on windows 2003 box and I cannot.

Any thoughts, ideas.

Atul

|||What if you don't install the workstation tools? Just install the Report Server and see if you can configure it. Can you install the relational database by itself?|||

I am able to install the report server as well as the db from the looks of it.

But since management studio does not gets installed, I cannot verify or do anything with the DB.

I need to evaluate reporting services so it is very crucial to get this up and running.

Atul

|||You don't need Management Studio to use Reporting Services. But if you really need it on this machine, I would recommend you post the question over in the Katmai setup forum.

Cannot install Workstation components, fails on report server upgrade

I have hard time installing July CTP as it is failing on workstation component and fails on report server upgrade.

Any ideas for ther resolution.

Property(S): AdministratorsGroup = BUILTIN\Administrators
Property(S): PerformanceMontiorUsersGroup = BUILTIN\Performance Monitor Users
Property(S): PerformanceLogUsersGroup = BUILTIN\Performance Log Users
Property(S): UsersGroup = BUILTIN\Users
Property(S): SCMNetworkServiceAccount = NT AUTHORITY\NetworkService
Property(S): SCMLocalServiceAccount = NT AUTHORITY\LocalService
Property(S): IISCHECKED = 1
Property(S): SqlIISInstalled = 1
Property(S): SqlASPNETInstalled = 1
Property(S): SqlCOMPlusInstalled = 1
Property(S): RSPREREQUISITECHECKED = 1
Property(S): RSSqlPoolLimit = 100
Property(S): RSGUIDVALUE = {ec3b61d7-2813-485b-a55d-e0c931740946}
Property(S): RemoveFeatureList = Client_Components,Connectivity,SQL_Tools,SQL_WarehouseDevWorkbench,SDK,SQLXML,Tools_Legacy,TOOLS_BC_DEP,SQL_Documentation,SQL_Samples,SQL_BooksOnline,SQL_DatabaseSamples
Property(S): SqlOriginalMachineName = TAHITI
Property(S): Namechecksumcommon_32 = Developer Edition
Property(S): SqlSubDir = \MSSQL
Property(S): EditionTypechecksumcommon_32 = Developer Edition
Property(S): Namechecksumtools = Developer Edition
Property(S): EditionTypechecksumtools = Developer Edition
Property(S): ValidMOFInstanceName = 1
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer
Property(S): RSVirtualDirectoryManager = Reports
Property(S): SQLStatusBeforeInstall = 3
Property(S): SOURCEDIR = Z:\Tools\Setup\
Property(S): SourcedirProduct = {D6251ACA-3FD4-49D1-8FCF-182B980B19E3}
Property(S): HxDs_Tmp_3643236F_FC70_11D3_A536_0090278A1BB8 = C:\DOCUME~1\abahl\LOCALS~1\Temp\HxEA.tmp
Property(S): HxDs_Tmp_Hash_3643236F_FC70_11D3_A536_0090278A1BB8 = B40B0DC6C3C19C68E0101E0E2A647F0C3A18F6
Property(S): InstallNgenTicks = 1750000
Property(S): ProductToBeRegistered = 1
MSI (s) (38:20) [17:31:47:165]: Note: 1: 1708
MSI (s) (38:20) [17:31:47:165]: Product: Microsoft SQL Server 2008 Tools -- Installation failed.

You shouldn't be able to upgrade your report server. We don't support upgrade in the July CTP. Can you install a new instance?|||

No I am not trying to upgrade, but trying to install a clean install on windows 2003 box and I cannot.

Any thoughts, ideas.

Atul

|||What if you don't install the workstation tools? Just install the Report Server and see if you can configure it. Can you install the relational database by itself?|||

I am able to install the report server as well as the db from the looks of it.

But since management studio does not gets installed, I cannot verify or do anything with the DB.

I need to evaluate reporting services so it is very crucial to get this up and running.

Atul

|||You don't need Management Studio to use Reporting Services. But if you really need it on this machine, I would recommend you post the question over in the Katmai setup forum.

Cannot install Workstation components, fails on report server upgrade

I have hard time installing July CTP as it is failing on workstation component and fails on report server upgrade.

Any ideas for ther resolution.

Property(S): AdministratorsGroup = BUILTIN\Administrators
Property(S): PerformanceMontiorUsersGroup = BUILTIN\Performance Monitor Users
Property(S): PerformanceLogUsersGroup = BUILTIN\Performance Log Users
Property(S): UsersGroup = BUILTIN\Users
Property(S): SCMNetworkServiceAccount = NT AUTHORITY\NetworkService
Property(S): SCMLocalServiceAccount = NT AUTHORITY\LocalService
Property(S): IISCHECKED = 1
Property(S): SqlIISInstalled = 1
Property(S): SqlASPNETInstalled = 1
Property(S): SqlCOMPlusInstalled = 1
Property(S): RSPREREQUISITECHECKED = 1
Property(S): RSSqlPoolLimit = 100
Property(S): RSGUIDVALUE = {ec3b61d7-2813-485b-a55d-e0c931740946}
Property(S): RemoveFeatureList = Client_Components,Connectivity,SQL_Tools,SQL_WarehouseDevWorkbench,SDK,SQLXML,Tools_Legacy,TOOLS_BC_DEP,SQL_Documentation,SQL_Samples,SQL_BooksOnline,SQL_DatabaseSamples
Property(S): SqlOriginalMachineName = TAHITI
Property(S): Namechecksumcommon_32 = Developer Edition
Property(S): SqlSubDir = \MSSQL
Property(S): EditionTypechecksumcommon_32 = Developer Edition
Property(S): Namechecksumtools = Developer Edition
Property(S): EditionTypechecksumtools = Developer Edition
Property(S): ValidMOFInstanceName = 1
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer
Property(S): RSVirtualDirectoryManager = Reports
Property(S): SQLStatusBeforeInstall = 3
Property(S): SOURCEDIR = Z:\Tools\Setup\
Property(S): SourcedirProduct = {D6251ACA-3FD4-49D1-8FCF-182B980B19E3}
Property(S): HxDs_Tmp_3643236F_FC70_11D3_A536_0090278A1BB8 = C:\DOCUME~1\abahl\LOCALS~1\Temp\HxEA.tmp
Property(S): HxDs_Tmp_Hash_3643236F_FC70_11D3_A536_0090278A1BB8 = B40B0DC6C3C19C68E0101E0E2A647F0C3A18F6
Property(S): InstallNgenTicks = 1750000
Property(S): ProductToBeRegistered = 1
MSI (s) (38:20) [17:31:47:165]: Note: 1: 1708
MSI (s) (38:20) [17:31:47:165]: Product: Microsoft SQL Server 2008 Tools -- Installation failed.

You shouldn't be able to upgrade your report server. We don't support upgrade in the July CTP. Can you install a new instance?|||

No I am not trying to upgrade, but trying to install a clean install on windows 2003 box and I cannot.

Any thoughts, ideas.

Atul

|||

What if you don't install the workstation tools? Just install the Report Server and see if you can configure it. Can you install the relational database by itself?|||

I am able to install the report server as well as the db from the looks of it.

But since management studio does not gets installed, I cannot verify or do anything with the DB.

I need to evaluate reporting services so it is very crucial to get this up and running.

Atul

|||

You don't need Management Studio to use Reporting Services. But if you really need it on this machine, I would recommend you post the question over in the Katmai setup forum.

Cannot Install SQLServer 2005 Express

When I try to run the install it detects some previous versions components. The remove all previous beta components fails and I have removed everything from the Add/Remove Programs.
Any advice would be helpful
Irina

Hi Irina,

Take a look at your setup logs to find out exactly what pre-release component is being detected. Once you know which component it is, it should be easier to remove.

Regards,

Mike Wachal
SQL Express team

-
Please mark your thread as Answered when you get your solution.

cannot install SQL Server Express, keep getting errors

I am trying to install SQL Server 2005 Express, but it fails.
SQL Server Setup has detected incompatible components from Beta version of Visual Studio, .NETFramework or SQL Server 2005. Use Add or Remove to

I had earlier installed Beta 2 Version of Dev Studio 2005 and SQL Server 2005 Beta 2. I also had DevStudio 2003 and SQL Server installed. I have gone through and un-installed everything, but I keep getting this error.

I have also tried
msiexec /x {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
msiexec /x {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Both of these un-install start, but fail with error messages.

Would appreciate if anyone can help.

Saleem Yusuf
Saleem_Yusuf@.hotmail.com

Try the following.
1. Uninstall all visible Beta components in Add/Remove Programes.

2. Detect the Beta components infromation in the the log file located in %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup_%machinename%_Core(Local).log.

3. Search the whole registry keys, remove those registy keys related to those Beta components. This is time-consuming.

4. Kill all Beta SQL Services (including SQL, OLAP, RS, SQLBROWSER, SQLAGENT, etc.) if they are existing with command sc.

5. Reboot the machine.

6. Start Setup again.

|||I looked at the log and tried to uninstall old version, but it does not exists.
However, in the logs, I saw a version number and seach registry. They are many entries of SQL Server Express. I deleted some of them, but no luck yet. I am quite sure if I get rid of all the old registry setting, it should fix the problem.
Thanks for your help,

Saleem|||Problem fixed. I can now install SQL Server Express. Thanks for you help.
This is what I did.
Looked in file \Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG.
It had referecne to other log files. I opened one of the files, HostName_core.log
(notepad C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_<My_HostName>_Core.log)

This file had multiple reference to older versions of SQL Server Express. Example
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.06
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP"

First I tried to uninstall, (MsiExec.exe /x {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}). Un-install failed.

Then I searched for 9.00.1399.06. I found multiple entried. I deleted them all.
After that I was able install SQL Server Express.|||

I tried 3 other fixes on other forums (asp.net,etc.) and this is the only one that worked.

My log file had a similar message. However, I deleted the entries related to the older version (in the case above, that would be 9.00.1116); not the later or "expected at least" version (9.00.1399.06).

With this fix, I did not have to remove .net 1.0 beta or .net 1.1

|||Thanks for posting - that worked for me too - I had just spent my own money buying VS2005 Pro and couldn't install SQL Express because previously installed beta stuff was fouling up the install.

Perhaps the SQL guys at MS could revise the install script in future releases to 'clean up' before installing... Just a suggestion.

Anyway, just re-installed trhe whole .Net DVD and it's running now, so thanks!

Mark

cannot install SQL Server Express, keep getting errors

I am trying to install SQL Server 2005 Express, but it fails.
SQL Server Setup has detected incompatible components from Beta version of Visual Studio, .NETFramework or SQL Server 2005. Use Add or Remove to

I had earlier installed Beta 2 Version of Dev Studio 2005 and SQL Server 2005 Beta 2. I also had DevStudio 2003 and SQL Server installed. I have gone through and un-installed everything, but I keep getting this error.

I have also tried
msiexec /x {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
msiexec /x {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Both of these un-install start, but fail with error messages.

Would appreciate if anyone can help.

Saleem Yusuf
Saleem_Yusuf@.hotmail.com

Try the following.
1. Uninstall all visible Beta components in Add/Remove Programes.

2. Detect the Beta components infromation in the the log file located in %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup_%machinename%_Core(Local).log.

3. Search the whole registry keys, remove those registy keys related to those Beta components. This is time-consuming.

4. Kill all Beta SQL Services (including SQL, OLAP, RS, SQLBROWSER, SQLAGENT, etc.) if they are existing with command sc.

5. Reboot the machine.

6. Start Setup again.

|||I looked at the log and tried to uninstall old version, but it does not exists.
However, in the logs, I saw a version number and seach registry. They are many entries of SQL Server Express. I deleted some of them, but no luck yet. I am quite sure if I get rid of all the old registry setting, it should fix the problem.
Thanks for your help,

Saleem|||Problem fixed. I can now install SQL Server Express. Thanks for you help.
This is what I did.
Looked in file \Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG.
It had referecne to other log files. I opened one of the files, HostName_core.log
(notepad C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_<My_HostName>_Core.log)

This file had multiple reference to older versions of SQL Server Express. Example
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.06
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP"

First I tried to uninstall, (MsiExec.exe /x {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}). Un-install failed.

Then I searched for 9.00.1399.06. I found multiple entried. I deleted them all.
After that I was able install SQL Server Express.|||

I tried 3 other fixes on other forums (asp.net,etc.) and this is the only one that worked.

My log file had a similar message. However, I deleted the entries related to the older version (in the case above, that would be 9.00.1116); not the later or "expected at least" version (9.00.1399.06).

With this fix, I did not have to remove .net 1.0 beta or .net 1.1

|||Thanks for posting - that worked for me too - I had just spent my own money buying VS2005 Pro and couldn't install SQL Express because previously installed beta stuff was fouling up the install.

Perhaps the SQL guys at MS could revise the install script in future releases to 'clean up' before installing... Just a suggestion.

Anyway, just re-installed trhe whole .Net DVD and it's running now, so thanks!

Mark

cannot install SQL Server Express, keep getting errors

I am trying to install SQL Server 2005 Express, but it fails.
SQL Server Setup has detected incompatible components from Beta version of Visual Studio, .NETFramework or SQL Server 2005. Use Add or Remove to

I had earlier installed Beta 2 Version of Dev Studio 2005 and SQL Server 2005 Beta 2. I also had DevStudio 2003 and SQL Server installed. I have gone through and un-installed everything, but I keep getting this error.

I have also tried
msiexec /x {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
msiexec /x {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Both of these un-install start, but fail with error messages.

Would appreciate if anyone can help.

Saleem Yusuf
Saleem_Yusuf@.hotmail.com

Try the following.
1. Uninstall all visible Beta components in Add/Remove Programes.

2. Detect the Beta components infromation in the the log file located in %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup_%machinename%_Core(Local).log.

3. Search the whole registry keys, remove those registy keys related to those Beta components. This is time-consuming.

4. Kill all Beta SQL Services (including SQL, OLAP, RS, SQLBROWSER, SQLAGENT, etc.) if they are existing with command sc.

5. Reboot the machine.

6. Start Setup again.|||I looked at the log and tried to uninstall old version, but it does not exists.
However, in the logs, I saw a version number and seach registry. They are many entries of SQL Server Express. I deleted some of them, but no luck yet. I am quite sure if I get rid of all the old registry setting, it should fix the problem.
Thanks for your help,

Saleem|||Problem fixed. I can now install SQL Server Express. Thanks for you help.
This is what I did.
Looked in file \Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG.
It had referecne to other log files. I opened one of the files, HostName_core.log
(notepad C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_<My_HostName>_Core.log)

This file had multiple reference to older versions of SQL Server Express. Example
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.06
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP"

First I tried to uninstall, (MsiExec.exe /x {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}). Un-install failed.

Then I searched for 9.00.1399.06. I found multiple entried. I deleted them all.
After that I was able install SQL Server Express.
|||

I tried 3 other fixes on other forums (asp.net,etc.) and this is the only one that worked.

My log file had a similar message. However, I deleted the entries related to the older version (in the case above, that would be 9.00.1116); not the later or "expected at least" version (9.00.1399.06).

With this fix, I did not have to remove .net 1.0 beta or .net 1.1

|||Thanks for posting - that worked for me too - I had just spent my own money buying VS2005 Pro and couldn't install SQL Express because previously installed beta stuff was fouling up the install.

Perhaps the SQL guys at MS could revise the install script in future releases to 'clean up' before installing... Just a suggestion.

Anyway, just re-installed trhe whole .Net DVD and it's running now, so thanks!

Mark

Cannot install MSDE 2000 on XP SP2

I have attempted to install MSDE 2000 (Italian localized version) on
XP SP2 but the install fails with the message (translated from
Italian): "Impossible to configure the server. For further information
examine the log etc., etc."
Norton Av: disenabled. Not connected to network.
My install parameters were:
setup SAPWD="password" SECURITYMODE=SQL /L*v "C:\Temp\MSDELog.log"
I searched the log for "return value 3" (valore restituito 3, in
Italian), and have captured the 20 lines before the failure:
MSI (s) (EC:D0) [18:27:47:141]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI21.tmp, Entrypoint: InstallSQLAgentSecurity
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is C:\DOCUME~1\Mike\IMPOST~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Mike\IMPOST~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity succeeded
MSI (s) (EC:38) [18:27:47:261]: Executing op:
ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
MSI (s) (EC:38) [18:27:47:261]: Executing op:
CustomActionSchedule(Action=SkuIt.2D02443E_7002_4C 0B_ABC9_EAB2C064397B,ActionType=1025,Source=Binary Data,Target=SkuIt,)
MSI (s) (EC:D8) [18:27:47:261]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI22.tmp, Entrypoint: SkuIt
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is C:\DOCUME~1\Mike\IMPOST~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Mike\IMPOST~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action SkuIt
MSI (s) (EC:38) [18:27:47:361]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (EC:38) [18:27:47:361]: Executing op:
CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (EC:C0) [18:27:47:361]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI23.tmp, Entrypoint: ConfigServer
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is C:\DOCUME~1\Mike\IMPOST~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Mike\IMPOST~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action ConfigServer
Executing "C:\Programmi\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
-V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "Latin1_General_CI_AS""
MSI (c) (BC:B8) [18:29:54:003]: Font created. Charset: Req=0, Ret=0,
Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Impossibile configurare il server. Per ulteriori informazioni,
esaminare il log degli errori del server e il log degli errori del
programma di installazione.
MSI (s) (EC!C4) [18:29:59:491]: Prodotto: Microsoft SQL Server Desktop
Engine -- Impossibile configurare il server. Per ulteriori
informazioni, esaminare il log degli errori del server e il log degli
errori del programma di installazione.
Fine operazione 18.29.59: InstallFinalize. Valore restituito 3.
Can anyone help me?
Mike Watson
hi Mike,
Mike Watson wrote:
> I have attempted to install MSDE 2000 (Italian localized version) on
> XP SP2 but the install fails with the message (translated from
> Italian): "Impossible to configure the server. For further information
> examine the log etc., etc."
please have a look at
http://support.microsoft.com/default...99&Product=sql
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message news:<3b5fcgF6gi5u6U1@.individual.net>...
> hi Mike,
> Mike Watson wrote:
> please have a look at
> http://support.microsoft.com/default...99&Product=sql
Ciao Andrea,
I checked out the the indicated paper. I have no previous installs.
Nonetheless, I physically removed the leftover install folders. I then
added an INSTANCENAME="..." to my ini file and repeated the
installation.
Exactly the same result. Can you give me further help?
Mike Watson
|||Ciao Mike,
Mike Watson wrote:
> I checked out the the indicated paper. I have no previous installs.
> Nonetheless, I physically removed the leftover install folders. I then
> added an INSTANCENAME="..." to my ini file and repeated the
> installation.
> Exactly the same result. Can you give me further help?
>
I actually installed MSDE on WinXP pro sp2 2 days ago on a virtual machine
just to test the very same result reported by another user but I was not
able to repro..
all Microsoft hints related to that kind of problem are indicated to be
solved by that Knowledge Base article... but I learned that sometime MSDE
fails to install on WinXP sp2 due to problems with the MDAC 2.8 WinXP sp2
stack, and currently there's no workaround for that.. but again, I was
(fortunately :D) not able to repro this kind of problems
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply