SQL Server 2005 SP 2 December CTP Authentication Fails
Jan 3, 2007
Hi,
if I try to install SP 2 using SQL Server authentification (sa) it fails. The following lines appear in the file "Hotfix.log":
01/03/2007 14:08:23.859 Authenticating user using SAPWD
01/03/2007 14:08:23.875 Validating database connections using Windows Authentication
01/03/2007 14:08:24.171 Pre-script database connection failed - continuing to wait for SQL service to become responsive to connection requests
... repeated 60 times ...
01/03/2007 14:13:33.625 The following exception occurred: SQL Server reagiert nicht vor der Skriptausführung Date: 01/03/2007 14:13:33.609 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllinstance.cpp Line: 1411
Why does it try to use Windows Authentification although I have told it to use SQL Server Authentification (Windows Authentification has been disabled in this Database Instance)?
I have a developer who built an application using the SSE 2005 December CTP and I would like to bring the db's into the official SSE 2005 released version. I have attempted the following:
1. Create the db's in the released version, detach and re-attach the CTP db's. I got an error telling me they were incompatible.
2. Installed CTP version on one server, backed up the db's and then attempted to restore the db's on another server running the official released version of SSE 2005. Got an error attempting that too.
3. Installed the Management Studio for SS 2005 Developer edition thinking that I could connect to the two seperate instances of each server and like I could in EM 2000 run the transfer wizard to move the db's and data from one server to the next. Problem with this is that I can't get an object browser connection established. I have TCP/IP all config'd correctly, too.
Any other ideas where I can go with this at this time?
I am using SQLXML 3 on a Windows 2003 server Running IIS 6.0. I used SQLXML configure IIS Support to create a virtual directry on this server to connect to MS SQL Server 2000 instance running on another windows 2003 server.
Configurations for the virtual directory are
1. Used Windows integrated authentication.
2. Created template for executing the stored procedure.
When i try to access the DB Server through a browser i am prompted to provide for Windows authentication. Even if i provide the domain user that has administrtive rights on both the server i am getting a response.
If from MMC i change the properties of the virtual directry to enable anonymous acess using the cridentials that i mentioned earlier, everything is working fine. I have been searching the net for 2 days and tried everything that i could find but still i keep getting the same error.
I folks.I Have installed sql server 2005 express and choosed windowsauthentication on instalation, but i make a mistake and now i needmixed authentication, how can i modify this whithout uninstall andinstall again the application?thanks for the help.
The setup athenticates the Database Services and the Reporting Services. Database Services login is successful, but the setup raises an error on the authentication of the reporting Services.
Hi there,I have installed MS SQL Server 2005 on my machine with windows authentication. But now I want to switch the authentication mode to SQL Authentication. I am unable to switch, I can’t find the proper way to do so here in 2005.Could any one help me in doing this?Thank you,-Ahsan
One of my users gets the following error when he tries to connect to my SQL Server 2000 database using windows authentication via Query Analyzer:
[Micorsoft][ODBC SQL Server Driver][SQL Server] Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Me and the server are located in Colorado and are on the NADomain. User is in London on the EURDomain. The EURDomain has a one way trust to the NADomain to use NADomain resources. I have granted access to the database to the user via Enterpise Manager as EURDomainuserid. All the literature I've read says this should be sufficient to connect but isn't. User can connect with SQL Server authentication. Users on the NADomain in Toronto can connect just fine with Windows Authentication. EURDomain user can access other file server resources in the same building as the SQL Server in Colorado.
SQL Server version is:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86) Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
EURDomain Client ODBC version is 2000.85.1022.00 and MDAC is 2.8.
<html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="/ReportServer/logon.aspx?ReturnUrl=%2freportserver%2fReportExecution2005.asmx">here</a>.</h2> </body></html>
We have been using Sql Server 2005 Compact Edition 3.1 RDA synchronization method successfully on Sql Server 2000 database. Recently we moved the database to Sql Server 2005, sync doesn't work anymore, it just hangs on one table. On further investigation, we found out that it's the index on that table that causes this. We removed the index, it works fine. We are wondering the root cause, removing the index is not a solution for us. Any thoughts?. Thanks.
When trying to connect to a SQL Server 2005 Analysis Services instance through the Excel 2007 Add-In, the ability to choose a user name/password combination rather than Windows Authentication seems to be disabled. Is there a way to do this? Thank you!
not sure if this is the right place to raise this question. If not please move this message.
I configured a Sql-Server 2005 installation -that is running on my computer for test purposes- with "Windows Authentication". I had to change my Windows password recently and it seems as if SQL-Server does not accept my account anymore. The event viewer told me that service startups failed because user or password are unkown.
Does anybody know how I may get access again? The problem seems to be that I cannot change back to my old password -unless I change it six or more times...
I am trying to upgrade SQL Server Express 2005 Report Server to SQL 2005 Standard and it fails with the following error:
SQL Server Setup did not have the administrator permissions required to copy a file: C:Program FilesMicrosoft SQL ServerMSSQL.8Reporting ServicesReportServer ssrvpolicy.config. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
After I click OK on the message, this whole path where the upgrade is bieng installed dissapears C:Program FilesMicrosoft SQL ServerMSSQL.8Reporting Services. The error is a bit missleading because the file that it is trying to copy rssrvpolicy.config does appear in that upgrade folder so I am not sure why it would try to copy a file that has already been copied.
I was able to upgrade the Database Engine instance fine but can't upgrade Reporting Services due to that error. I have verified that the account that ran the setup had the administrator permissions. Your prompt reply to my question would be greatly appreciatted.
HI, My computer keeps trying to download SQL Server 2005 Express Edition SP2 and fails with the error code 0x2B22. It is a new computer running with Windows XP Pro.
I have spent hours searching the forums and the internet, but I can't find anything to help, or I don't understand the solutions or whether they relate to my computer. I don't know how to find out why the update is failing either.
I am trying to upgrade SQL Server 2005 Express to SQL Server 2005 Enterprise Edition. (As a Preparation to install SQLServer2005 Service Pack 2 (CTP))
I tried to upgrade a particular Instance (OFFICESERVERS, which was based on SQL Server 2005 Express ).
During the upgrade I get a message saying that ...
.....Your upgrade is blocked because of edition upgrade rules.....
All other components I selected for Installation are propertly installed (Analysis, Reporting)
The setup log contains the following detail information:
---- Context ----------------------------------------------- Setting status of unmanaged components and removing unmanaged resources
Error Code: 29543 MSI (s) (DC!C8) [13:57:26:265]: Product: Microsoft SQL Server 2005 -- Error 29543. Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online. Edition check: Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Error 29543. Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online. Edition check: Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online. <Func Name='SetCAContext'> <EndFunc Name='SetCAContext' Return='T' GetLastError='0'> Doing Action: ValidateUpgrade PerfTime Start: ValidateUpgrade : Fri Dec 29 13:57:26 2006 <Func Name='ValidateUpgrade'> <Func Name='updateFeatureSellection'> Error Code: 0x80077367 (29543) Windows Error Text: Source File Name: sqlcaupgradeproduct.cpp Compiler Timestamp: Mon Sep 19 01:07:45 2005 Function Name: sqls::UpgradeProduct::CanUpgrade Source Line Number: 142
The result is the same, i.e.... Your upgrade is blocked because of edition upgrade rules...
Does anybody know about this problem? Some more information about the system: W2K3 R2 Enterprise Edition WSS3.0 MOSS2007 previously installed SQL Server 2005 Express Edition (Version 9.00.2047.00)
I used JTDS to connect to SQL Server 2005 SP1(with Windows Authentication) from a Tomcat DataSource, using your usefull ntlmauth.dll, so I can use Users from Active Directory. All is ok until I must call a Stored procedure that excecute queries from a linked server table. I have the following exception message "Login failed for user 'NT AUTHORITYANONYMOUS LOGON'"
I make a lot of test, I make a Java main program invoking the sotred procedure that excecute queries on linked server using JTDS and then using Microsoft SQL Server 2005 JDBC Driver 1.2(April 2007)sqljdbc.jar and Ihave the same problem, but if we use the bridge JDBC-ODBC all works OK.
We are using VB.NET 2005 (Winform) and the backend SQL Server Express 2005. We would like to connect the Express (.mdf) database from Remote Machine. What type of connection string we have to use?
We tried the following ConnectionString but we got the error: Provider=SQLNCLI.1;Server=.SQLEXPRESS;AttachDbFileName=S:MLJData.mdf;Database=MLJData;Trusted_Connection=Yes;
Also suggest what are all the prerequisites to run sql server express 2005 database in client machine.
We did installed the following tools in client machine:
Hi all, I've read up on the fact that if you use SQL server 2005 instead of SQL express you need to change the connection string in web.config. Is there anyway to make this default connection type, or do I have to do it for every website I create. i.e. is there a global file that this connection can be entered into. Then whenever I start a new website I don't have to put the string in. Just me being lazy really. But it's nice to know if it's possible.
I have installed SQL Server 2005 onto a server and then on my client machine I have installed SQL Server 2005 and the Server Management Studio.
When installing it on the server I chose all the defaults so have not setup an sql username or password to connect as I thought I could use Windows.
I go to the Server Management and registered servers, create a new one and enter the ip address of the server and choose Windows Authentication. The following error keeps appearing though and I am not sure what settings/where to check:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (.Net SqlClient Data Provider)
I have checked and think port 1443 is open on the server, tcpip is enabled but when I choose Windows authentication I cannot enter a username or password as it is greyed out. It has completed the username but no password and these are not the correct ones to connect to the server - I wish to wish the same one I use for RDC.
Or should I try SQL Authentication and if so how would I set this up? Cannot see on the server in SQL Configuration where I could set this?
Hope someone who knows a lot more than me on this can help!
Thanks for your time - this has been driving me mad for days now and everything I print off the internet is not help so any feed back or more useful links to loo up would be great.
After the installer has asked for authentication mode and has started verifying the authentication it simply hangs. I've let it sit there for an hour before taking the installer forcibly down but nothing seems to be happening except for two osql.exe processes showing up in the task manager.
I've tried both windows authentication and SQL server authentication but the outcome is always the same. At the same time I'm, however, able to login to the database engine and all services with management studio using both authentication modes.
The last few lines in HotFix.log are as follows:
05/09/2006 09:49:09.999 Authenticating user using Windows Authentication 05/09/2006 09:49:10.015 SQL Service MSSQLServer was previously running, ready for authentication 05/09/2006 09:49:10.218 SQL Agent Service SQLSERVERAGENT was previously running 05/09/2006 09:49:12.093 User authentication was successful
This would indicate that there's nothing wrong with the authentication but with whatever is supposed to take place after that.
There are quite a few lines in the log similar to the one below:
05/09/2006 09:47:08.438 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.2MSSQLBinnSQLServr.exe
Redist9_Hotfix_KB913090.log seems to be the only individual log file that ends with line saying "Hotfix package launched" whereas all other logs have several lines of checks being completed successfully.
Any ideas what might be causing the installer to hang and how to fix it?
I have just created some SSIS package. Some package has connection to remote SQL Server 2005 by SQL server authentication mode (not windows).
In the connection property I have setted "save my password", but I have found that after a while the connection is missed and I have to make the Logon. this happen always to random.
Do you know how to keep the connection persistent?
I would like to ONLY allow using SQL Server authentication and restrict Windows Authentication. At the moment, i set the security to "SQL server and windows authentication". Now, even though i set the password for "sa", i can ignore the SQL Server authentication and just use Windows authentication to manipulate database objects???
can anybody give some suggestions to restrict windows authentication and allow sql server authentication?.
Microsoft recommends using Windows authentication instead of SQL Server authentication in SQL Server 2005 for improved security. What are the Microsoft best practices for implementing this? Will be helpful if someone also provides some links that talks about this....
I have a Windows Server 2003 Enterprise Edition SP1 with a couple of SQL Server 2000 instances on it and two SQL Server 2005 instances on it.
I tried to install SQL Server 2005 SP1, but kept getting failures. I saw that SP2 fixed some of the issues with installation issues that SP1 had. So, I tried to install it. Some of the smaller components install successfully (VSS Writer, Backward Compatibility, SQLXML4, MSXML 6.0 Parser, Native Client, Support Files), but all of the base services fail to install (Database services, Reporting Services failed for two different instances).
I've downloaded the SP2 from the Microsoft site local to that server and install from there. I don't have space problems on the drives in question.
In the summary log that's located at C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfix, I see:
Error Number : 29513 Error Description : MSP Error: 29513 SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:Program FilesMicrosoft SQL Server90Sharedsqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
I've searched through many links, one suggested that the WMI could be potentially corrupt. So, I also downloaded with WMIDiag utility and ran it. So, I have a log from that as well. It did have 8 errors in it. But, the information in the report hasn't really helped me determine how to fix those errors.
While I was looking around, I found another log file located at C:WINNTsystem32wbemLogs called the mofcomp.log. As my error looks like a compile error issue, I looked in that log file and found the following at the times when the install was failing:
(Thu Feb 22 16:29:49 2007.1910312) : Parsing MOF file: C:Program FilesMicrosoft SQL Server90Sharedsqlmgmprovider.mof (Thu Feb 22 16:29:49 2007.1910625) : Finished compiling file:C:Program FilesMicrosoft SQL Server90Sharedsqlmgmprovider.mof (Thu Feb 22 16:34:25 2007.2186343) : Parsing MOF file: C:Program FilesMicrosoft SQL Server90Sharedsqlmgmproviderxpsp2up.mof (Thu Feb 22 16:34:25 2007.2186343) : (1): error SYNTAX 0X8004401e: This is not a valid MOF file
This makes me wonder if there is an invalid MOF file as part of SP2?
Also, when I go into Microsoft SQL Server Management Studio, I can no longer look at any of my maintenance plans. All of them throw an error which says:
Error loading 'Daily Backup' : Unable to cast COM object of type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass' to interface type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSApplication90'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{7591CC39-276A-4973-97C7-4EFEA5A5788F}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE))..
I have been trying to install Visual Web Developer 2005 Express Edition and SQL Server 2005. The Web Developer installs ok but the SQL Server installation fails. I can't figure out why. I have (I think...) uninstalled my previous beta intallations. The must be something else that prevents the installation. Can anyone point me to some FAQ or something that can give me some ideas on how to handle the installation./anders
Hi, Trying to install SQL Server 2005 SP1 on a windows 2003 box and it fails for database services and reporting services patch. It installs successfully other components of the patch.
Following errors are logged in the event log.
1) Product: Microsoft SQL Server 2005 - Update 'Service Pack 1 for SQL Server Database Services 2005 ENU (KB913090)' could not be installed. Error code 1603. Additional information is available in the log file C:WINNTHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.log 2) Product: Microsoft SQL Server 2005 -- Error 29506. SQL Server Setup failed to modify security permissions on file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData for user birendraa. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.
3) Product: Microsoft SQL Server 2005 Reporting Services -- Error 29561. SQL Server Setup failed to retrieve the SSL Certificate Name.
4) Product: Microsoft SQL Server 2005 Reporting Services - Update 'Service Pack 1 for SQL Server Reporting Services 2005 ENU (KB913090)' could not be installed. Error code 1603. Additional information is available in the log file C:WINNTHotfixRS9LogsRS9_Hotfix_KB913090_sqlrun_rs.msp.log.
The account running SQL server setup has admin privileges on that box.
I am trying to install Sql Server 2005 SP2 (KB921896) on a Windows Server 2003 box that has all the other patches installed. However, the service pack fails on Databse Services and Analysis Serrvices. The Summary.txt file is listed below. I have already done some research and tried putting the NT Authority/SYSTEM in the local Administrators group but I still get the same error. Can anyone help? Thanks Time: 06/21/2007 15:30:09.610 KB Number: KB921896 Machine: PDSQL OS Version: Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790) Package Language: 1033 (ENU) Package Platform: x86 Package SP Level: 2 Package Version: 3042 Command-line parameters specified: Cluster Installation: No
********************************************************************************** Prerequisites Check & Status SQLSupport: Passed
********************************************************************************** Products Detected Language Level Patch Level Platform Edition Setup Support Files ENU 9.2.3042 x86 Database Services (MSSQLSERVER) ENU SP1 2005.090.2047.00 x86 STANDARD Analysis Services (MSSQLSERVER) ENU SP1 2005.090.2047.00 x86 STANDARD Reporting Services (MSSQLSERVER) ENU SP2 9.00.3054.00 x86 STANDARD Notification Services ENU SP2 9.00.3054.00 x86 STANDARD Integration Services ENU SP2 9.00.3054.00 x86 STANDARD SQL Server Native Client ENU 9.00.3042.00 x86 Client Components ENU SP2 9.2.3054 x86 STANDARD MSXML 6.0 Parser ENU 6.10.1129.0 x86 SQLXML4 ENU 9.00.3042.00 x86 Backward Compatibility ENU 8.05.2004 x86 Microsoft SQL Server VSS Writer ENU 9.00.3042.00 x86
********************************************************************************** Products Disqualified & Reason Product Reason Reporting Services (MSSQLSERVER) The product instance MSSQLSERVER been patched with more recent updates. Notification Services The product instance NS been patched with more recent updates. Integration Services The product instance Integration Services been patched with more recent updates. Client Components The product instance SQL Tools been patched with more recent updates.
********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID msftesql Database Services Service NT AUTHORITYSYSTEM 3464 SQLBrowser Database Services Service NT AUTHORITYSYSTEM 5276
********************************************************************************** Product Installation Status Product : Setup Support Files Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Database Services (MSSQLSERVER) Product Version (Previous): 2047 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 29512 Error Description : MSP Error: 29512 SQL Server Setup was unable add user NT AUTHORITYSYSTEM to local group PERSONNELALSQLServer2005SQLAgentUser$PDSQL$MSSQLSERVER. ---------------------------------------------------------------------------------- Product : Analysis Services (MSSQLSERVER) Product Version (Previous): 2047 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixOLAP9_Hotfix_KB921896_sqlrun_as.msp.log Error Number : 29512 Error Description : MSP Error: 29512 SQL Server Setup was unable add user NT AUTHORITYSYSTEM to local group PERSONNELALSQLServer2005MSOLAPUser$PDSQL$MSSQLSERVER. ---------------------------------------------------------------------------------- Product : Reporting Services (MSSQLSERVER) Product Version (Previous): 3054 Product Version (Final) : Status : NA Log File : Error Description : The product instance MSSQLSERVER been patched with more recent updates. ---------------------------------------------------------------------------------- Product : Notification Services Product Version (Previous): 3054 Product Version (Final) : Status : NA Log File : Error Description : The product instance NS been patched with more recent updates. ---------------------------------------------------------------------------------- Product : Integration Services Product Version (Previous): 3054 Product Version (Final) : Status : NA Log File : Error Description : The product instance Integration Services been patched with more recent updates. ---------------------------------------------------------------------------------- Product : SQL Server Native Client Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Client Components Product Version (Previous): 3054 Product Version (Final) : Status : NA Log File : Error Description : The product instance SQL Tools been patched with more recent updates. ---------------------------------------------------------------------------------- Product : MSXML 6.0 Parser Product Version (Previous): 1129 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : SQLXML4 Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Backward Compatibility Product Version (Previous): 2004 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Microsoft SQL Server VSS Writer Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ----------------------------------------------------------------------------------
********************************************************************************** Summary One or more products failed to install, see above for details Exit Code Returned: 29512
