We are trying to install SQL Server on a cluster that has 4 nodes, 3 of them running SQL2k. We're getting an error in the setup after it is done with Framework:
Failed to find property "ComputerList" {"SqlComputers", "", ""} in cache
... Source File Name: datastoremachineconfigscopeproperties.cpp
Compiler Timestamp: Wed Aug 24 13:40:04 2005
Function Name: SqlInstallConfigScope.InstanceName
....-
Error: Could not find an install of type 3 for instance SQL ##
We think it's due to a directory and item in the registry for a server instance we used to run on this server, but no longer due as it was uninstalled and the server moved to this cluster. The directory doesn't show in other nodes in the cluster, but does in the cluster it was moved from. We continue to find that 2nd instance refuses to failover to this server also. We have determined that it€™s only the SQL server which is having issues as we were able to move the disks over. When we start the SQL service it pops back to 2nd instances home server.
We are planning to upgrade the SQL Server in our production environment from SQL Server 2000 to SQL Server 2005. This is a 4 Node cluster environment with 3 Databases on 3 Virtual instances. The main requirement is to achieve this with no/minimal downtime.
Could you please suggest or direct me to any documentation for the best practices used to upgrade such an environment?
We're upgrading a SQL Server 2000 cluster (Active/Passive) running on Windows 2000 Server to a SQL Server 2005 Cluster running on Windows Server 2003. We can't purchase new hardware and we have no spare hardware. We also need to move from Windows 2000 Server to Windows 2003 Server at the same time. We want to keep downtime to a bare minimum.
What we were thinking was the following steps... Anyone try this?
1. Break the link between the servers.
2. Install a fresh copy of windows 2003 server on one side along with SQL Server 2005. While this step is running, the active node would still be live on Windows 2000 Server and SQL Server 2000 serving our customers.
3. Restore a copy of a backup from the active production side to the node we're upgrading and at that point we would bring the active node down, switching the active node to be the newly upgraded server.
4. As a final step, the old active node would now have the link to it broken, we would install a fresh copy of windows 2003 server on it and sql server 2005. At this point we would bring it back into the cluster and the cluster would be complete again.
Need your help and guidence for doing upgrading SQL Server 2000 Cluster to SQL Server 2005 Cluster.
Let me explain my current environment.
1. Currently SQL Server 2000 Cluster environment is running on Windows 2000 Server we need to upgrade this to SQL Server 2005 on Windows 2003 Server. >>> Production environment.
My Plans:
1. On Testing Environment Install SQL Server 2000 cluster on Windows 2003 Server and do a restore of databases from the produciton environment.
2. Upgrade In-Place from SQL Server 2000 Cluster to SQL Server 2005 Cluster.
My doubts
1. Can i install SQL Server 2000 Cluster on Windows 2003 Server. Is it possible or not.
I am trying to install SQL 2005 in a 2-node virtual Windows 2003 cluster. I set the cluster up through Virtual Server 2005 with 2 virtual nodes and one virtual domain. The nodes can connect to each other as well as the physical machine. When I try to install a fresh copy of SQL 2005 on my cluster, I get an error every time. The error stops the installation while checking system configuration after installing prerequisites. The log file entry is as follows:
******************************************* Setup Consistency Check Report for Machine: --SERVERNAME-- ******************************************* Article: WMI Service Requirement, Result: CheckPassed Article: MSXML Requirement, Result: CheckPassed Article: Operating System Minimum Level Requirement, Result: CheckPassed Article: Operating System Service Pack Level Requirement, Result: CheckPassed Article: SQL Compatibility With Operating System, Result: CheckPassed Article: Minimum Hardware Requirement, Result: CheckPassed Article: IIS Feature Requirement, Result: Warning Description: IIS is not installed, therefore Report Server feature will be disabled Action: Install IIS in order for Report Server feature to be enabled Article: Pending Reboot Requirement, Result: CheckPassed Article: Performance Monitor Counter Requirement, Result: CheckPassed Article: Default Installation Path Permission Requirement, Result: CheckPassed Article: Internet Explorer Requirement, Result: CheckPassed Article: Check COM+ Catalogue, Result: CheckPassed Article: ASP.Net Registration Requirement, Result: CheckPassed Article: Minimum MDAC Version Requirement, Result: CheckPassed <Func Name='PerformDetections'> 1 Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.1399.0 Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. Error information reported during run: Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "ComputerList" {"SqlComputers", "", ""} in cache Source File Name: datastoreclusterinfocollector.cpp Compiler Timestamp: Fri Sep 16 13:20:12 2005 Function Name: ClusterInfoCollector::collectClusterVSInfo Source Line Number: 883 ---------------------------------------------------------- Failed to detect VS info due to datastore exception. Source File Name: datastoreclustergroupsproperties.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: ClusterGroupScope.SharedDisks Source Line Number: 56 ---------------------------------------------------------- Failed to find a cluster group that owned shared disk: J: WinException : 2 Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified. Source File Name: datastoreclustergroupsproperties.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: ClusterGroupScope.SharedDisks Source Line Number: 56
I am in the process of moving databases from a SQL 2005 Standard version to a 2-node 2014 cluster.All of my 2005 databases back up successfully.They all restore without issue except for one database that has a full text catalog. I get this message
Msg 7610, Level 16, State 1, Line 2 Access is denied to "fileStoragedataMSSQLSERVERFullTextCatalog", or the path is invalid. Msg 3156, Level 16, State 50, Line 2 File 'sysft_FTCatalog' cannot be restored to 'fileStoragedataMSSQLSERVERFullTextCatalog'. Use WITH MOVE to identify a valid location for the file. Msg 3119, Level 16, State 1, Line 2 Problems were identified while planning for the RESTORE statement. Previous messages provide details. Msg 3013, Level 16, State 1, Line 2 RESTORE DATABASE is terminating abnormally.
[code]....
I went as far as giving the folder full access to everyone temporarily and received the same error.
...so got the below information from the cluster log:
000009fc.00000d68::2007/02/13-12:36:53.210 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.226 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746; message = [Microsoft][SQL Native Client]TCP Provider: An existing connection was forcibly closed by the remote host.
000009fc.00000d68::2007/02/13-12:36:53.226 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] OnlineThread: QP is not online. 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 0000088c.00000af8::
Looked at the system log to see if there are any errors , but could not found any during that time....The last message in the system log was
Event Type: Warning Event Source: Print Event Category: None Event ID: 3 Date: 2/13/2007 Time: 5:03:04 PM User: NT AUTHORITYSYSTEM Computer: xxx Description: Printer ITGHP8N1 on rchprt01 (from R6911497-XP) in session 1 was deleted.
before that there were messages of creating and deleting the printer...and R6911497-XP is my laptop which was not really running during that time...
From some research came to know that this might be because of network issues, but let me know for what errors I need to look for network issues...does the above error in the system log suggests network errors...
I have a two node failover cluster with SQL 2005 installed. I am running Windows Server 2003 x64 Enterprise and SQL 2005 x64 Enterprise. When I try the SP2 upgrade, I basically get an error message saying no passive nodes were succesfully patched. I have tried installing from the active node and the virtual server, same results with both. I have also tried the LMHOSTS file addition that Microsoft recommends, but that didnt solve the problem either. We do have an MSDTC Resource set up, as I have read this may cause problems, but it still doesnt work.
I dont know what to do next, any ideas?
Time: 03/11/2008 09:40:26.456 KB Number: KB921896 Machine: CAROLINA OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 2 (Build 3790) Package Language: 1033 (ENU) Package Platform: x64 Package SP Level: 2 Package Version: 3042 Command-line parameters specified: Cluster Installation: Yes Log Location on Passive Nodes: (OAKLAND) C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfix (CAROLINA) C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfix ********************************************************************************** Prerequisites Check & Status SQLSupport: Passed ********************************************************************************** Products Detected Language Level Patch Level Platform Edition Setup Support Files ENU 9.2.3042 x64 Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x64 ENTERPRISE SQL Server Native Client ENU 9.00.3042.00 x64 Client Components ENU RTM 9.00.1399.06 x64 ENTERPRISE MSXML 6.0 Parser ENU 6.10.1200.0 x64 SQLXML4 ENU 9.00.1399.06 x64 Backward Compatibility ENU 8.05.2004 x64 Microsoft SQL Server VSS Writer ENU 9.00.3042.00 x64 ********************************************************************************** Products Disqualified & Reason Product Reason ********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID ********************************************************************************** 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): 1399 Product Version (Final) : Status : Failure Log File : Error Number : 11009 Error Description : No passive nodes were successfully patched ---------------------------------------------------------------------------------- ********************************************************************************** Summary No passive nodes were successfully patched Exit Code Returned: 11009 e : Error Description : ---------------------------------------------------------------------------------- ********************************************************************************** Summary No passive nodes were successfully patched Exit Code Returned: 11009
First I am fairly new to SQL Server 2005 Clustering so this is why I was to see if any of you might be able to help me.
Are current setup is as follows:
CRM1 SERVER 2K3 R2 xxx.xxx.xxx.74
CRM2 SERVER 2K3 R2 xxx.xxx.xxx.75
HP MSA1000 xxx.xxx.xxx.75
MSDTC IP xxx.xxx.xxx.77
SQL INSTANCE xxx.xxx.xxx.78
Now are CRM guys are trying to connect to xxx.xxx.xxx.78 for there SQL instance or RDP into this ip address and they can’t…Now the question is should they be able yto logon to the SQL Instance via RDP?
We have sql server 2005 installed locally on 2 servers and want to set up failover clustering. Do we need to uninstall what we have then install as failover cluster? Thanks.
I have windows server 2003 service pack 1 and sql server 2005 service pack 1 - 64 bit. Sometimes it happens in the middle of the night. Sometimes it's in the middle of the day and sometimes it's multiple times in the same day. Usually the server fails over.
Hi. I have installed an SQL 2005 Failover Cluster on a Two Node Active Passive Windows 2003 Cluster.If i am trying to failover from the Active node to the passive Node,The Sql Server,Sql Server Agent and SQL Analysis resources fail,However if i reset the passowrd in the services tab of the above three services on the pasive node,the resources come online. Below is the brief of my setup 1.I have two Active directory domain controllers running Windows 2003 R2 Standard edition with SP2. 2.i have installed a Windows 2003 Two Node Active Passive Cluster as NODE1 and NODE2. 3.The Domain account used to install WIndows 2003 A/P Cluster is Clusteradmin.This account is the member of Administartors on the Domain as well as the Local Admin on NODE1 and NODE2. 4.SQL 2005 with SP2 is installed on both the Nodes as SQL 2005 Failover Cluster.The account used to install SQL 2005 is sqadmin.This account is the member of Administartors on the domain and the member of Local Admins on NODE1 and NODE2. 5.SLQ 2005 has four domain groups for 4 SQL Services.The Services are SQL Server,SQL Server Agent,SLQ Anaylisis Server and Full text Search. 6.Each of these servcie has a seperate service account created for them.All these service accounts areb the members of domain admin and the member of Local Admin on NODE1 and NODE2. 7.Each of these servcies is running under these servcie accounts in the Servcies tab in NODE1 and NODE2. 8.If i fail the resources from NODE1 to NODE2 ,The SQL Server,SQL Server Agent and SQL Anaylisis resources are failing.on going to the service tab of NODE 2 I reset the password for these services,the services come online. 10.The Cluster resources and MSDTC Resources are Failing over successfully.They are coming online successfully. 11,I have a problem with the SQL Server Resources,even if i failback to NODE1 from NODE2,the same resources are failing again.
I have a failed sql cluster setup on Windows 2003 OS cluster. sql will not uninstall on node 1 because it says the group name was not specified in the template.ini file for the cluster. The OS cluster nodes have been evicted from the cluster. The OS cluster is no longer available to provide a group name for.
SQl uninstall process process is failing because of the error mentioned above.
I want to completely , uninstall SQL server from both nodes, clean up Windows Server and install just a default instance of SQL server on just one of the machines, The cluster can wait.
A few months ago, I was trying to install SQL Server 2005 SP2 on a cluster (Active-Active), the Cluster has 3 instances, 2 lives in one node and the other one in the other node. When I try to make the deployment an error message appear, I do not have the error right now but it€™s something like €śCould not connect to the passive node, installation failed€?. The worst part of the error was all instances shut down and I couldn€™t bring on line and I have to reinstall all instances. I need to install SP2 but I€™m a little afraid fail again. Do you know the best way to deploy the SP2 on a cluster? Maybe move all instances in one node before install SP2? Can you help me with your comments. Do you think I have problems with the windows cluster?
I'm building an SQL Server 2005 cluster on a Windows 2003 cluster. Windows 2003 cluster and MSDTC service are all up and running properly. No problems there, but when I try to install SQL Server 2005 as a cluster service, it fails. The installation goes past the stage where it validates both the nodes and doesn't find any issue there, but when it tries to install fiels it fails. It fails on node 2. When I checked the scduled installer job it creates on node2 to install, the job never seems to run and fails. I'm using only one user account to setup windows cluster MSDTC and SQL Server. Now the complications: It is 64 bit Windows 2003 and SQL Server 2005. Also, the node 1 is built to be a domain controller as well.
When using this connection string, the connection to MAIN is alrigth, but when we simulate a unavailability situation on "MyBase" or on the entire MAIN instance, the new connection are joining the MAIN and not the BCKUP SQL Server.
We tryed several Connection Strings including Failover_Partner, Initliag Catalog instead of database... but no one succed in joining the BCKUP SQL Server.
I precise that the DNS on the PC that connect to SQL server is configured and both MAIN and BCKUP are resolved in command line or in explorer.
Is there an other driver that must be used, or is there an other parameter to set in the connection string ?
I am trying to install multi instances on my server cluster 2003 R2 Sp2. Because of the compatibility issues with my services I need to install both SQL 2000 and 2005. With 2000 I can easily specify the instance and servername. The server name can be the same, but the instance has to be different. Is this true for 2005? I have found so far that for every new instance that you create that you need to have a different virtual server name. How can you utilize the same virtual name and have multi insances
When using this connection string, the connection to MAIN is alrigth, but when we simulate a unavailability situation on "MyBase" or on the entire MAIN instance, the new connection are joining the MAIN and not the BCKUP SQL Server.
We tryed several Connection Strings including Failover_Partner, Initliag Catalog instead of database... but no one succed in joining the BCKUP SQL Server.
I precise that the DNS on the PC that connect to SQL server is configured and both MAIN and BCKUP are resolved in command line or in explorer.
Is there an other driver that must be used, or is there an other parameter to set in the connection string ?
We have about a dozen SQL server 2000 Enterprise Edition servers in house. Our goal is to set up a cluster SQL server 2005 and consodiate the existing dozen servers to a few servers for easy manage and maintainence. So there are 3 things that we want to accomplish:
1. upgrade to SQL server 2005,
2. Consolidate existing servers
3. Make a cluster server to get high availability
But I'm sure what's the right order to acheive them. To upgrade each server to 2005 and then move them to cluster server? or set up the cluster server in 2005 and restore existing dbs to the cluster server. upgrade first or cluster first? upgrade first or consolidate first? pros and cons? upgrade or backup/restore? What do you recommend? We have lots of stored procedures, views and triggers, DTS packages and some replications. Any insight will be greatly appreciated.
I would like to install SQL server 2005 cluster on Windows 2003 cluster. Is domain controller (AD and DNS) necessary for the SQL server 2005 cluster? If yes, may I install it on one of the SQL server 2005 cluster nodes? Thanks in advance
Hello All, I am trying the following script to upgrade SQL Server 2005 SP1 to SP2. I have an Active Passive cluster configuration. I have default instances of SQL Server. I am using the following script.
The sql server install fails to run. When I used the above command with just
start /wait c:1sqlserversp2SQLSERVER2005SP2-KB921896-x86-ENU.exe /quiet still the summary.txt file came with authentication success and that is all. I changed the above script and did
start /wait c:1sqlserversp2SQLSERVER2005SP2-KB921896-x86-ENU.exe /instancename=instancename of the cluster
This worked, however the install patched the passive node (DB engine, all the cluster unaware components) but failed to patch the DB engine on the Active node. I had to run the SQL Server sp2 install manually but still it did not patch the DB engine on the primary node
1. Can someone please help me with this issue as I want the unattended install to work. so it installs both active and passive node. I will post the final output and also the ADS script to do this as a bonus if this works.
Here is the summary.txt file.
********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID msftesql Database Services Service 5152 MSSQLSERVER Database Services Service 4412 ResrcMon.exe Database Services Application SHOMSCSService 4688 ********************************************************************************** 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): 2153 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 29506 Error Description : MSP Error: 29506 SQL Server Setup failed to modify security permissions on file D:Microsoft SQL ServerMSSQL.1MSSQLData for user sqlservice. 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. ---------------------------------------------------------------------------------- Product : Integration Services Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- 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): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- 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: 29506
My question is, I'd like my actual cluster to have 4 servers. The virtual server that will be running SQL 2005 will only be installed on 2 of those nodes. Will this work or do I have to split my cluster in to 2 to meet the SQL Server 2005 2 node failover limitation? A basic config for the cluster would be like below....
ClusterSQLNode Active SQL 2005 Server ClusterExchNode Active Exchange Server ClusterAppNode Active Application Server ClusterFailoverNode Failover SQL 2005 Failover Exchange Failover Application
Will SQL 2005 install in a 4 server cluster if I only install it on to two of the nodes? Any potential gotchas?
I have a problem with DTS - ActiveXScripting that it cannot initialize the script engine, I have the backward compatibility stuff installed, even tried a repair but still does not work.
Many thanks for any help you can provide on this problem.
Paul
Error Information below:
Date 17/04/2007 13:07:32 Log Job History (Test ActiveX Script)
Step ID 1 Server GBCONV1A002V03 Job Name Test ActiveX Script Step Name Step 1: Exec TestActiveX script Duration 00:00:01 Sql Severity 0 Sql Message ID 0 Operator Emailed Operator Net sent Operator Paged Retries Attempted 0
Message Executed as user: WW004ConSrvSQLAgentA002. ...TSStep_DTSActiveScriptTask_1 DTSRun OnError: DTSStep_DTSActiveScriptTask_1, Error = -2147220487 (800403F9) Error string: ActiveX Scripting was not able to initialize the script execution engine. Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts80.hlp Help context: 4500 Error Detail Records: Error: -2147220487 (800403F9); Provider Error: 0 (0) Error string: ActiveX Scripting was not able to initialize the script execution engine. Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts80.hlp Help context: 4500 DTSRun OnFinish: DTSStep_DTSActiveScriptTask_1 Error: -2147220440 (80040428); Provider Error: 0 (0) Error string: Package failed because Step 'DTSStep_DTSActiveScriptTask_1' failed. Error source: Microsoft Data Transformation Services (DTS) Package Help file: ... Process Exit Code 1. The step failed.
I am installing SSRS 2005 with the following scenario:
- Report Server and Report Manager will be installed on web server
- The repository databases (ReportServer and ReportServerTempDB) will be hosted in SQL2005 cluster server.
Both servers are running Win2003 SP1, SQL/SSRS 2005 SP1
When I try to browse the ReportServer virtual directory from IIS on the web server, the system keep asking username and password. After 3 times trials and it failed eventhough the username and password is correct.
The error message is:
HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials. Internet Information Services (IIS)
I've been searching on the web and found couple of articles talking about this issue. I've tried some of them like: http://support.microsoft.com/kb/887993 or even this one: http://groups.google.ca/group/microsoft.public.sqlserver.reportingsvcs/browse_frm/thread/991c9178ceab8f58/8f1a447aa60ad837?lnk=st&q=reporting+services+the+server+is+not+responding&rnum=3&hl=en#8f1a447aa60ad837
But this doesn't work.
I've checked both event viewer both web server and SQL server, but I can't see any information that tell me what had happened.
I also look at BOL, but doesn't help much.
Is there anyone can help me or point me to the right direction? Is there any guide document that explains step-by-step how to install SSRS in my scenario or similiar?
I am setting up a clustered sql 2005 to test replciation and I am having trouble setting the server as a distributor. I get the following message
* SQL Server could not configure xxxx as a Distributor.
Only replication jobs or job schedules can be added, modified, dropped or viewed through replication stored procedures. Changed database context to 'master'. (Microsoft SQL Server, Error: 22538)
I have upgraded our test server and on non cluster production machine. My next server is a cluster and I don't have a test cluster server. Do I upgrade the active node and that is all or am I going to need to fail it over and upgrade the other node.
Also the prerequesite for the upgrade advisor is .net 2.0 I am going to up that on each server one at a time but I am only going to add the upgrade advisor to one node is that ok.
I read the SP1 documentation and it clearly states only patch the active node and do not patch the inactive nodes.
I have no idea how to apply "fixes" or updates to SQL Server when it is running on a cluster.
We are currently running SQL Server 2005 with SP2. The version would be Microsoft SQL Server 2005 - 9.00.3042.00 (X64) Feb 10 2007 00:59:02 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
I am hoping that someone can tell me of a document that exists, that includes the very basics, on how to do this. I need something that says go to the cluster and do these steps in this order, etc. from start to finish.
