SQL 2005 x64 exception
Recently We've migrated SQL 2005 x86 Enterprise running on Windows 2003 Enterprise to new hardware where is running Windows 2008 SP2 and SQL 2005 x64 SP4 with CU3. We migrate users (with standard approach by Microsoft) and application databases
to new server. Everything is looking ok, applications working. But we've got some SQL exceptions like below.
Is there any known bug related to that? Could someone help us.
Memory
MemoryLoad = 15%
Total Physical = 32733 MB
Available Physical = 27752 MB
Total Page File = 64782 MB
Available Page File = 60344 MB
Total Virtual = 8388607 MB
Available Virtual = 8355366 MB
**Dump thread - spid = 84, PSS = 0x00000000D1A43ED0, EC = 0x00000000D1A43EE0
***Stack Dump being sent to D:\MSSQL.1\MSSQL\LOG\SQLDump0005.txt
* BEGIN STACK DUMP:
* 04/25/14 12:54:30 spid 84
* ex_handle_except encountered exception C0000264 - Server terminating
* Input Buffer 255 bytes -
There is also some output from debugger:
0:000> .ecxr
rax=0000000077207080 rbx=0000000000000000 rcx=0000000016a37d50
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000440
rip=00000000772070bd rsp=0000000016a38240 rbp=000000000000003f
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000287 r12=00000000032fdab0 r13=0000000000000000
r14=00000000000019e4 r15=0000000049b8d00c
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000206
kernel32!RaiseException+0x3d:
00000000`772070bd 4881c4c8000000 add rsp,0C8h
0:000> kC 1000
Call Site
kernel32!RaiseException
sqlservr!DmpGetClientExport
sqlservr!_____SQL______Process______Available
sqlservr!_____SQL______Process______Available
sqlservr!_____SQL______Process______Available
sqlservr!SQLExit
kernel32!UnhandledExceptionFilter
ntdll!RtlpNotOwnerCriticalSection
ntdll!_C_specific_handler
ntdll!RtlIntegerToChar
ntdll!_C_specific_handler
ntdll!RtlRaiseStatus
ntdll!RtlpNotOwnerCriticalSection
ntdll!LdrGetProcedureAddress
sqlshield
sqlservr
0x0
0x0
0x0
0x0
0x0
Hi,
In last days we "close" our SQL to some scanning security applications which could also do some things on our SQL. But it's only a guess. About sqlshield we do the unregister and register DLL's again. Now at last two exception is not the same situation.
Can you see something from there with "Non-yielding Scheduler". Is it also possible that it something wrong with the hardware. We're using new Cisco rack 1U server for that SQL server. I've also read someting about upgrading the BIOS, related to errors
"Non-yielding Scheduler". At the end i can also tell, that the server is alive for a couple of days, if there is no a lot activity on the server, i mean on national holidays, through weekend, etc.
Any new idea?
Thanks,
Matjaž
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.5266.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is Cisco0 - 0
BIOS Date: 08/20/13 06:01:31 Ver: 04.06.05
Current time is 11:17:16 04/30/14.
12 Unknown CPU 9., 14 Mhz processor (s).
Windows NT 6.0 Build 6002 CSD Service Pack 2.
Memory
MemoryLoad = 17%
Total Physical = 32733 MB
Available Physical = 26900 MB
Total Page File = 64782 MB
Available Page File = 59543 MB
Total Virtual = 8388607 MB
Available Virtual = 8355342 MB
***Unable to get thread context - no pss
* BEGIN STACK DUMP:
* 04/30/14 11:17:16 spid 0
* Non-yielding Scheduler
Stack Signature for the dump is 0x00000000000003AD
Similar Messages
-
SQL 2005 x64 poor performance after migration from SQL 2005 x86
Recently We've migrated SQL 2005 x86 SP1 Enterprise running on Windows 2003 Enterprise to new hardware where is running Windows 2008 SP2 and SQL 2005 x64 SP4 with CU3.
In the work day, there are sometime SQL excpetions like this below. On other hand i can also tell that we already found some queries which has some inner joins and where clauses on nvarchar fileds, because of the nature of application. Such a query
is running for about 11 seconds on old SQL server, and about 6 minutes on new SQL server. My main question if is this possible just with a change to new architecture of SQL and more last patches and updates for SQL 2005. Is there any way how to get
this queries running faster, without rewritng them with new ones? Is this also possible this could be also cause for SQL exceptions, which we are facing on SQL server?
About new hardware, for now we can't find it something wrong. There is basic configuration:
Cisco UCS C220 M3S (1U server)
32GB RAM
Intel(R)Xeon® CPU [email protected], 6 core
Disk system: 4xSAS 300GB in RAID5 (OS and DATA) and 2xSATA 1TB in RAID1 (SQL backup)
RAID controller: LSI MegaRAID SAS 9271-8i (with latest driver and firmware)
Part of log of dump file:
2014-05-09 08:30:07.08 spid86 Error: 17311, Severity: 16, State: 1.
2014-05-09 08:30:07.08 spid86 SQL Server is terminating because of fatal exception c0000264. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling.
Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
2014-05-09 08:30:07.08 spid86 Using 'dbghelp.dll' version '4.0.5'
2014-05-09 08:30:07.08 spid86 **Dump thread - spid = 86, PSS = 0x0000000132A67ED0, EC = 0x0000000132A67EE0
2014-05-09 08:30:07.08 spid86 ***Stack Dump being sent to D:\MSSQL.1\MSSQL\LOG\SQLDump0087.txt
2014-05-09 08:30:07.08 spid86 * *******************************************************************************
2014-05-09 08:30:07.08 spid86 *
Thanks for any help,
Matjaž>Is there any way how to get this queries running faster, without rewriting them with new ones?
You need to perform basic performance tuning steps in the new environment.
Software optimization:
http://www.sqlusa.com/articles/query-optimization/
Disk optimization:
http://www.sqlusa.com/bestpractices/configureharddisk/
Memory optimization:
http://www.sqlusa.com/bestpractices/memory-configuration/
REBUILD INDEXES, eliminate missing indexes & UPDATE STATISTICS.
If there is still a problem, look in Activity Monitor for expensive queries. Optimize them. As a general rule, you don't want to have expensive queries in RDBMS.
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012 -
MS SQL 2005 x64 Linked Server to Oracle 10g 32bit
I need to connect to a 10.2.0.4 Oracle DB from a SQL Server 2005 x64 on W2003.
The Instant Client installed is 10.2.0.1 with ODP 10.2.0.3, which is used to connect to another Oracle DB.
I get de error ORA-12154 while doing the linked server query.
Do I really need to update de Instant Client?
Thankx and some more info.
I can reach it with TOAD from my laptop which has Instant Client 11.1.0.7.
I followed several how-tos while configuring the linked server.
The other linked server supposely works but I'm not sure and don't know the Oracle version.Hi sanjay,
but why sysdate is giving me the today's date and when i use getdate ...it does not give me anything..
i am using openquery tooracle data base..usually i have to use Oracle command..
Mo.. -
OraOLEDB.Oracle on x64 Win 2003 connect to Oracle 9.2 from SQL 2005 x64
I know this is an Oracle board but some of you may also support SQL Server like I do and I am hoping someone has had the pleasure of using OraOLEDB.Oracle on 64 bit.
I have a 64 bit SQL Server 2005 SP2 on a Windows 2003 x64. The developer said that he needed to use OLE to talk to Oracle so I went to Oracle and downloaded the 64 bit OraOLDDB driver as recommended in a MS note.
I can connect to Oracle via tnsping and using SQLPlus but I cannot create a linked db successfully.
The linked database errors off with >> Cannot initialize data source for OLE provider "OraOLEDB.Oracle" for Lined Server "X" (Microsoft SQL Server error: 7399) << (manually typed)
Here is the official OS, SQL Server, and Oracle client information:
The OS is Windows Server 2003 Standard x64 edition Service Pack 2 (NT 5.2 build 3790)
The SQL Server 2005 9.0.3042 (x64) [from
Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.086.3959.00
(srv03_sp2_rtm.070216-1710)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 6.0.3790.3959
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790
The OraOLEDB.Oracle driver shows that it is version 10.2.0.3
Oracle "tnsping sid " works
SQLPlus (ver 9.2) works
I have serveral linked databases to Oracle that I have built but all of them are 1- on SQL Server 2000 and 2- are 32 bit. If anyone knows of any additional patches (Windows or Oracle) necessary to resolve this I would appreciate the information. Also there are potential firewall issues though the fact that SQLPus can be used seems to rule this out, but if there are any ports associated with OLE I would like to check on them specifically.
-- Mark D Powell --Thank you for reminding me what I already knew but in my haste to post out a reply I had forgotten to consider looking at the provider properties.
Today I did and the linked database still failed. The though occurred to me a little later to delete and recreate the linked db and bingo I had a working linked database to Oracle. Now I have three of them and the developer should be working with them now.
This is the first time I ever had to change a provider property to get the provider to work. I would have thought that when the Oracle client install process registered the OLE provider with SQL Server 2005 it would be set with the proper defaults to work.
Thanks again to everyone
-- Mark D Powell -- -
SQL Server Error when tryingt to install the CMS DB on SQL Server 2005 x64
I am trying to install BOEXI R3 on w2k3 64-bit OS in a SQL Server 2005 x64 database, I am currently at the installation step where i Specify an exisiting CMS database. I created a System DSN and tested it, and it was successful. So when I got to the screen where I select my datasource I had to check use trusted connection because the datasource would not show up when Use DSN created by WOW64 option was checked. From there I could select the database I created. Oh yeah, I also made the application server local system account part of my DB admins group so it has full access to the database yet when I click next to connect I get a CMS Database Error: STU000226. here is what I have in my log:
ThreadID Message
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: findDFA_LLR: (CmdLineDir) C:Documents and SettingsgsdadminDesktopBOEXI and BSM AnalyticsBOEXI R3 Full Version from SAPpackagedbcheck
sqlrule.llr
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: Loading: database subsystem only
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: loading libary succeeded
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: DatabaseSubsystem::Init()
(Thu Apr 23 20:57:46 2009) 3024 3028 (.wireobinit.cpp:96): trace message: Creating the shared CWireObject::PropertyNameMap
(Thu Apr 23 20:57:46 2009) 3024 3028 (.wireobinit.cpp:118): trace message: Setting static property map
(Thu Apr 23 20:57:46 2009) 3024 3028 (.wireobinit.cpp:125): trace message: CWireObject::InitializeStaticPropertyMap() - reference count: 1
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: initializing subsystem succeeded
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: Loading: done loading subsystem - database subsystem only
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: DatabaseSubsystem::Connect()
(Thu Apr 23 20:57:46 2009) 3024 3028 (.DBConnectionManager.cpp:802): trace message: DBConnectionManager - Setting total target number of connections for pool 0 to 1.
(Thu Apr 23 20:57:46 2009) 3024 3028 (.SQLServerDatabase.cpp:119): trace message: SQLServer error found: ErrorMessage( (Microsoft)[ODBC Driver Manager] Data source name not found and no default driver specified), ErrorCode(0)
(Thu Apr 23 20:57:46 2009) 3024 3028 (.dbutils.cpp:820): trace message: Caught DatabaseSubystem Error: BusinessObjects Enterprise CMS: Unable to connect to the CMS system database "BOEXI_CMS". Reason: (Microsoft)[ODBC Driver Manager] Data source name not found and no default driver specified
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: DatabaseSubsystem::Shutdown()
(Thu Apr 23 20:57:46 2009) 3024 3028 (.wireobinit.cpp:175): trace message: CWireObject::TerminateStaticPropertyMap() - reference count: 1
(Thu Apr 23 20:57:46 2009) 3024 3028 (.wireobinit.cpp:182): trace message: Releasing
static property map
How do I get past this?The workaround was, I installed the SQL Server Client tools and created a System DataSource and then had to create a user DataSource (it is a quirk in the installer I guess) to get past this point in the installation. Now I have an even bigger problem. Everything but the CMS installed and the installer hung at the "Configuring the CMS" part. The installation finished but when I tried to log into the Central managment console I got this error:
Error: Server GSD-RRPT-RDC:6400 not found or server may be down (FWM 01003) null
I looked at the forums for the cause of this error and came to the conclusion that BOEXI does not support an installation on SQL Server 2005 when using Integrated Authentication to the SQL Server. See the engineers here disabled SQL Authentication for the SQL Server and will not allow it.
Is this true? Or is there a workaround to install the CMS using Integrated Authentication in the DataSource ?
Thanks. -
Netweaver 7.0 SR3 install - x64 - Windows 2003(64-bit)/MS SQL 2005
I want to install Netweaver 7.0 SR3 on 64-Bit Windows 2003 Enterprise server with a SQL 2005 backend.
I downloaded packages 51033323_1, 51033323_2 & 51033323_3 and started the sapinst.exe utility in the 51033323_1\IM_WINDOWS_I386 directory.
I get the following error message: "You started an installation of software for platform I386, but SAPinst is running on platform AMD64."
I obviously have the 32-bit content but I require the 64bit install. How do I locate the 64-bit installation content.
Should I first install with the 32-bit install and then update the components to 64-bit? Or is there a standalone 64-bit installer and content?
ThanksUse below DVD's to install the Netweaver 7.0 SR3
51033493_1: - NW 7.0 SR3 Installation Export 1 of 2
51033493_2: - NW 7.0 SR3 Installation Export 2 of 2
51033508_15: - NW 7.0 SR3 UC-Kernel 7.00 Windows Server on x64 64bit
51033511_13: - BS2005 SR3 Installation Master Windows Server on x64 64bit
Thanks
Shambo -
Error export from my database sql 2005 with Windows 2003 abap+java
Hi all
I'm trying to create an Export from my database sql 2005 with Windows 2003, but SAPINST starts with an error. ABAP+JAVA stack
While running the export preparation, I am getting the following error;
INFO 2010-09-08 12:12:43
Output of C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath D:\usr\sap\BID\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jce.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jsse.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_smime.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_ssl.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/antlr.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/exception.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/jddi.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/logging.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/offlineconfiguration.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/opensqlsta.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SDMutil.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SLUtil.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\base.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\util.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\sqlserver.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\spy.jar -export -type=keydb "-expfile=C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/usages_data.xml" -log=UTL_load_usages.log -sid=BID -dsn=jdbc/pool/BID -ssprops=D:/usr/sap/BID/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/BID/SYS/global/security/data/SecStore.key is written to the logfile C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/UTL.java.log.
WARNING 2010-09-08 12:12:46
Execution of the command "C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath D:\usr\sap\BID\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jce.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jsse.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_smime.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_ssl.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/antlr.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/exception.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/jddi.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/logging.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/offlineconfiguration.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/opensqlsta.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SDMutil.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SLUtil.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\base.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\util.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\sqlserver.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\spy.jar -export -type=keydb "-expfile=C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/usages_data.xml" -log=UTL_load_usages.log -sid=BID -dsn=jdbc/pool/BID -ssprops=D:/usr/sap/BID/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/BID/SYS/global/security/data/SecStore.key" finished with return code 64. Output:
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_13-b06, mixed mode)
ERROR 2010-09-08 12:12:46
CJS-30071 Execution of UTL tool 'C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath D:\usr\sap\BID\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jce.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jsse.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_smime.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_ssl.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/antlr.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/exception.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/jddi.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/logging.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/offlineconfiguration.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/opensqlsta.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SDMutil.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SLUtil.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\base.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\util.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\sqlserver.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\spy.jar -export -type=keydb "-expfile=C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/usages_data.xml" -log=UTL_load_usages.log -sid=BID -dsn=jdbc/pool/BID -ssprops=D:/usr/sap/BID/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/BID/SYS/global/security/data/SecStore.key' aborts due to database connection error with return code 64.<br>DIAGNOSIS: The connection parameters are wrong or the database server is shutdown.<br> SOLUTION: Check 'UTL_load_usages.log' and 'C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/UTL.java.log' for more information.
ERROR 2010-09-08 12:12:46
FCO-00011 The step getUsageTypes with step key |NW_Prepare_Export|ind|ind|ind|ind|0|0|NW_Java_Prepare_Export_Dialog|ind|ind|ind|ind|5|0|getUsageTypes was executed with status ERROR .
Could anyone please help me out on this, if possible?
Thanks
JMHi,
please ensure that you use a SAP supported JDK as below:
716604 for the Sun JDK (Windows, Linux, Solaris)
709140 Recommended JDK and VM Settings for the WebAS630/640/7.0
And the re try the export pls.
Regards,
Snow -
Database connection to MS SQL 2005 (URGENT Help Needed)
Hi all,
Does anyone know how to connect my adobe form to MS SQL 2005?
I have this code:
try {
InitialContext initialContext = new InitialContext ();
DataSource dataSource = (DataSource) initialContext.lookup ("jdbc/MyAlias");
java.sql.Connection connection = dataSource.getConnection ();
} catch (SQLException e) {
// handle exception
} catch (NamingException e) {
// handle exception
Other than these, what else do i need to do inorder to get my database connection up?
And after my database connection is up, how do i test to check if my database connection is up or not?
How do i extract the information from the database and put them onto the textfields/dropdownlists on my form?
Thanks In AdvanceHi Mel,
After implementing the codes and modifying them, some of them are underlined, why is this so? =X
Or are u willing to exchange msn so i could send u the screenshot instead?
Thanks In Advance
(Sorry im not that good in this)
(I shall underline the areas which represents the red underline in my web dynpro)
//Code for database connection.
InitialContext ctx = new InitialContext();
DataSource ds = (DataSource)_ctx.lookup("jdbc/JXDataSource");_
Connection conn = ds.getConnection();
Statement st = null;
ResultSet rs = null;
IPrivateDetailed_Claims_FormView.IFillDataElement dataEle = null;
st = conn.createStatement();
// Execute the appropriate SQL query
rs = st.executeQuery("SELECT NAME WHERE VENDORCODE='9000116L' ");_
while (rs.next()) {
// Code that will populate your VN based on the data obtained in the ResultSet.
dataEle = wdContext.createFillDataElement();
dataEle.setName(_rs.getString(1)_);
// dataEle.setAge(rs.getInt(2));
// dataEle.setAddress(rs.getString(3));
//wdContext.nodeFillData.addElement(dataEle);
// Close the connections
rs.close();
st.close();
conn.close();
Edited by: JingXuan Lim on Jan 25, 2008 4:59 AM
Edited by: JingXuan Lim on Jan 25, 2008 5:00 AM -
Upgrade R/3 4.7 110 from SQL 2000 to ECC 6.0 /SQL 2005
Dear Experts,
We are currently running R/3 4.7 110 with kernel 640 32 Bit Non Unicode on Windows Server 2000/ MS SQL 2000 Platform. We are planning to Upgrade the same to ECC 6.0 on Windows 2003/ SQL 2005 on New x64 Bit Hardware.
I was earlier planning to Upgrade the OS/DB in first Phase moving the same R/3 4.7 on Windows 2003 Server /MS SQL 2005 and then Upgrade it to ECC 6.0 in second phase. But to my surprise when I checked PAM, I found that R/3 4.7 110 is not at all supported on SQL 2005 ( though R/3 4.6 C is)
Now shall I upgrade it to ECC6.0 First with Windows 2003/SQL 2000 ( Because ECC6.0 is supported with MS SQL 2000)and then move to MS SQL 2005 ?
Thanks
Jitendra TayalWe had the same issue.
So I checked with SAP.
This was their reply.
'SAP R/3 4.7 Ext 110 is supported on SQL 2005. Please refer to the following notes for further information:'
Note 905634 - Release planning for Microsoft SQL Server 2005
Note 799058 - Setting Up Microsoft SQL Server 2005
Note 899111 - Installing R3 4.7SR1 (47X110) on x64 Windows Platform
Note 151603 - Copying an SQL Server database
So feel free to go ahead.
Thanks.
Carl. -
SQL 2005 Patch installation fail
Hi all
I am having error on installing KB2716429... currently the SQL server is build no. 9.0.5057
here following is the error
11/30/2013 09:46:45.484 ================================================================================
11/30/2013 09:46:45.484 Hotfix package launched
11/30/2013 09:46:45.500 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:45.500 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:45.500 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:45.500 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:45.515 Local Computer:
11/30/2013 09:46:45.515 Target Details: SV53704
11/30/2013 09:46:45.515 commonfilesdir = C:\Program Files\Common Files
11/30/2013 09:46:45.515 lcidsupportdir = e:\6ce33de16cc8ba67b3e41388bb\1033
11/30/2013 09:46:45.515 programfilesdir = C:\Program Files
11/30/2013 09:46:45.515 programfilesdir_wow = C:\Program Files
11/30/2013 09:46:45.515 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:45.515 supportdirlocal = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:45.515 windir = C:\WINDOWS
11/30/2013 09:46:45.515 winsysdir = C:\WINDOWS\system32
11/30/2013 09:46:45.515 winsysdir_wow = C:\WINDOWS\SysWOW64
11/30/2013 09:46:45.515
11/30/2013 09:46:45.531 Enumerating applicable products for this patch
11/30/2013 09:46:45.531 Found SQL 2005 product definition
11/30/2013 09:46:45.531 Warning: Product HotFixSQL is missing LCID value
11/30/2013 09:46:46.953 Enumeration: Determining QFE level for product instance MSSQLSERVER
11/30/2013 09:46:46.969 Enumeration: Found following QFE level for product instance MSSQLSERVER: 5057
11/30/2013 09:46:46.969 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
11/30/2013 09:46:46.969 Enumeration: Found following GDR branch hotfix for product instance MSSQLSERVER: 5292
11/30/2013 09:46:46.969 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:46.984 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:46.984 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:46.984 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:46.984 Product discovery completed during the install process for MSSQLSERVER
11/30/2013 09:46:46.984 SP Level check completed during the install process for MSSQLSERVER
11/30/2013 09:46:46.984 Product language check completed during the install process for MSSQLSERVER
11/30/2013 09:46:46.984 Product version check completed during the install process for MSSQLSERVER
11/30/2013 09:46:46.984 Command-line instance name check completed during the install process
11/30/2013 09:46:46.984 Baseline build check completed during the installation process for MSSQLSERVER
11/30/2013 09:46:47.000 Baseline build check completed during the install process
11/30/2013 09:46:47.000 Found OLAP Server 2005 product definition
11/30/2013 09:46:47.000 Warning: Product HotFixAS is missing LCID value
11/30/2013 09:46:48.453 Enumeration: Determining QFE level for product instance MSSQLSERVER
11/30/2013 09:46:48.453 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\\Bin\msmdsrv.exe
11/30/2013 09:46:48.453 Enumeration: Found following QFE level for product instance MSSQLSERVER: 5057
11/30/2013 09:46:48.453 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
11/30/2013 09:46:48.453 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\\Bin\msmdsrv.exe
11/30/2013 09:46:48.453 Enumeration: No GDR branch Hotfix found for product instance MSSQLSERVER
11/30/2013 09:46:48.469 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:48.469 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:48.469 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:48.469 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:48.469 Product discovery completed during the install process for MSSQLSERVER
11/30/2013 09:46:48.469 SP Level check completed during the install process for MSSQLSERVER
11/30/2013 09:46:48.469 Product language check completed during the install process for MSSQLSERVER
11/30/2013 09:46:48.484 Product version check completed during the install process for MSSQLSERVER
11/30/2013 09:46:48.484 Command-line instance name check completed during the install process
11/30/2013 09:46:48.484 Baseline build check completed during the installation process for MSSQLSERVER
11/30/2013 09:46:48.484 Baseline build check completed during the install process
11/30/2013 09:46:48.484 Found Notification Services 2005 product definition
11/30/2013 09:46:48.484 Warning: Product HotFixNS is missing LCID value
11/30/2013 09:46:50.015 Enumeration: Determining QFE level for product instance
11/30/2013 09:46:50.047 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\\Bin\nsservice.exe
11/30/2013 09:46:50.062 Enumeration: Found following QFE level for product instance : 5057
11/30/2013 09:46:50.062 Enumeration: Determining GDR branching Hotfix for product instance
11/30/2013 09:46:50.062 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\\Bin\nsservice.exe
11/30/2013 09:46:50.062 Enumeration: Found following GDR branch hotfix for product instance : 5292
11/30/2013 09:46:50.062 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:50.062 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:50.062 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:50.078 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:50.078 Product discovery completed during the install process for NS
11/30/2013 09:46:50.078 SP Level check completed during the install process for NS
11/30/2013 09:46:50.078 Product language check completed during the install process for NS
11/30/2013 09:46:50.078 Product version check completed during the install process for NS
11/30/2013 09:46:50.078 Baseline build check completed during the installation process for NS
11/30/2013 09:46:50.078 Baseline build check completed during the install process
11/30/2013 09:46:50.078 Found Report Server 2005 product definition
11/30/2013 09:46:50.109 Warning: Product HotFixRS is missing LCID value
11/30/2013 09:46:51.687 Enumeration: Determining QFE level for product instance MSSQLSERVER
11/30/2013 09:46:51.703 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\\ReportServer\bin\ReportingServicesService.exe
11/30/2013 09:46:51.703 Enumeration: Found following QFE level for product instance MSSQLSERVER: 5057
11/30/2013 09:46:51.703 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
11/30/2013 09:46:51.703 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\\ReportServer\bin\ReportingServicesService.exe
11/30/2013 09:46:51.703 Enumeration: Found following GDR branch hotfix for product instance MSSQLSERVER: 5292
11/30/2013 09:46:51.703 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:51.703 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:51.703 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:51.703 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:51.703 Product discovery completed during the install process for MSSQLSERVER
11/30/2013 09:46:51.703 SP Level check completed during the install process for MSSQLSERVER
11/30/2013 09:46:51.703 Product language check completed during the install process for MSSQLSERVER
11/30/2013 09:46:51.703 Product version check completed during the install process for MSSQLSERVER
11/30/2013 09:46:51.719 Command-line instance name check completed during the install process
11/30/2013 09:46:51.750 Baseline build check completed during the installation process for MSSQLSERVER
11/30/2013 09:46:51.750 Baseline build check completed during the install process
11/30/2013 09:46:51.765 Found DTS 2005 product definition
11/30/2013 09:46:51.765 Warning: Product HotFixDTS is missing LCID value
11/30/2013 09:46:53.359 Enumeration: Determining QFE level for product instance
11/30/2013 09:46:53.375 Enumeration: Found following QFE level for product instance : 5057
11/30/2013 09:46:53.375 Enumeration: Determining GDR branching Hotfix for product instance
11/30/2013 09:46:53.375 Enumeration: Found following GDR branch hotfix for product instance : 5292
11/30/2013 09:46:53.375 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:53.375 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:53.375 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:53.375 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:53.375 Product discovery completed during the install process for Integration Services
11/30/2013 09:46:53.375 SP Level check completed during the install process for Integration Services
11/30/2013 09:46:53.375 Product language check completed during the install process for Integration Services
11/30/2013 09:46:53.375 Product version check completed during the install process for Integration Services
11/30/2013 09:46:53.375 Baseline build check completed during the installation process for Integration Services
11/30/2013 09:46:53.375 Baseline build check completed during the install process
11/30/2013 09:46:53.390 Found SQL 2005 Tools product definition
11/30/2013 09:46:53.390 Warning: Product HotFixTools is missing LCID value
11/30/2013 09:46:54.953 Enumeration: Determining GDR branching Hotfix for product instance
11/30/2013 09:46:54.969 Enumeration: Found following GDR branch hotfix for product instance : 5292
11/30/2013 09:46:54.969 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:54.969 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:54.969 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:54.969 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:54.969 Product discovery completed during the install process for SQL Tools
11/30/2013 09:46:54.969 SP Level check completed during the install process for SQL Tools
11/30/2013 09:46:54.969 Product language check completed during the install process for SQL Tools
11/30/2013 09:46:54.984 Product version check completed during the install process for SQL Tools
11/30/2013 09:46:54.984 Baseline build check completed during the installation process for SQL Tools
11/30/2013 09:46:54.984 Baseline build check completed during the install process
11/30/2013 09:46:55.031 Product Enumeration Results:
11/30/2013 09:46:55.031 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixSQL.inf
11/30/2013 09:46:55.031 arpfolder = SQL9_KB2716429_ENU
11/30/2013 09:46:55.031 associatedhotfixbuild = 5320
11/30/2013 09:46:55.031 baselinebuild = 5000
11/30/2013 09:46:55.031 baselinebuildmax = 5069
11/30/2013 09:46:55.031 build = 5069
11/30/2013 09:46:55.031 description = SQL Server Database Services 2005
11/30/2013 09:46:55.031 details = Patch for SQL Server Database Services 2005
11/30/2013 09:46:55.031 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.031 kbarticle = KB2716429
11/30/2013 09:46:55.031 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.031 legalproductname = SQL Server Database Services 2005
11/30/2013 09:46:55.031 machinetype = x86
11/30/2013 09:46:55.031 package = HotFixSQL
11/30/2013 09:46:55.031 packagetype = GDR
11/30/2013 09:46:55.031 productname = SQL9
11/30/2013 09:46:55.047 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.047 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.047 splevel = 4
11/30/2013 09:46:55.047 sqlutility = sqlcmd.exe
11/30/2013 09:46:55.047 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.047 version = 9
11/30/2013 09:46:55.047
11/30/2013 09:46:55.047 File Group Details: MSP
11/30/2013 09:46:55.047 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.047 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.047 File Details: sqlrun_sql.msp
11/30/2013 09:46:55.047
11/30/2013 09:46:55.047 Instance Details: MSSQLSERVER
11/30/2013 09:46:55.047 agentservicename = SQLSERVERAGENT
11/30/2013 09:46:55.047 associatedhotfixbuild = 5292
11/30/2013 09:46:55.047 clustername =
11/30/2013 09:46:55.047 default = TRUE
11/30/2013 09:46:55.047 ftsservicename = MSFTESQL
11/30/2013 09:46:55.047 fullversion = 2005.090.5057.00
11/30/2013 09:46:55.047 hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.1
11/30/2013 09:46:55.047 id = MSSQL.1
11/30/2013 09:46:55.062 installsqldatadir = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
11/30/2013 09:46:55.062 installsqldir = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
11/30/2013 09:46:55.062 lcid = 1033
11/30/2013 09:46:55.062 name = MSSQLSERVER
11/30/2013 09:46:55.062 productcode = {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
11/30/2013 09:46:55.062 qfelevel = 5057
11/30/2013 09:46:55.062 servicename = MSSQLServer
11/30/2013 09:46:55.062 sku = STANDARD
11/30/2013 09:46:55.062 sp = 4
11/30/2013 09:46:55.094 type = SQL Server Standalone Product
11/30/2013 09:46:55.094 vermajbld = 5000
11/30/2013 09:46:55.094 version = 9
11/30/2013 09:46:55.109
11/30/2013 09:46:55.125 Product Enumeration Results:
11/30/2013 09:46:55.140 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixAS.inf
11/30/2013 09:46:55.140 arpfolder = OLAP9_KB2716429_ENU
11/30/2013 09:46:55.140 associatedhotfixbuild = 5320
11/30/2013 09:46:55.140 baselinebuild = 5000
11/30/2013 09:46:55.140 baselinebuildmax = 5069
11/30/2013 09:46:55.140 build = 5069
11/30/2013 09:46:55.140 description = SQL Server Analysis Services 2005
11/30/2013 09:46:55.140 details = Patch for Analysis Services 2005
11/30/2013 09:46:55.140 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.140 kbarticle = KB2716429
11/30/2013 09:46:55.140 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.140 legalproductname = SQL Server Analysis Services 2005
11/30/2013 09:46:55.156 machinetype = x86
11/30/2013 09:46:55.156 package = HotFixAS
11/30/2013 09:46:55.156 packagetype = GDR
11/30/2013 09:46:55.156 productname = OLAP9
11/30/2013 09:46:55.156 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.156 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.156 splevel = 4
11/30/2013 09:46:55.156 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.156 validateauthentication = true
11/30/2013 09:46:55.156 version = 9
11/30/2013 09:46:55.156
11/30/2013 09:46:55.156 File Group Details: MSP
11/30/2013 09:46:55.156 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.156 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.172 File Details: sqlrun_as.msp
11/30/2013 09:46:55.172
11/30/2013 09:46:55.172 Instance Details: MSSQLSERVER
11/30/2013 09:46:55.172 associatedhotfixbuild = 1520
11/30/2013 09:46:55.172 clustername =
11/30/2013 09:46:55.187 default = TRUE
11/30/2013 09:46:55.203 fullversion = 2005.090.5057.00
11/30/2013 09:46:55.219 hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.2
11/30/2013 09:46:55.219 id = MSSQL.2
11/30/2013 09:46:55.219 installsqldatadir = C:\Program Files\Microsoft SQL Server\
11/30/2013 09:46:55.234 installsqldir = C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\
11/30/2013 09:46:55.250 lcid = 1033
11/30/2013 09:46:55.265 name = MSSQLSERVER
11/30/2013 09:46:55.297 olapservicename = MSSQLServerOLAPService
11/30/2013 09:46:55.297 productcode = {8ABF8FEB-ABB0-40DC-9945-85AF36EF30A9}
11/30/2013 09:46:55.297 qfelevel = 5057
11/30/2013 09:46:55.297 servicename = MSSQLServerOLAPService
11/30/2013 09:46:55.297 sku = STANDARD
11/30/2013 09:46:55.297 sp = 4
11/30/2013 09:46:55.297 type = Olap Standalone Product
11/30/2013 09:46:55.297 vermajbld = 5000
11/30/2013 09:46:55.297 version = 9
11/30/2013 09:46:55.297
11/30/2013 09:46:55.297 Product Enumeration Results:
11/30/2013 09:46:55.297 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixNS.inf
11/30/2013 09:46:55.297 arpfolder = NS9_KB2716429_ENU
11/30/2013 09:46:55.297 associatedhotfixbuild = 5320
11/30/2013 09:46:55.297 baselinebuild = 5000
11/30/2013 09:46:55.297 baselinebuildmax = 5069
11/30/2013 09:46:55.297 build = 5069
11/30/2013 09:46:55.297 description = SQL Server Notification Services 2005
11/30/2013 09:46:55.297 details = Patch for SQL Server Notification Services 2005
11/30/2013 09:46:55.297 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.312 kbarticle = KB2716429
11/30/2013 09:46:55.312 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.312 legalproductname = SQL Server Notification Services 2005 instances
11/30/2013 09:46:55.312 machinetype = x86
11/30/2013 09:46:55.312 package = HotFixNS
11/30/2013 09:46:55.312 packagetype = GDR
11/30/2013 09:46:55.312 productname = NS9
11/30/2013 09:46:55.312 recommendinstall = 1
11/30/2013 09:46:55.312 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.312 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.312 splevel = 4
11/30/2013 09:46:55.312 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.312 validateauthentication = true
11/30/2013 09:46:55.312 version = 9
11/30/2013 09:46:55.312
11/30/2013 09:46:55.312 File Group Details: MSP
11/30/2013 09:46:55.312 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.312 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.312 File Details: sqlrun_ns.msp
11/30/2013 09:46:55.312
11/30/2013 09:46:55.312 Instance Details: NS
11/30/2013 09:46:55.312 associatedhotfixbuild = 5292
11/30/2013 09:46:55.328 clustername =
11/30/2013 09:46:55.328 fullversion = 9.00.5057.00
11/30/2013 09:46:55.328 hiveregpath = Software\Microsoft\Microsoft SQL Server\90\NS
11/30/2013 09:46:55.328 id =
11/30/2013 09:46:55.328 installsqldatadir =
11/30/2013 09:46:55.328 installsqldir = C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\
11/30/2013 09:46:55.328 lcid = 1033
11/30/2013 09:46:55.328 name =
11/30/2013 09:46:55.375 productcode = {37E9AD9F-3217-4229-B5A5-7A0C82364C6C}
11/30/2013 09:46:55.390 qfelevel = 5057
11/30/2013 09:46:55.406 sku = STANDARD
11/30/2013 09:46:55.406 sp = 4
11/30/2013 09:46:55.406 type = Tools Only
11/30/2013 09:46:55.406 vermajbld = 5000
11/30/2013 09:46:55.422 version = 9
11/30/2013 09:46:55.422
11/30/2013 09:46:55.422 Product Enumeration Results:
11/30/2013 09:46:55.422 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixRS.inf
11/30/2013 09:46:55.422 arpfolder = RS9_KB2716429_ENU
11/30/2013 09:46:55.422 associatedhotfixbuild = 5320
11/30/2013 09:46:55.422 baselinebuild = 5000
11/30/2013 09:46:55.422 baselinebuildmax = 5069
11/30/2013 09:46:55.422 build = 5069
11/30/2013 09:46:55.453 description = SQL Server Reporting Services 2005
11/30/2013 09:46:55.453 details = Patch for SQL Server Reporting Services 2005
11/30/2013 09:46:55.453 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.453 kbarticle = KB2716429
11/30/2013 09:46:55.453 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.453 legalproductname = SQL Server Reporting Services 2005
11/30/2013 09:46:55.453 machinetype = x86
11/30/2013 09:46:55.453 package = HotFixRS
11/30/2013 09:46:55.453 packagetype = GDR
11/30/2013 09:46:55.453 productname = RS9
11/30/2013 09:46:55.469 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.469 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.469 splevel = 4
11/30/2013 09:46:55.469 sqlutility = sqlcmd.exe
11/30/2013 09:46:55.469 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.469 validateauthentication = true
11/30/2013 09:46:55.469 version = 9
11/30/2013 09:46:55.469
11/30/2013 09:46:55.469 File Group Details: MSP
11/30/2013 09:46:55.469 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.469 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.469 File Details: sqlrun_rs.msp
11/30/2013 09:46:55.469
11/30/2013 09:46:55.469 Instance Details: MSSQLSERVER
11/30/2013 09:46:55.469 associatedhotfixbuild = 5292
11/30/2013 09:46:55.469 clustername =
11/30/2013 09:46:55.469 default = TRUE
11/30/2013 09:46:55.469 fullversion = 9.00.5057.00
11/30/2013 09:46:55.469 hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.3
11/30/2013 09:46:55.469 id = MSSQL.3
11/30/2013 09:46:55.469 installsqldatadir =
11/30/2013 09:46:55.469 installsqldir = C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\
11/30/2013 09:46:55.484 lcid = 1033
11/30/2013 09:46:55.484 name = MSSQLSERVER
11/30/2013 09:46:55.484 productcode = {E930E839-998E-42F9-97E2-71FC960DB1B7}
11/30/2013 09:46:55.484 qfelevel = 5057
11/30/2013 09:46:55.484 rsservicename = ReportServer
11/30/2013 09:46:55.484 servicename =
11/30/2013 09:46:55.484 sku = STANDARD
11/30/2013 09:46:55.484 sp = 4
11/30/2013 09:46:55.484 type = Report Server Standalone Product
11/30/2013 09:46:55.484 vermajbld = 5000
11/30/2013 09:46:55.484 version = 9
11/30/2013 09:46:55.484
11/30/2013 09:46:55.484 Product Enumeration Results:
11/30/2013 09:46:55.484 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixDTS.inf
11/30/2013 09:46:55.500 arpfolder = DTS9_KB2716429_ENU
11/30/2013 09:46:55.625 associatedhotfixbuild = 5320
11/30/2013 09:46:55.625 baselinebuild = 5000
11/30/2013 09:46:55.625 baselinebuildmax = 5069
11/30/2013 09:46:55.625 build = 5069
11/30/2013 09:46:55.625 description = SQL Server Integration Services 2005
11/30/2013 09:46:55.625 details = Patch for SQL Server Integration Services 2005
11/30/2013 09:46:55.625 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.625 kbarticle = KB2716429
11/30/2013 09:46:55.625 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.625 legalproductname = SQL Server Integration Services 2005
11/30/2013 09:46:55.625 machinetype = x86
11/30/2013 09:46:55.640 package = HotFixDTS
11/30/2013 09:46:55.640 packagetype = GDR
11/30/2013 09:46:55.640 productname = DTS9
11/30/2013 09:46:55.640 recommendinstall = 1
11/30/2013 09:46:55.640 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.640 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.640 splevel = 4
11/30/2013 09:46:55.640 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.640 version = 9
11/30/2013 09:46:55.640
11/30/2013 09:46:55.640 File Group Details: MSP
11/30/2013 09:46:55.640 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.640 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.640 File Details: sqlrun_dts.msp
11/30/2013 09:46:55.640
11/30/2013 09:46:55.640 Instance Details: Integration Services
11/30/2013 09:46:55.640 associatedhotfixbuild = 5292
11/30/2013 09:46:55.640 clustername =
11/30/2013 09:46:55.640 dtsservicename = MsDtsServer
11/30/2013 09:46:55.640 fullversion = 9.00.5057.00
11/30/2013 09:46:55.656 hiveregpath = Software\Microsoft\Microsoft SQL Server\90\DTS
11/30/2013 09:46:55.656 id =
11/30/2013 09:46:55.656 installsqldatadir =
11/30/2013 09:46:55.656 installsqldir = C:\Program Files\Microsoft SQL Server\90\DTS\
11/30/2013 09:46:55.656 lcid = 1033
11/30/2013 09:46:55.656 name =
11/30/2013 09:46:55.656 productcode = {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
11/30/2013 09:46:55.656 qfelevel = 5057
11/30/2013 09:46:55.656 servicename = MsDtsServer
11/30/2013 09:46:55.656 sku = STANDARD
11/30/2013 09:46:55.656 sp = 4
11/30/2013 09:46:55.656 type = Tools Only
11/30/2013 09:46:55.656 vermajbld = 5000
11/30/2013 09:46:55.656 version = 9
11/30/2013 09:46:55.656
11/30/2013 09:46:55.656 Product Enumeration Results:
11/30/2013 09:46:55.672 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixTools.inf
11/30/2013 09:46:55.672 arpfolder = SQLTools9_KB2716429_ENU
11/30/2013 09:46:55.672 associatedhotfixbuild = 5320
11/30/2013 09:46:55.672 baselinebuild = 5000
11/30/2013 09:46:55.672 baselinebuildmax = 5069
11/30/2013 09:46:55.672 build = 5069
11/30/2013 09:46:55.672 description = SQL Server Tools and Workstation Components 2005
11/30/2013 09:46:55.672 details = Patch for SQL Server Tools and Workstation Components 2005
11/30/2013 09:46:55.672 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.672 kbarticle = KB2716429
11/30/2013 09:46:55.672 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.672 legalproductname = SQL Server Tools and Workstation Components 2005
11/30/2013 09:46:55.672 machinetype = x86
11/30/2013 09:46:55.672 package = HotFixTools
11/30/2013 09:46:55.672 packagetype = GDR
11/30/2013 09:46:55.672 productname = SQLTools9
11/30/2013 09:46:55.672 recommendinstall = 1
11/30/2013 09:46:55.672 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.672 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.672 splevel = 4
11/30/2013 09:46:55.672 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.687 version = 9
11/30/2013 09:46:55.687
11/30/2013 09:46:55.687 File Group Details: MSP
11/30/2013 09:46:55.687 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.687 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.687 File Details: sqlrun_tools.msp
11/30/2013 09:46:55.687
11/30/2013 09:46:55.687 Instance Details: SQL Tools
11/30/2013 09:46:55.687 associatedhotfixbuild = 5292
11/30/2013 09:46:55.687 clustername =
11/30/2013 09:46:55.687 fullversion = 9.4.5057
11/30/2013 09:46:55.687 hiveregpath = Software\Microsoft\Microsoft SQL Server\90\Tools
11/30/2013 09:46:55.687 id =
11/30/2013 09:46:55.687 installsqldatadir =
11/30/2013 09:46:55.687 installsqldir = C:\Program Files\Microsoft SQL Server\90\Tools\
11/30/2013 09:46:55.687 lcid = 1033
11/30/2013 09:46:55.687 name =
11/30/2013 09:46:55.687 productcode = {1DD463C0-A50A-4394-B7E4-5895C02F9E0D}
11/30/2013 09:46:55.687 qfelevel = 5057
11/30/2013 09:46:55.687 sku = STANDARD
11/30/2013 09:46:55.687 sp = 4
11/30/2013 09:46:55.687 type = Tools Only
11/30/2013 09:46:55.703 vermajbld = 5000
11/30/2013 09:46:55.703 version = 9
11/30/2013 09:46:55.703
11/30/2013 09:47:00.781 Registry: Opened registry key "System\CurrentControlSet\Control\Session Manager"
11/30/2013 09:47:00.781 Registry: Cannot read registry key value "PendingFileRenameOperations", error 0
11/30/2013 09:47:00.812 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.719 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.734 Locked file: Checking for locked files
11/30/2013 09:47:04.328 Attempting to pause the 32 bit ngen queue
11/30/2013 09:47:04.968 Installing product: SQL9
11/30/2013 09:47:05.781 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:05.781 Installing instance: MSSQLSERVER
11/30/2013 09:47:05.812 Installing target: SV53704
11/30/2013 09:47:05.828 Installing file: sqlrun_sql.msp
11/30/2013 09:47:05.828 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2716429_sqlrun_sql.msp.log
11/30/2013 09:47:05.828 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:05.828 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:06.203 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:06.203 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:06.203 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:06.218 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixSQL\Files\sqlrun_sql.msp
11/30/2013 09:47:06.218 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:06.218 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:06.640 Watson: Param1 = Unknown
11/30/2013 09:47:06.640 Watson: Param2 = 0x66e
11/30/2013 09:47:06.640 Watson: Param3 = Unknown
11/30/2013 09:47:06.640 Watson: Param4 = 0x66e
11/30/2013 09:47:06.656 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:06.656 Watson: Param6 = Unknown
11/30/2013 09:47:06.656 Watson: Param7 = SQL9
11/30/2013 09:47:06.656 Watson: Param8 = @
11/30/2013 09:47:06.656 Watson: Param9 = x86
11/30/2013 09:47:06.656 Watson: Param10 = 5069
11/30/2013 09:47:06.656 Installed product: SQL9
11/30/2013 09:47:06.656 Installing product: OLAP9
11/30/2013 09:47:07.468 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:07.484 Installing instance: MSSQLSERVER
11/30/2013 09:47:07.484 Installing target: SV53704
11/30/2013 09:47:07.500 Installing file: sqlrun_as.msp
11/30/2013 09:47:07.500 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\OLAP9_Hotfix_KB2716429_sqlrun_as.msp.log
11/30/2013 09:47:07.515 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:07.515 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:07.640 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:07.640 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:07.640 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:07.656 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixAS\Files\sqlrun_as.msp
11/30/2013 09:47:07.656 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:07.656 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:08.078 Watson: Param1 = Unknown
11/30/2013 09:47:08.078 Watson: Param2 = 0x66e
11/30/2013 09:47:08.078 Watson: Param3 = Unknown
11/30/2013 09:47:08.078 Watson: Param4 = 0x66e
11/30/2013 09:47:08.078 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:08.078 Watson: Param6 = Unknown
11/30/2013 09:47:08.078 Watson: Param7 = OLAP9
11/30/2013 09:47:08.078 Watson: Param8 = @
11/30/2013 09:47:08.078 Watson: Param9 = x86
11/30/2013 09:47:08.078 Watson: Param10 = 5069
11/30/2013 09:47:08.078 Installed product: OLAP9
11/30/2013 09:47:08.078 Installing product: RS9
11/30/2013 09:47:08.875 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:08.875 Installing instance: MSSQLSERVER
11/30/2013 09:47:08.890 Installing target: SV53704
11/30/2013 09:47:08.890 Installing file: sqlrun_rs.msp
11/30/2013 09:47:08.890 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\RS9_Hotfix_KB2716429_sqlrun_rs.msp.log
11/30/2013 09:47:08.890 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:08.890 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:09.015 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:09.015 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:09.015 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:09.031 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixRS\Files\sqlrun_rs.msp
11/30/2013 09:47:09.047 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:09.047 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:09.593 Watson: Param1 = Unknown
11/30/2013 09:47:09.593 Watson: Param2 = 0x66e
11/30/2013 09:47:09.593 Watson: Param3 = Unknown
11/30/2013 09:47:09.609 Watson: Param4 = 0x66e
11/30/2013 09:47:09.609 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:09.609 Watson: Param6 = Unknown
11/30/2013 09:47:09.609 Watson: Param7 = RS9
11/30/2013 09:47:09.609 Watson: Param8 = @
11/30/2013 09:47:09.609 Watson: Param9 = x86
11/30/2013 09:47:09.609 Watson: Param10 = 5069
11/30/2013 09:47:09.625 Installed product: RS9
11/30/2013 09:47:09.625 Installing product: NS9
11/30/2013 09:47:10.406 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:10.406 Installing instance: NS
11/30/2013 09:47:10.422 Installing target: SV53704
11/30/2013 09:47:10.422 Installing file: sqlrun_ns.msp
11/30/2013 09:47:10.422 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\NS9_Hotfix_KB2716429_sqlrun_ns.msp.log
11/30/2013 09:47:10.422 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:10.422 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:10.531 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:10.531 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:10.531 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:10.547 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixNS\Files\sqlrun_ns.msp
11/30/2013 09:47:10.547 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:10.547 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:10.890 Watson: Param1 = Unknown
11/30/2013 09:47:10.890 Watson: Param2 = 0x66e
11/30/2013 09:47:10.890 Watson: Param3 = Unknown
11/30/2013 09:47:10.890 Watson: Param4 = 0x66e
11/30/2013 09:47:10.890 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:10.890 Watson: Param6 = Unknown
11/30/2013 09:47:10.890 Watson: Param7 = NS9
11/30/2013 09:47:10.890 Watson: Param8 = @
11/30/2013 09:47:10.890 Watson: Param9 = x86
11/30/2013 09:47:10.890 Watson: Param10 = 5069
11/30/2013 09:47:10.890 Installed product: NS9
11/30/2013 09:47:10.890 Installing product: DTS9
11/30/2013 09:47:11.703 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:11.703 Installing instance: Integration Services
11/30/2013 09:47:11.703 Installing target: SV53704
11/30/2013 09:47:11.703 Installing file: sqlrun_dts.msp
11/30/2013 09:47:11.703 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log
11/30/2013 09:47:11.703 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:11.718 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:11.890 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:11.890 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:11.906 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:11.906 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixDTS\Files\sqlrun_dts.msp
11/30/2013 09:47:11.922 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:11.922 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:12.328 Watson: Param1 = Unknown
11/30/2013 09:47:12.328 Watson: Param2 = 0x66e
11/30/2013 09:47:12.328 Watson: Param3 = Unknown
11/30/2013 09:47:12.328 Watson: Param4 = 0x66e
11/30/2013 09:47:12.328 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:12.328 Watson: Param6 = Unknown
11/30/2013 09:47:12.328 Watson: Param7 = DTS9
11/30/2013 09:47:12.328 Watson: Param8 = @
11/30/2013 09:47:12.328 Watson: Param9 = x86
11/30/2013 09:47:12.328 Watson: Param10 = 5069
11/30/2013 09:47:12.343 Installed product: DTS9
11/30/2013 09:47:12.343 Installing product: SQLTools9
11/30/2013 09:47:13.125 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:13.140 Installing instance: SQL Tools
11/30/2013 09:47:13.140 Installing target: SV53704
11/30/2013 09:47:13.156 Installing file: sqlrun_tools.msp
11/30/2013 09:47:13.172 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB2716429_sqlrun_tools.msp.log
11/30/2013 09:47:13.172 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:13.172 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:13.484 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:13.484 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:13.484 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:13.500 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixTools\Files\sqlrun_tools.msp
11/30/2013 09:47:13.500 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:13.500 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:13.828 Watson: Param1 = Unknown
11/30/2013 09:47:13.828 Watson: Param2 = 0x66e
11/30/2013 09:47:13.843 Watson: Param3 = Unknown
11/30/2013 09:47:13.843 Watson: Param4 = 0x66e
11/30/2013 09:47:13.843 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:13.843 Watson: Param6 = Unknown
11/30/2013 09:47:13.843 Watson: Param7 = SQLTools9
11/30/2013 09:47:13.843 Watson: Param8 = @
11/30/2013 09:47:13.843 Watson: Param9 = x86
11/30/2013 09:47:13.843 Watson: Param10 = 5069
11/30/2013 09:47:13.843 Installed product: SQLTools9
11/30/2013 09:47:13.843 Hotfix package completed
11/30/2013 09:47:13.859 Attempting to continue the 32 bit ngen queueHi ~ any idea on this case ? here is the one MSP installation log:
=== Verbose logging started: 11/30/2013 21:28:15 Build type: SHIP UNICODE 4.05.6001.00 Calling process: e:\de60d5388bc787220900e629b152c9\hotfix.exe ===
MSI (c) (D4:28) [21:28:15:681]: Resetting cached policy values
MSI (c) (D4:28) [21:28:15:681]: Machine policy value 'Debug' is 0
MSI (c) (D4:28) [21:28:15:681]: ******* RunEngine:
******* Product: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
******* Action:
******* CommandLine: **********
MSI (c) (D4:28) [21:28:15:681]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (D4:28) [21:28:15:681]: Grabbed execution mutex.
MSI (c) (D4:28) [21:28:15:697]: Cloaking enabled.
MSI (c) (D4:28) [21:28:15:697]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (D4:28) [21:28:15:697]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (A8:C0) [21:28:15:697]: Running installation inside multi-package transaction {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
MSI (s) (A8:C0) [21:28:15:697]: Grabbed execution mutex.
MSI (s) (A8:04) [21:28:15:697]: Resetting cached policy values
MSI (s) (A8:04) [21:28:15:697]: Machine policy value 'Debug' is 0
MSI (s) (A8:04) [21:28:15:697]: ******* RunEngine:
******* Product: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
******* Action:
******* CommandLine: **********
MSI (s) (A8:04) [21:28:15:697]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (A8:04) [21:28:15:931]: End dialog not enabled
MSI (s) (A8:04) [21:28:15:931]: Original package ==> C:\WINDOWS\Installer\181c1.msi
MSI (s) (A8:04) [21:28:15:931]: Package we're running from ==> C:\WINDOWS\Installer\181c1.msi
MSI (s) (A8:04) [21:28:15:994]: APPCOMPAT: looking for appcompat database entry with ProductCode '{EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}'.
MSI (s) (A8:04) [21:28:15:994]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (A8:04) [21:28:15:994]: Opening existing patch 'C:\WINDOWS\Installer\e9ff36e.msp'.
MSI (s) (A8:04) [21:28:16:010]: Opening existing patch 'C:\WINDOWS\Installer\239697ae.msp'.
MSI (s) (A8:04) [21:28:16:056]: File will have security applied from OpCode.
MSI (s) (A8:04) [21:28:16:056]: Original patch ==> e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp
MSI (s) (A8:04) [21:28:16:056]: Patch we're running from ==> C:\WINDOWS\Installer\1f80a9f.msp
MSI (s) (A8:04) [21:28:16:072]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp' against software restriction policy
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: SOFTWARE RESTRICTION POLICY: e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp is not digitally signed
MSI (s) (A8:04) [21:28:16:072]: SOFTWARE RESTRICTION POLICY: e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp is permitted to run at the 'unrestricted' authorization level.
MSI (s) (A8:04) [21:28:16:072]: SequencePatches starts. Product code: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}, Product version: 9.00.1399.06, Upgrade code: {2B33A057-4470-45CD-8E63-863CB78FC626}, Product language 1033
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: PATCH SEQUENCER: verifying the applicability of QFE patch e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp against product code: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}, product version: 9.00.1399.06, product language
1033 and upgrade code: {2B33A057-4470-45CD-8E63-863CB78FC626}
MSI (s) (A8:04) [21:28:16:072]: PATCH SEQUENCER: QFE patch e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp is not applicable.
MSI (s) (A8:04) [21:28:16:072]: SequencePatches returns success.
MSI (s) (A8:04) [21:28:16:072]: Final Patch Application Order:
MSI (s) (A8:04) [21:28:16:072]: Other Patches:
MSI (s) (A8:04) [21:28:16:072]: Unknown\Absent: {4C3BC5C8-67A5-40F1-85B7-D9341A5F7B6C} - e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp
MSI (s) (A8:04) [21:28:16:072]: Superseded: {5E9ADA2D-3132-42CF-8628-D2ADA0F335EE} -
MSI (s) (A8:04) [21:28:16:072]: Superseded: {32BCE9F2-8686-487A-80A9-A401C0F7DCBD} -
MSI (s) (A8:04) [21:28:16:072]: Unknown\Absent: {D23D25E7-0AB4-41EE-81B5-F0CF34D1BA2B} -
MSI (s) (A8:04) [21:28:16:072]: Unknown\Absent: {CF321155-04AA-4CF8-BB9A-DA3144835E3E} -
MSI (s) (A8:04) [21:28:16:072]: Machine policy value 'DisablePatch' is 0
MSI (s) (A8:04) [21:28:16:072]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (A8:04) [21:28:16:072]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (A8:04) [21:28:16:072]: Disallowing uninstallation of patch {CF321155-04AA-4CF8-BB9A-DA3144835E3E} because the patch is marked as not uninstallable
MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services - Update 'Service Pack 4 for SQL Server Integration Services 2005 ENU (KB2463332)' could not be removed. Error code 1646. Additional information is available in the log
file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log.
MSI (s) (A8:04) [21:28:16:072]: Windows Installer removed an update. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Update Name: Service Pack 4 for SQL Server Integration Services 2005 ENU
(KB2463332). Removal success or error status: 0.
MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services - Update '{4C3BC5C8-67A5-40F1-85B7-D9341A5F7B6C}' could not be installed. Error code 1646. Additional information is available in the log file C:\Program Files\Microsoft
SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log.
MSI (s) (A8:04) [21:28:16:072]: Windows Installer installed an update. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Update Name: {4C3BC5C8-67A5-40F1-85B7-D9341A5F7B6C}. Installation success
or error status: 1646.
MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services - Update 'GDR 5057 for SQL Server Integration Services 2005 ENU (KB2494120)' could not be removed. Error code 1646. Additional information is available in the log file C:\Program
Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log.
MSI (s) (A8:04) [21:28:16:072]: Windows Installer removed an update. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Update Name: GDR 5057 for SQL Server Integration Services 2005 ENU (KB2494120).
Removal success or error status: 1646.
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 1708
MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services -- Installation failed.
MSI (s) (A8:04) [21:28:16:072]: Windows Installer installed the product. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Installation success or error status: 1646.
MSI (s) (A8:04) [21:28:16:088]: Attempting to delete file C:\WINDOWS\Installer\1f80a9f.msp
MSI (s) (A8:04) [21:28:16:088]: MainEngineThread is returning 1646
MSI (s) (A8:C0) [21:28:16:088]: No System Restore sequence number for this installation.
Uninstallation of the patch package is not supported.
C:\WINDOWS\Installer\181c1.msi
MSI (s) (A8:C0) [21:28:16:088]: User policy value 'DisableRollback' is 0
MSI (s) (A8:C0) [21:28:16:088]: Machine policy value 'DisableRollback' is 0
MSI (s) (A8:C0) [21:28:16:088]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (A8:C0) [21:28:16:088]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (A8:C0) [21:28:16:088]: Restoring environment variables
MSI (c) (D4:28) [21:28:16:088]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (D4:28) [21:28:16:088]: MainEngineThread is returning 1646
=== Verbose logging stopped: 11/30/2013 21:28:16 === -
Issue in Java system installation: MS SQL 2005
Dear All,
I am installing a SAP Netweaver '04 SR1 , Java system with data base MS SQL 2005.
I am facing the issue hereby i will attach the jload.java.log file.
Can any one help me out in fixing it?
java version "1.4.2_16"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_16-b05)
Java HotSpot(TM) Client VM (build 1.4.2_16-b05, mixed mode)
Mar 16, 2009 11:09:42 PM com.sap.inst.jload.Jload main
INFO: Jload -sec KS7,jdbc/pool/KS7,D:\usr\sap\KS7\SYS\global/security/data/SecStore.properties,D:\usr\sap\KS7\SYS\global/security/data/SecStore.key -dataDir D:/Netweaver/netweaver1\J2EE_OSINDEP\J2EE-ENG/JDMP -job C:\Program Files\sapinst_instdir\NW04SR1\WEBAS_JAVA\ONE_HOST/IMPORT.XML -log C:\Program Files\sapinst_instdir\NW04SR1\WEBAS_JAVA\ONE_HOST/jload.log
Mar 16, 2009 11:09:43 PM com.sap.inst.jload.Jload main
SEVERE: couldn't connect to DB
java.sql.SQLException: [SAP NetWeaver][SQLServer JDBC Driver]Unable to connect. Invalid URL.
Thanks
RajHi
Yes, everything is checked it. Error appears in the phase of Load Java Database content (18 of 25).
ERROR 2009-03-17 03:35:49
CJS-20065 Execution of JLoad tool 'C:\j2sdk1.4.2_16/bin/java.exe '-classpath' './sharedlib/antlr.jar;./sharedlib/exception.jar;./sharedlib/jddi.jar;./sharedlib/jload.jar;./sharedlib/logging.jar;./sharedlib/offlineconfiguration.jar;./sharedlib/opensqlsta.jar;./sharedlib/tc_sec_secstorefs.jar;D:\usr\sap/KS7/JC00/j2ee\jdbc\base.jar;D:\usr\sap/KS7/JC00/j2ee\jdbc\util.jar;D:\usr\sap/KS7/JC00/j2ee\jdbc\sqlserver.jar;D:\usr\sap/KS7/JC00/j2ee\jdbc\spy.jar;D:/usr/sap/KS7/SYS/global/security/lib/tools/iaik_jce_export.jar;D:/usr/sap/KS7/SYS/global/security/lib/tools/iaik_jsse.jar;D:/usr/sap/KS7/SYS/global/security/lib/tools/iaik_smime.jar;D:/usr/sap/KS7/SYS/global/security/lib/tools/iaik_ssl.jar;D:/usr/sap/KS7/SYS/global/security/lib/tools/w3c_http.jar' '-showversion' '-Xmx512m' 'com.sap.inst.jload.Jload' '-sec' 'KS7,jdbc/pool/KS7,D:\usr\sap\KS7\SYS\global/security/data/SecStore.properties,D:\usr\sap\KS7\SYS\global/security/data/SecStore.key' '-dataDir' 'D:/Netweaver/netweaver1\J2EE_OSINDEP\J2EE-ENG/JDMP' '-job' 'C:\Program Files\sapinst_instdir\NW04SR1\WEBAS_JAVA\ONE_HOST/IMPORT.XML' '-log' 'C:\Program Files\sapinst_instdir\NW04SR1\WEBAS_JAVA\ONE_HOST/jload.log'' aborts with returncode 1. Check 'C:\Program Files\sapinst_instdir\NW04SR1\WEBAS_JAVA\ONE_HOST/jload.log' and 'C:\Program Files\sapinst_instdir\NW04SR1\WEBAS_JAVA\ONE_HOST/jload.java.log' for more information.
Thanks
Raj -
Can SQL 2000 and SQL 2005 drivers co-exist in PI?
Hi,
Currently in our PI environment, we have JDBC Adapter connections to SQL 2000 database servers for which the Driver has already been installed.
For connecting to new SQL 2005 database servers, I understand that we have to install the SQL 2005 drivers. I also came to know that SQL 2005 Driver is backward compatible and supports JDBC connection to SQL 2000 server.
But the question I have is whether both the SQL 2000 and SQL 2005 drivers can be installed together in a way that connection to SQL 2000 use the 2000 driver and the connection to 2005 uses 2005 Driver.
(They have different connection strings)
Many thanks in advance,
Regards,
Rosie SasidharanThe SQL Server 2005 JDBC driver is far better than the SQL Server 2000 JDBC driver. The 2005 JDBC driver primarily consists for one file, sqljdbc.jar. ( if you want to use windows authentication there is another file you would need based on your platform x64 vs x86 called sqljdbc_auth.dll. If in the connect string you list ;integratedSecurity=true which means integrated security would be used and this second file would be required. The 2000 driver did not support integrated security.
The SQL 2000 JDBC driver was made up of the 3 jar files:
msbase.jar,mssqlserver.jar and msutil.jar.
If you want to use a Microsoft JDBC driver to connect to SQL Server 2005, than you should use the 2005 driver, sqljdbc.jar.
Follow the instructions in point 1 of the note #831162 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 JDBC Adapter questions 1 and 13.
Since the jar are different I assume you can use the both drivers, but it doesnt make sense. -
Sql 2005 standard edition for sql and AS databases with bpc 7.0 sp3 ?
hello
Install guide tells that we must use SQL 2005 Enterprise Edition with BPC except for Reporting Services.
Customer asks wether he could use SQL 2005 Standard Edition for SQL database and Analysis Services ?
Thanks.Hello Sorin. Two more questions, please:
1) what do you mean by "Also into Application server you need EE because only in this version you have control flow." ?
Is "control flow" "business process flow" new functionality ?
2) On the other hand, I don't think that BPC admin task is able to handle lite or full optimize without an Enterprise Edition Client.
But customer asks wether it is possible to install on application server
- SSIS standard edition for SSIS service
- SSRS standard edition for Reporting Services
- SQL client Enterprise Edition to let BPC admin task handle lite and full optimize properly.
Why all this ? Because Enterprise Edition costs ten times more than Standard Edition and in a multi-server configuration, customer has to buy several SQL Server licenses, one per server running at least one SQL server service. (For example, with SQL,SSIS and OLAP on one server, and SSIS and SSRS running on the application server, customer has to buy two SQL servers licenses).
Thanks. R. -
Hi ,
I have SAP 47X200 on SQL2005 64-bit installed on Windows enterprise edition X64.
I have installed database software using SQL4SAP.vbs as decrived in the installation guide : all OK , all work fine.
But , I want to use SQL 2005 with fixed memory as descrived in the article http://msdn.microsoft.com/en-us/library/ms191144.aspx
but in the server page proprierties box Memory i don't have the flag box Dynamic memory configuration but only Minimum server memory and Maximum server memory : if I set this two last value the same , the minimum server memory real is under this parameter.
So anyone know whi ? How to set fixed server memory ? Whi I don't have this flag?
thks Antonio Voce
Reward point for you.Hi ,
I set as you tell and now in database server proprierties under memory box i have this value :
Minimum server memory : 12000
Maximum server memory : 12000
Index creation memory : 12000
I have rebooted the server , starded SAP but in st04 I still see that the database memory is dynamically assigned :
Microsoft SQL Server 2005 - 9.00.3054.00 (X64) ##M Enterprise Edition
Windows NT 5.2 (Build 3790: Service Pack 2)
Database R3A Schema r3a Time of analysis 13.06.2008 16:38:46
DB Server SAPPONE DB startup 06/13/2008 16:35:38
CPUs available for SQL Server 16 of 16 Physical memory MB 32.765
Trace flag SAP release 620
Memory Usage
Current memory KB 600.320 Total SQL connections 61
Maximum memory KB 12.288.000 R/3 connections 60
Memory setting RANGE Free pages 675
Procedure cache KB 58.163 Data cache size KB 534.274
hit ratio % 87 hit ratio % 93 -
Hi,
We have a problem when we are trying to install SQL SP3 on SQL 2005 cluster.
The problem is described bellow:
We installed a new Windows 2008 R2 x64 failover cluster with two nodes.
As a next step we installed SQL 2005 Enterprise edition x64 on this failover cluster. We have finished the installation without problems. After SQL installation we are trying to install SQL SP3 . We have logged on using a domain administrator account and
we start the installation of SP3 with that user. In authentication mode screen the test gives a success status using either domain administrator-windows authentication or sa-sql authentication. On remote user account screen, when we give the domain
administrator account we get the message "the account information could not be verified. Press ok to return to authentication mode screen to determine the reason for failure".
We have tried to give the SQL services startup user on remote user account screen but the error is the same.
the domain administrator account exists on security logins of SQL with sysadmin rights.
Can someone help?
Thanks.Hi StelioMavro,
According to your error message, when you install SQL Server 2005 SP3 in your failover cluster, we need to verify if there was other instance that had been removed and the installation did not pass the login check. I recommend you use windows authentication
instead of SQL Server authentication when applying SP3. And the windows account used to run the SP3 setup program must have administrator privileges on the computer where SP3 will be installed.
For more information about how to install SQL Server 2005 SP3 in failover cluster, you can review the following article.
http://www.sqlcoffee.com/Tips0007.htm
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support
Maybe you are looking for
-
Can't print from CS4 (Illustrator, Photoshop, Acrobat)
Here is the issue... When I try to print from any of the CS4 programs (illustrator, photoshop, or acrobat) most times I get the spinning color wheel and eventually the application quits. Sometimes I do get to the print dialog box but that's as far a
-
Removing icons from Finder window sidebar after 10.6.7
Not a major calamity, but since upgrading to 10.6.7 I don't seem to be able to drag icons off the Finder window sidebar to remove them. In earlier versions of SL they would disappear in a small puff of smoke. Right-clicking and contextual menu comman
-
Does anyone know if it is possible to uninstall The Maverick update from IMac? Since installing it my computer is running so slow and every time I try to do something all I see is the spinning ball. It is so frustrating because it was working fine be
-
10.4.11 and Safari 3 are cursed!!!!!
I decided to update to 10.4.11 and Safari 3, with some hesitation due to past troubles with updates. Now everything crashes when I try to open it. Safari stays open for about one second before shutting down. What can I do? -Tom
-
I just have a question about call long and call duration. My fiance and I use skype everyday since we were dating and would like to retrieve information mainly call logs & call duration for immigration purposes; we were wondering if there is a way of