Installation Bug Found SQL Server 2005
Oct 28, 2005Hi!
View 24 RepliesHi!
View 24 RepliesHi Everyone,
I have problem when installing SQL 2005 Enterprise to my Windows 2003 R2 cluster. I install the SQL instance on the first node in my cluster, it analyses the cluster and comes up with no errors or warnings, i answer all the installation questions and proceed with the installation. When installing the SQL engine I see the status changing as the instance is started and then stopped again etc, finally the status changes to "removing backup files" when it get an error that reports:
"The setup has encountered an unexpected error while Completing Commit. The error is: The specified module could not be found."
Unfortunately there isnt any more information to go on. Any help would be appreciated.
I cannot find sql server configuration manager installed in cluster. but the installation is complete. what should i do
View 4 Replies View RelatedHi every one,
I'd like to install SQL SERVER 2005 Express Edition ,I begin to install it from DVD but during the installation it dosn't ask me about any instance and after installation there isn't SQLExpress service and I can't use sql server .(there are not MSSQL and Binn directory in sql server 2005) but when I install visual studio 2005 and after that I install sql server 2005 it ask me for name of instance and with this way every thing is ok and I use sql server completely.
I 'd like to know the complete installation of sql server 2005 is depend on installation of visual studio 2005 befor it ?if not how can I introduce any instance after installation of sel server 2005 .
I installed Visual Studio 2005 Professional then after that was installed and running, I tried to install the the SQL Server 2005 Developer's Edition which installed but I do not get the SQL Server 2005 Studio Manager. I have remove and reinstalled but it never gets installed. Any ideas?
Chuck
Sorry if someone already covered this, but I can't find anything about it.
I just installed (3 hours ago actually) SQL2005 Standard Edition (from the Launch event) on my machine, and i don't seem to have a shortcut to the SQL Server 2005 Management Studio anywhere.
I looked for a likely executable, but couldn't find it anywhere. This wouldn't bother me as much if I could use Enterprise Manager from 2K, but SQL2005 will not allow it to register.
How do I get this going? There are people here that want to inspect it's features, etc. I haven't got anything to show them.
I just installed Sql Server Reporting Services 2005 on a Windows Server 2003 R2 x64 server. I configured Reporting Services through the Reporting Services Configuration tool and everything has a green checkmark.
I'm trying to connect to the webservice, but keep getting 404 not found errors. I've tried putting the following into a web browser and all return a 404 error:
http://msql01/reports/
http://msql01/reportserver/
http://msql01/reportserver/reportservice.asmx?wsdl
http://msql01/reportserver/reportservice2005.asmx?wsdl
I've tried edting the RSWebApplication.config file using the following configurations (restarting IIS afterwards) without any luck:
<UI>
<ReportServerUrl></ReportServerUrl>
<ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory>
<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>
</UI>
and
<UI>
<ReportServerUrl>http://msql01/ReportServer/</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>
</UI>
Any help is appreciated!
Thanks,
Rob
While waiting for the fax of instructions to contact MS Support, I thought I would post here (tried several times and no fax...)
We get this message in the log file and then all hell breaks loose until it resets memory. The SQL Service continues working but nobody can connect for about 5 minutes and then is seems to reset itself. This has happened three times over the past two weeks. Only one time it did create the SQLDUMP files but all three occurences have practically the same entries.
We are running SQL Server 2005 x64 SP2 under Windows 2003 x64 SP1. We have 4GB RAM and SQL is configured to use 2GB of it. We have a large number of databases (about 400) on this one instance that experiences this problem. The server itself is not under a tremendous load. All of the databases were recently upgraded from SQL 2000 SP4 32 bit instance. The first occurence happened just days after the migration.
----- Log Entries -----
LazyWriter: warning, no free buffers found.
2007-06-14 14:15:56.18 spid3s
Memory Manager
VM Reserved = 4415288 KB
VM Committed = 4398048 KB
AWE Allocated = 0 KB
Reserved Memory = 1024 KB
Reserved Memory In Use = 0 KB
2007-06-14 14:15:56.18 spid3s
Memory node Id = 0
VM Reserved = 4409528 KB
VM Committed = 4392376 KB
AWE Allocated = 0 KB
SinglePage Allocator = 1951840 KB
MultiPage Allocator = 81680 KB
2007-06-14 14:15:56.18 spid3s
MEMORYCLERK_SQLGENERAL (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 39264 KB
MultiPage Allocator = 21944 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_SQLBUFFERPOOL (Total)
VM Reserved = 4214784 KB
VM Committed = 4198400 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 0 KB
MultiPage Allocator = 8 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_SQLQUERYEXEC (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 264 KB
MultiPage Allocator = 104 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_SQLOPTIMIZER (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 26816 KB
MultiPage Allocator = 96 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_SQLUTILITIES (Total)
VM Reserved = 120 KB
VM Committed = 120 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 4728 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_SQLSTORENG (Total)
VM Reserved = 96768 KB
VM Committed = 96768 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 62192 KB
MultiPage Allocator = 27624 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_SQLCONNECTIONPOOL (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 4392 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_SQLCLR (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_SQLSERVICEBROKER (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 624 KB
MultiPage Allocator = 320 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_SQLHTTP (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_SNI (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 568 KB
MultiPage Allocator = 16 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_FULLTEXT (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 16 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_SQLXP (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 16 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_BHF (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 336 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_SQLQERESERVATIONS (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8192 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_HOST (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 24 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_SOSNODE (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 42376 KB
MultiPage Allocator = 27392 KB
2007-06-14 14:15:56.20 spid3s
MEMORYCLERK_SQLSERVICEBROKERTRANSPORT (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 48 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_OBJCP (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 352016 KB
MultiPage Allocator = 432 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_SQLCP (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 953192 KB
MultiPage Allocator = 3088 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_PHDR (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 308728 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_XPROC (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 56 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_TEMPTABLES (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 128 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_NOTIF (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 16 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_VIEWDEFINITIONS (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 16 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_XMLDBTYPE (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_XMLDBELEMENT (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_XMLDBATTRIBUTE (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_STACKFRAMES (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 0 KB
MultiPage Allocator = 8 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_BROKERTBLACS (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 96 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_BROKERKEK (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_BROKERDSH (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_BROKERUSERCERTLOOKUP (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_BROKERRSB (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_BROKERREADONLY (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 32 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_BROKERTO (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_EVENTS (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 16 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
CACHESTORE_SYSTEMROWSET (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 43744 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
USERSTORE_SCHEMAMGR (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 30632 KB
MultiPage Allocator = 16 KB
2007-06-14 14:15:56.20 spid3s
USERSTORE_DBMETADATA (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 39856 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
USERSTORE_TOKENPERM (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 14536 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
USERSTORE_OBJPERM (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 14904 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
USERSTORE_SXC (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 936 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
OBJECTSTORE_LBSS (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 64 KB
MultiPage Allocator = 400 KB
2007-06-14 14:15:56.20 spid3s
OBJECTSTORE_SNI_PACKET (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 6584 KB
MultiPage Allocator = 48 KB
2007-06-14 14:15:56.20 spid3s
OBJECTSTORE_SERVICE_BROKER (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 272 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.20 spid3s
OBJECTSTORE_LOCK_MANAGER (Total)
VM Reserved = 8192 KB
VM Committed = 8192 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 4232 KB
MultiPage Allocator = 0 KB
2007-06-14 14:15:56.21 spid3s Buffer Distribution: Stolen=22764 Free=0 Cached=221235
Database (clean)=268686 Database (dirty)=3406
I/O=0, Latched=5
2007-06-14 14:15:56.21 spid3s Buffer Counts: Committed=516096 Target=523990 Hashed=272097
Internal Reservation=104798 External Reservation=1022
Stolen Potential=252769
Min Free=128 Visible=523990
Available Paging File=4634734592
2007-06-14 14:15:56.21 spid3s Procedure Cache: TotalProcs=11768 TotalPages=202189 InUsePages=950
2007-06-14 14:15:56.21 spid3s Process physical/virtual memory pressure: 0/0 System physical memory pressure: 0
2007-06-14 14:15:56.23 spid3s Global Memory Objects:
Resource= 2880
Locks= 532
SE Schema Mgr= 3653
SQLCache= 1622
Replication= 3
ServerGlobal= 49
XPGlobal= 2
Xact= 165
SETLS= 4
DatasetMemObjs= 8
SubpDescPmos= 4
SortTables= 2
2007-06-14 14:15:56.23 spid3s Query Memory Objects: Grants=8 Waiting=0 Maximum=226034 Available=225010 Limit=226048
2007-06-14 14:15:56.23 spid3s Query Memory Objects: Next Request=0 Waiting For=0 Cost=0 Timeout=0 Wait Time=0 Last Target=237945
2007-06-14 14:15:56.23 spid3s Small Query Memory Objects: Grants=0 Waiting=0 Maximum=11895 Available=11895 Limit=11895
2007-06-14 14:15:56.24 spid3s
Optimization Queue
Overall Memory = 3440517120 Target Memory = 1485357056 Last Notification = GROW Timeout = 6 Early Termination Factor = 5
2007-06-14 14:15:56.24 spid3s
Small Gateway
Configured Units = 16 Available Units = 16 Acquires = 0
Waiters = 0 Threshold Factor = 380000 Threshold = 380000
2007-06-14 14:15:56.24 spid3s
Medium Gateway
Configured Units = 4 Available Units = 4 Acquires = 0
Waiters = 0 Threshold Factor = 12 Threshold = -1
2007-06-14 14:15:56.24 spid3s
Big Gateway
Configured Units = 1 Available Units = 1 Acquires = 0
Waiters = 0 Threshold Factor = 8 Threshold = -1
2007-06-14 14:15:56.24 spid3s
MEMORYBROKER_FOR_CACHE
Allocations = 221239
Rate = 0
Target Allocations = 379816
Future Allocations = 0
Last Notification = GROW
2007-06-14 14:15:56.24 spid3s
MEMORYBROKER_FOR_STEAL
Allocations = 22741
Rate = 0
Target Allocations = 181318
Future Allocations = 0
Last Notification = GROW
2007-06-14 14:15:56.24 spid3s
MEMORYBROKER_FOR_RESERVE
Allocations = 1024
Rate = 0
Target Allocations = 253810
Future Allocations = 95233
Last Notification = GROW
2007-06-14 14:39:56.82 Server Resource Monitor (0x1180) Worker 0x000000008000C1C0 appears to be non-yielding on Node 0. Memory freed: 148160 KB. Approx CPU Used: kernel 125 ms, user 62 ms, Interval: 65000.
2007-06-14 14:40:56.84 Server Resource Monitor (0x1180) Worker 0x000000008000C1C0 appears to be non-yielding on Node 0. Memory freed: 218536 KB. Approx CPU Used: kernel 328 ms, user 93 ms, Interval: 125046.
2007-06-14 14:41:56.84 Server Resource Monitor (0x1180) Worker 0x000000008000C1C0 appears to be non-yielding on Node 0. Memory freed: 288960 KB. Approx CPU Used: kernel 515 ms, user 125 ms, Interval: 185046.
2007-06-14 14:42:56.84 Server Resource Monitor (0x1180) Worker 0x000000008000C1C0 appears to be non-yielding on Node 0. Memory freed: 366008 KB. Approx CPU Used: kernel 718 ms, user 171 ms, Interval: 245046.
2007-06-14 14:43:56.84 Server Resource Monitor (0x1180) Worker 0x000000008000C1C0 appears to be non-yielding on Node 0. Memory freed: 435992 KB. Approx CPU Used: kernel 968 ms, user 296 ms, Interval: 305046.
2007-06-14 14:44:56.84 Server Resource Monitor (0x1180) Worker 0x000000008000C1C0 appears to be non-yielding on Node 0. Memory freed: 505160 KB. Approx CPU Used: kernel 1203 ms, user 390 ms, Interval: 365046.
2007-06-14 14:45:56.84 Server Resource Monitor (0x1180) Worker 0x000000008000C1C0 appears to be non-yielding on Node 0. Memory freed: 572488 KB. Approx CPU Used: kernel 1468 ms, user 468 ms, Interval: 425046.
2007-06-14 14:46:56.84 Server Resource Monitor (0x1180) Worker 0x000000008000C1C0 appears to be non-yielding on Node 0. Memory freed: 639056 KB. Approx CPU Used: kernel 1703 ms, user 500 ms, Interval: 485046.
We have an application server running Windows Server 2000 with Sp4. When we use the ODBC data sources connection software, it shows the SQL Server 2000 servers in the drop down box, but none of the new 2005 servers. If we enter the 2005 server name and try to connect, we get the 'Specified SQL Server not found' error message. The connection works fine from a newer Windows XP box and remote connections is enabled. My guess is that we need a new ODBC to connect to SQL Server 2005, but I can't find anything that says this.
View 2 Replies View RelatedI'm Getting "Report Server WMI Provider error: Not Found" when trying to Grant Database Access while configuring the Reporting Sevices Integration. Logging in fine to the DB. Tried all the WMI troublshooting and can't find any issues there. Any tips?
Many Thanks!!
Hi: I try to install SQL Server 2005 but it gives warning message. My computer configuration is Pentium III 900 HZ, 512 RAM with operating system windows 2000 Pro and service pack 4 and 10 GB free space. It gives warning on operating system. Also Visual Studio. Net 2005 is already installed on my comupter.
- SQL Server Edition Operating System Compatibility (Warning)
Messages
* SQL Server Edition Operating System Compatibility
* Some components of this edition of SQL Server are not supported on this operating system. For details, see 'Hardware and Software Requirements for Installing SQL Server 2005' in Microsoft SQL Server Books Online.
- Operating System Minimum Level Requirement (Success)
Messages
* Operating System Minimum Level Requirement
* Check Passed
- Operating System Service Pack Level Requirement. (Success)
Messages
* Operating System Service Pack Level Requirement.
* Check Passed
hi,
I have to install SQL Server 2005 on SBS Standard 2003. I am already running Sql Server Desktop Engine with three instances: MSSQL$SHAREPOINT, MSSQL$SBSMONITORING, MSSQL$BLUECOAT. I am wondering how the installation is gonna affect my system. I do need SQL Server 2005 for the new financial software which is intalled 2morrow. What shall I put as the instance during the installation. Is Sql Server Desktop Engine gonna be replaced by SQL Server 2005?
help!
i had downloaded .Net and SQL Server 2005 from microsoft site. In SQL Server 2005 after installation i get only Configuration Tools and 3 subtopics. I am able to create table only through . NET but am not able to work independantly with SQL Server 2005. Can anyone advice me!!
View 2 Replies View Related--------------------------------------------------------------------------------
Dear Sir,
While Installing Sql 2005 Express in IBM POS machine, the following Error comes.
The Sql Server Service has failes to Start
MESSAGE ID : 29503
Message Source : Setup.rll
evt Type : Sqlsetuplibservice.cpp@do_sqlscri
i Tried to other pos machine also , same problem Comes. But Normal Desktop pc it is running fine.
Please guide me
Thanks
Hi All,
I trying to Install on Windows XP with Service pack 4, OS.
I am trying to install the Developer Edition of SQL Server 2005 version for which it is not able to load many packages as it says IIS services, Integration Services Etc,. were not installed and if they were ignored then rest will be loaded and thereafter I could not either login or invoke either any.
Can anyone suggest me where it went wrong and what I need to do with instructions.
Thanks in advance.
Unfortunately for me, I am not a DBA - even though I have always filled that role where ever I have been. That being said, I have always been fortunate enough to have someone else more knowledgeable than I to perform the initial build of the SQL Servers I have used and managed. So, I have the following question...
I just finished installing and configuring a new dedicated SQL Server (it is nice too). One of the included discs it he MSDN Library. Do I need to install that too? Is there any reason to or not to install it? I would appreciate any feedback.
- - - -
- Will -
- - - -
http://www.strohlsitedesign.com
http://blog.strohlsitedesign.com/
http://skins.strohlsitedesign.com/
Hi,
SQL Server 2005 has been installed on windows server 2003 machine by the support team.
Microsoft SQL Server Management Studio 9.00.3042.00
Now this machine has been passed on to me to create databases, tables, etc...
On this server, I open the management studio and I get the connect to server windows.
What should the entries in the connect to server window be for me to get to the next stage where I can start building databases.
At present, I tried local or localhost and windows/sql authentication.
Still can not get to the management studio window.
Any thoughts please?
Thanks
Hi,
I have a couple of questions reagrding SQL Server 2005 SP2?
1) Do I need to install SP1 and its accumulative hotfixes before applying SP2??
2) Anyone know what is SQL Server 2005 V 9.0.3033?? I saw it in a couple of SQL 2005 servers that suppose to have SP2 installed. I thought SP2's version is 3042??
Thanks for any input.
Hi,
We have the Windows server 2003 R2 Service PAck 2 , we got updated to this version after i installed automatic updates today,and i am having problems with setting up maintenance plan in SQL server 2005 (9.0.1399)
Hence i am trying to install Sql server 2005 SP1, but the read me file says that this installation is compatible only with Windows server 2003 SP1
Also, i received this error when i tried to install SQL server 2005 SP1 yesterday
"The image file hotfix.exe is valid, but is for a machine type other than the current machine"
I am confused, Can someone help me out in this regard?
Thanks in advance
Hi,
I'm trying to re-install the ms sql server 2005 but I keep getting the following message:
TITLE: Microsoft SQL Server 2005 Setup
------------------------------
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
------------------------------
This is my second time installing the ms sql server. I couldn't create a new database connection using odbc, I constantly got error messages so i decided to install it with windows and sql authentication (earlier i installed it only with windows authentication).
But I can't complete my installation.
Can some please help me with this.
Thank you!!
Soen
Hello Experts,I have a Windows Server 2003 For Small Business Server SP 2. Is it possible to install SQL Server 2005 on Windows Server 2003? I am intending to switch to SQL Server 2005 from SQL Server 2000 (on Windows Server 2000).Please advice. Thanks in advance.Regards,Suman Ghosh
View 6 Replies View RelatedI have just purchased SQL Server 2005 and a new Dell 2800 server to run it on. I was told by my Dell rep to configure the server with the following drives. 2 - 36GB drives in a RAID 0 (15,000 RPM), 2 - 73GB drives in a RAID 0 (10,000 RPM) and 3 - 146GB drives in a RAID 5 (10,000 RPM). Dell pre-installed the OS on the 36GB drive. I was told to install SQL on the 73GB drives and the data (primarily TIFF images) on the 146GB. The server is a 64bit machine with Windows 2003 Server and 4GB of RAM. I was told to put the transaction logs on a different physical drive that the database to speed the writes. Is this a correct installation? Is there any information on a best practice installation? I have spent about 6 hours on MS and Google trying to find an answer. Thanks for any help you can give. Recap of Dell recommendation:
2 - 36GB Mirrored Drives = OS
2 - 73BG Mirrored Drives = SQL Server 2005
3 - 146GB RAID 5 Drives = Data (Images)
Is this correct?
Where should the Transaction Logs Be?
While installing Microsoft SQL Server 2005 Express Edition the installation did not complete because of WMI configuation of my system.
Can somebody help!
View 1 Replies View Related
I have sql server 2000 on my PC. If I want to upgrade to SQL Server 2005 should I have to uninstall the Sql server 2000 and install Sql server 2005. Or can i install the sql server 2005 directly.
View 2 Replies View RelatedHI All,
After i installed SQL Server 2005 workgroups edition to my Laptop, P4 and 1 Giga memory. I had a problem.
my problem is: when i start my laptop need 4 minutes to start the windows xp pro edition.
then I format my laptop and install the windows again, and every thing works fine, but I installed the SQL again and i had same problem with windows startup, there is nothing related to SQL in ;msconfig utilities.
do you have any tip about this problem ?
Thank You
Hi, I am new to the whole ASP and SQL data base and have a basic question.I installed visual studio 2008 and SQL server 2005 developer edition in my computer. However it seems like the SQL installation is not installing all the components I need. I tried to reinstall it again and the only thing it installs is the "configurations tools". Below is a screen shot of my installation.Is this correct? How to a get the other tools installed? thx in advance,
View 1 Replies View RelatedHey guys -
I am busy testing SQL 2005 Server Unattended installations and have a quick question. Microsoft specifies the following code for command line installation:
Start /wait <CD or DVD Drive>serverssetup.exe /qb INSTANCENAME=<InstanceName> ADDLOCAL=All PIDKEY=<pidkey value with no "-"> SAPWD=<StrongPassword>
SQLACCOUNT=<domainuser>
SQLPASSWORD=<DomainUserPassword>
AGTACCOUNT=<domainuser>
AGTPASSWORD=<DomainUserPassword> SQLBROWSERACCOUNT=<domainuser>
SQLBROWSERPASSWORD=<DomainUserPassword>
Here is a link to the installation pages: Click Here (http://msdn2.microsoft.com/en-us/library/ms144259.aspx)
My question is what are all the different accounts for?
Any help will be appreciated.
Thanks
Reghardt
I am having problems installing SP1 successfully. So far I've tried it on two separate Windows 2003 server boxes running SQL Server 2005 Standard v9.0.1399.
The first upgraded successfully all over services except the SQL server itself. Reporting services then failed due to database version mismatch but that was easily fixed. The other box doesn't have anything other than SQL2005 and components were upgraded but the database upgrade failed. I got the generic "send this error to microsoft" message.
I've tried other suggested fixes on this board but none have worked so far.
The Logfile seems to go haywire at about this point:
Property(S): REINSTALLMODE = omus
Property(S): Privileged = 1
Property(S): RedirectedDllSupport = 2
Property(S): REINSTALL = All
Property(S): PATCH = \TESTC$SP1HotFixSQLFilessqlrun_sql.msp
Property(S): MsiWin32AssemblySupport = 5.2.3790.1830
Property(S): MsiNetAssemblySupport = 2.0.50727.42
Property(S): Date = 6/15/2006
Property(S): ProductToBeRegistered = 1
Property(S): Time = 13:52:47
Property(S): ProductState = 5
Property(S): TTCSupport = 1
Property(S): TRANSFORMS = :SqlRun01.mst;:InstID01.mst;:InstName01.mst
Property(S): ColorBits = 32
Property(S): TextHeight = 16
Property(S): PackageCode = {3185FC73-41E0-43F4-97DF-2254C4D7C667}
Property(S): BorderSide = 1
Property(S): BorderTop = 1
Property(S): CaptionHeight = 19
Property(S): ScreenY = 1024
Property(S): ScreenX = 1280
Property(S): SystemLanguageID = 1033
Property(S): SQL200532Hotfix2047 = \TESTC$SP1HotFixSQLFilessqlrun_sql.msp
Property(S): BrowseAuto.2FC2D269_8625_4826_BB3F_F9059090CB38 = 0
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 1729
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C4:30) [13:52:47:807]: Product: Microsoft SQL Server 2005 -- Configuration failed.
MSI (s) (C4:30) [13:52:47:807]: Attempting to delete file C:WINDOWSInstaller6770f.msp
MSI (s) (C4:30) [13:52:47:807]: Unable to delete the file. LastError = 32
MSI (s) (C4:30) [13:52:47:839]: Cleaning up uninstalled install packages, if any exist
MSI (s) (C4:30) [13:52:47:839]: MainEngineThread is returning 1602
MSI (s) (C4:08) [13:52:47:839]: Destroying RemoteAPI object.
MSI (s) (C4:B0) [13:52:47:839]: Custom Action Manager thread ending.
=== Logging stopped: 6/15/2006 13:52:47 ===
MSI (c) (D4:90) [13:52:47:854]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (D4:90) [13:52:47:854]: MainEngineThread is returning 1602
=== Verbose logging stopped: 6/15/2006 13:52:47 ===
Help!
I have uninstalled SQL server 2000 & am installing SQL Server 2005, I'm getting follwing error.
=== Verbose logging started: 3/27/2008 10:24:26 Build type: SHIP UNICODE 3.01.4000.4039 Calling process: C:Program FilesMicrosoft SQL Server90Setup
Bootstrapsetup.exe ===
MSI (c) (88:78) [10:24:26:828]: Resetting cached policy values
MSI (c) (88:78) [10:24:26:828]: Machine policy value 'Debug' is 0
MSI (c) (88:78) [10:24:26:828]: ******* RunEngine:
******* Product: F:ServersSetupSqlRun_SQL.msi
******* Action:
******* CommandLine: **********
MSI (c) (88:78) [10:24:26:828]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (88:78) [10:24:26:828]: Grabbed execution mutex.
MSI (c) (88:78) [10:24:26:828]: Cloaking enabled.
MSI (c) (88:78) [10:24:26:828]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (88:78) [10:24:26:828]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (7C:94) [10:24:26:843]: Grabbed execution mutex.
MSI (s) (7C:54) [10:24:26:843]: Resetting cached policy values
MSI (s) (7C:54) [10:24:26:843]: Machine policy value 'Debug' is 0
MSI (s) (7C:54) [10:24:26:843]: ******* RunEngine:
******* Product: F:ServersSetupSqlRun_SQL.msi
******* Action:
******* CommandLine: **********
MSI (s) (7C:54) [10:24:26:843]: Note: 1: 2203 2: F:ServersSetupSqlRun_SQL.msi 3: -2147287010
MSI (s) (7C:54) [10:24:26:843]: MainEngineThread is returning 1620
MSI (c) (88:78) [10:24:26:843]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (88:78) [10:24:26:843]: MainEngineThread is returning 1620
=== Verbose logging stopped: 3/27/2008 10:24:26 ===
SUMMARY.txt (C:Program FilesMicrosoft SQL Server90Setup BootstrapLOG) has follwing contents...
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Thu Mar 27 09:57:45 2008
Machine : ADITYA
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_1.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_1.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_2.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_2.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_2.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_2.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_3.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLNCLI_2.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_3.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_3.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_3.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_4.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_4.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_4.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_5.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLNCLI_3.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_5.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_5.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_4.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_6.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLNCLI_4.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft Visual Studio 2005 Premier Partner Edition - ENU
Product Version : 8.0.50727.42
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_PPESku_1.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_6.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BOL_1.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_6.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_5.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server 2005 Integration Services
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_DTS.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLXML4_1.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLXML4_2.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server 2005 Analysis Services
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_AS.log
--------------------------------------------------------------------------------
Machine : ADITYA
Product : Microsoft SQL Server 2005 Notification Services
Product Version : 9.00.1399.06
Install : Failed
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_NS.log
Error Number : 1602
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Thu Mar 27 10:28:36 2008
List of log files:
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_Core(Local).log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLNCLI_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLNCLI_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_4.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_4.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_4.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_5.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLNCLI_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_5.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SqlWriter_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_5.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_4.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_6.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLNCLI_4.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_PPESku_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_6.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BOL_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_6.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_5.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_DTS.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLXML4_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQL.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLXML4_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_AS.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_NS.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_Datastore.xml
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_.NET Framework 2.0.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_Core.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_.NET Framework 2.0 LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_.NET Framework Upgrade Advisor.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_.NET Framework Upgrade Advisor LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_.NET Framework Windows Installer.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_.NET Framework Windows Installer LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_Support.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SCC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_WI.log
Your help is appreciated.
aditya
I am running Windows XP SP2. The installation fails with
SQL Server coul not connect to the database service for server configuration.
[SQL Native Client]Unable to complete login process due to delay in opening server conection.
Please help in getting this working, I have not been able to find anything by googling thus far.
Regards
Harald Hedlund
Dear Sir/madam
While installing sql server express 2005 get an error message install latest version using sqlnci.msi . Please let me know from where i can find or download sqlnci.msi
This error comes while installing native client option
With regards
Anil
I received the following error when installing SQL Server 2005:
The setup has encountered an unexpected error while Installing performance counters. The error is: -1073741790