SQL 2005 UPDATE_STATISTICS Long runtimes

Hi All,
we've an issue with CCMS_sid_SID_UPDATE_STATISTICS SQL 2005 Job that sometimes (most of all) run for between 1 to 2 hours, but, sometimes runs for several hours (20 to 25h), we wish to know if someone experience this kind of issues and what can we do to improve this job performance.
We are in SQL 2005 and DB compatibility level is SQL 2005 (90).
someone as one clue on this issue? Shoul we schedule this job to run twice or more a week?
thanks in advance,
best regards,
Pedro H Rodrigues

Hi Pedro,
  Please refer to note 1178916 and 1305752.
12.02.2009 - 20:40:18 CET -  by SAP
Hello Dennis and Kenka,
The table sap_tabstats is not cleared out after the upgrade to SQL
Server 2008. The records in sap_tabstats became unusable after the
schema was switched to tcp from dbo. That is because the table
sap_tabstats has a column uid which tracks which schema a table belongs
to . Note 1305752 is being written to address this situation.
I logged into your system, and the table appears to of been populated
over the course of the last several days.
Best regards,
Dale Adams SQL Server port dev support

Similar Messages

  • Selecting from a SQL Server 2005 with long column names ( 30 chars)

    Hi,
    I was able to set up a db link from Oracle 11.2.0.1 to SQL Server 2005 using DG4ODBC.
    My problem is that some column names in the Sql Server are longer than 30 chars and trying to select them gives me the ORA-00972: identifier is too long error.
    If I omit these columns the select succeeds.
    I know I can create a view in the sql server and query it instead of the original table, but I was wondering if there's a way to overcome it with sql.
    My select looks like this:
    select "good_column_name" from sometable@sqlserver_dblink -- this works
    select "good_column_name","very_long_column_name>30 chars" from sometable@sqlserver_dblink -- ORA-00972Thanks

    I tried creating a view with shorter column names but selecting from the view still returns an error.
    create view v_Boards as (select [9650_BoardId] as BoardId, [9651_BoardType] as BoardType, [9652_HardwareVendor] as
    HardwareVendor, [9653_BoardVersion] as BoardVersion, [9654_BoardName] as BoardName, [9655_BoardDescription] as BoardDescription,
    [9656_SlotNumber] as SlotNumber, [9670_SegmentId] as SegmentId, [MasterID] as MasterID, [9657_BoardHostName] as BoardHostName,
    [9658_BoardManagementUsername] as BoardManagementUsername, [9659_BoardManagementPassword] as BoardManagementPassword,
    [9660_BoardManagementVirtualAddress] as BoardManagementVirtualAddress, [9661_BoardManagementTelnetLoginPrompt] as
    MANAGEMENTTELNETLOGINPROMPT, [9662_BoardManagementTelnetPasswordPrompt] as MANAGEMENTTELNETPASSPROMPT,
    [9663_BoardManagementTelnetCommandPrompt] as MANAGEMENTTELNETCOMMANDPROMPT FROM Boards)performing a select * from this view in sqlserver works and show the short column names
    this is the error i'm getting for performing a select * from v_boards@sqlserver_dblink
    ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
    [Microsoft][SQL Native Client][SQL Server]Invalid column name 'BoardManagementTelnetLoginProm'. {42S22,NativeErr = 207}[Microsoft]
    [SQL Native Client][SQL Server]Invalid column name 'BoardManagementTelnetPasswordP'. {42S22,NativeErr = 207}[Microsoft][SQL Native
    Client][SQL Server]Invalid column name 'BoardManagementTelnetCommandPr'. {42S22,NativeErr = 207}[Microsoft][SQL Native Client][SQL
    Server]Statement(s) could not be prepared. {42000,NativeErr = 8180}
    ORA-02063: preceding 2 lines from sqlserver_dblinkI also tried replacing the * with specific column names but it fails on the columns that have a long name (it doesn't recognize the short names from the view)
    what am I doing wrong?
    Edited by: Pyrocks on Dec 22, 2010 3:58 PM

  • Browse Data & Parameter flds no longer fully populated after upgd  SQL 2005

    I upgrade our SQL 2000 Server last weekend to SQL 2005 (sp2).
    Now our Crystal reports that access SQL data are not working correctly. Parameter Fields are showing little to no data, where before the upgrade we were seeing many more rows in the list.
    Digging further, I looked at the fields used for the dynamic LOV. If I use Browse Data on those fields I am seeing the same lack of data. One "Browse Data" that would typically return 80 items now returns 3 items. In that report the data field is DateTime. In another report, the field is string.
    I am also seeing an extra check for User Name and password before getting to the Enter values screen for the parameter.
    I am using Crystal Developer 11.0.0.1994. It is happening on multiple PCs. I tried with both the original SQL ODBC Driver and the newer SQL Native Client ODBC driver, with the same result.
    I've looked at this for 3 days with no luck. Any ideas?

    Full SysAdmin rights.
    I use a dedicated ODBC connection and have tried both "SQL Server" odbc driver and "SQL NativeClient" (2005) odbc driver.
    If I go to Crystal, to the Field Explorer, to the one of the fields, right-click and "Browse Data..." I get two results (I expect 82 results and have seen that in the past.) If I paste the query from Crystal, Database, "Show SQL Query.."  to SQL Server Management Studio, I see the full, correct results.
    In one example the field browsed is called "PeriodEndDate" (DateTime). A dynamic Parameter Field was created accessing this field. Here is the security curiosity...refreshing now asks for the user login each time "Prompt for new parameter values" is selected. It used to ask only the first time. The Crystal: Data Explorer" shows the current connection logged in ok.
    The two issues may or may not be related. Certainly if #1 were fixed, dynamic parameters would return the correct results. Even if it asked for the password each time.
    1.) "Browse Data" returning a smaller result than normal.
    2.) "Parameter Prompt" asks for Server Name, Database Name, User Name, and Password on
         each refresh selecting "Prompt for new parameter values".

  • DPM 2010 SharePoint 2007 and SQL 2005 long time Recovery point

    Hi, i have two farms with two dedicated DPM for each of them
    SP 2010 with SQL 2008 R2
    SP 2007 with SQL 2005
    While recovery point is running for 2010 multiple databases are taken simultaneously while in 2007 only one database at time in sequential order which leads in large time for recovery point of farm.
    any recommendations or modification known for this behavior
    Thanks
    Mina

    Hi,
    I have not tried this with SharePoint workload - but give this a try.
    Steps to enable parallel backups for SQL 2005 databases:
    1. The fix in SQL Writer to enable parallel backups has been rolled out as part of SQL server SP4. So please update SQL Server 2005 to SP4.
    2. On DPM Server, create Registry Key “SQL2005_ParallelBackup” under “HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration”
    3. Create String Value with Name equals FQDN of SQL Server
    and empty value, under registry key “SQL2005_ParallelBackup”
    Let me know if that worked.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This
    posting is provided "AS IS" with no warranties, and confers no rights.

  • 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
    Raj

    Hi
      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

  • SQL 2005 discoveries after upgrade to Operations Manager 2012 R2 UR3 upgrade

    Hi
    We did a (succesfull) upgrade of our SCOM 2012 SP1 environment to 2012 R2 UR3. We noticed after the upgrade that databases of some  SQL 2005 clustered instances on Windows 2003 R2 SP2 are no longer discovered. checking the eventlog shows the eventid
    21405 on the DiscoverSQL2005DB.vbs disvovery (process exited with 4294967295)
    Browsing and checking several webfinds didn't provide a solution yet. Perhaps I overlooked the obvious....
    Possible solutions which didn't bring relief yet:
    check on SQL SP's
    WMI registry settings [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM] ": Low/High Threshold On Events
    WMI repair, mofcomp...
    Uninstall/Reinstall Monitorring Agent
    manual run of the discover script returns all info
    The runas discover and monitor account(s) are local admin on the OS and SA on the SQL instances
    I'm stuck: right now we wanted to present some distributed applications through LiveMaps in scom to our internal customers and some essential databases are no longer discovered/monitorred.
    Any help highly appreciated

    I'd just like to add that since upgrading all of our environments to 2012 R2 UR3, we are receiving multiple alerts for multiple script failures - e.g. Events 21404, 21405 to name a couple.
    I have logged a few Microsoft Premier Support Calls and they are still working on them.
    We get this on all SQL 2005,2008 running on Windows Server 2003.  Microsoft's response to this is:
    "This is a known bug in the latest SQL MP. This is due to the problem with the DiscoverSQL2008DBEngineDiscovery.vbs and DiscoverSQL2005DBEngineDiscovery.vbs scripts which contains the following line of code :                   
    tcp = oQuery.ItemIndex(0).PropertyStrVal
    The issue is the ItemIndex is supported only on Vista+ operating systems. The product group is currently investigating and evaluating the issue and I don’t think the fix will be released recently…"
    I guess that meant "any time soon' :)
    I should add that we also upgraded the SQL MPs around this time too, to 6.5.1.0.
    So as you can appreciate, we just have to put up with this for now!
    Cheers

  • CF8 and connection pooling using MS SQL 2005 JDBC Driver

    After upgrading one of our production servers to CF8 we're
    getting errors under load while connecting to MS SQL 2000 data
    bases using the MS SQL 2005 JDBC 1.1 driver instead of the driver
    cf8 ships with. The following error is recorded in the logs:
    Error Executing Database Query. The TCP/IP connection to the
    host has failed. java.net.BindException: Address already in use:
    connect
    Confirmed by the database statistics, Coldfusion is no longer
    pooling the database connections. After changing the data source to
    use the build in driver everything works fine. We've been using
    this driver and CF7 for some time without this error.
    Is this a compatibility issue between the driver and Java 6?
    Or is there a conflict between this driver and the build in driver?
    Has anyone seen similar issues? We’d like to use this driver
    rather then the build in one.
    Thanks,
    Remy Becher

    thanks for the answer...I have been waiting for one..I do agree that connection ppooling is same ..but I would appreciate it if someone could point me to some example implemenations using MS JDBC type 4 driver..
    Thanks again..
    PS: I did search the forum before posting this..

  • Trying to use Linked Servers in SQL 2005 to connect to RDB 7

    I'm looking for detailed info on how to set up a linked server in SQL 2005 to connect to my Oracle RDB 7 database (running on VMS). I'm able to connect via odbc using VS.Net and Sql Server 2005 Reporting Services. I'm not sure if I need to use the ODP.NET or not. I have created a generic linked server, but it requires me to use the OpenQuery function to access the data, which is not giving me the functionality I'm looking for.

    Hi doanpq,
    Please download and install OLE DB Provider for Visual FoxPro 9.0, which exposes OLE DB interfaces that you can use to access Visual FoxPro databases and tables from other programming languages and applications. Please see:
    http://www.microsoft.com/en-us/download/details.aspx?id=14839
    Then, please follow up the following article to create a linked server:
    Creating Linked Servers:
    http://technet.microsoft.com/en-us/library/ff772782(v=sql.105).aspx
    For more information, you can also take a look at the following article, especially Dave K's comment:
    http://blog.dbase.integralwebsolutions.co.za/2008/10/accessing-your-dbf-tables-via-linked.html
    Elvis Long
    TechNet Community Support

  • Microsoft SQL 2005 preload problem

    Hi Guys,
    First post! I took receipt of my W520 a few weeks ago. It is great, very pleased with it on the whole.
    There is one problem, however. I play a fair amount of recreational card games over the internet. This requires a program which converts the text file “hand histories” into postgreSQL server data to make it quickly readable and provide tracking for win/loss among a whole host of other statistical things.
    Unfortunately after going through their troubleshooting numerous times, going through factory restore and repeating the process, I still cannot get my SQL server to automatically start. Believe me, I have tried everything. Running them all as admin, editing the startup in the windows “services” dialog etc etc. The server does start manually and the program works fine, but every time I start it I have to do it manually and it is irritating. It should just start up in the background but it doesn’t.
    I believe it is the Microsoft SQL 2005 express that is somehow blocking the auto start. Basically, I want my Lenovo as it is, just without the preloaded SQL server. Using the factory restore just reloads it back on and when I manually uninstall the SQL server I still have the same problem. I believe it leaves a lot of little nuggets behind when you uninstall it through the standard W7 “uninstall a program” and the full uninstall looks a long and difficult process, with no guarantee of really removing everything.
    So, the plan is to install a bare copy of W7 using a borrowed disk, install my own personal SQL program and test to see if that works. I am almost certain it will. From there, I plan to build back my programs on top so I essentially have my PC now, bar the bundled SQL 2005 express or whatever it is. Following this I will make a system image and store it away safely to avoid all this mess and only reinstall using the factory disks if absolutely necessary.
    I have my W7 OEM serial, found using a serial grabber. Obviously I didn’t pay all this money to scrap all the useful thinkvantage tools like “airbag” and basic fingerprint/camera drivers etc. I also like the realtime warranty countdown timer. How should I go about this task? Is all I need is the PC serial underneath to reload thinkvantage at a later date with full functionality? Is there anything I should consider before starting?
    If there is a better subforum to post this question in, please let me know.
    Many thanks,
    Nick

    What is service dependency?
    Yes I tried to make a batch file. Not in startup folder, but one on the desktop that had the right path. This returned an error from the statistical program and not the SQL server. It initially looked hopeful as I had it start up the "start server" option for the right SQL server. This opened up the dos window and said it had correctly started. However, when the stats program launched it hung up on loadscreen and returned an error message. Not sure why this was, but it didn't seem to like being loaded through a .bat.
    This seems like a work around more than a solution anyway. I just want to get it to work properly.
    Here is the thread in the database analaysis program forum for your reference.
    http://forums.holdemmanager.com/general-support/197501-hem-crashing.html
    Thanks,
    Nick

  • SQL 2005 mirroring : Abrupt Automatic failover

    hi All, 
    We have a SQL 2005 SP4 mirroring  setup of 15 DBs with Principal(P), Mirror(M) & Witness (W).
    We have now seen abrupt DB failovers for some of the databases (yest it was 4 out of 15) from P to M.
    Errors were seen on Witness server as follows for all Dbs that failed over:
    Date 07/01/2015 11:07:48 PM
    Log SQL Server (Current - 08/01/2015 12:00:00 AM)
    Source spid19s
    Message
    The mirroring connection to "TCP://<server.domain.com>:5022" has timed out for database "<DBName>" after 10 seconds without a response.  Check the service and network connections.
    Actions taken:
    1. Network and Firewall team reverted that no error detected and no network traffic between the witness server and db server during the db auto failover period.
    2. On the system side, we have verified that no hardware error found on either VM or SAN storage, and no Symantec SQL backup jobs running nor anti virus scanning during the db auto failover period too.
    3. We did see some high amount of IO activity on P server around failover time. Some IO errors similar to below were seen, however point to note is these errors were not only for the DBs that failed over, but for others including TEMPDB:
    Date 07/01/2015 11:07:38 PM
    Log SQL Server (Current - 08/01/2015 4:06:00 AM)
    Source spid2s
    Message
    SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [R:\SQLDATA\MSSQL.1\MSSQL\Data\<DBName>.mdf] in database [DBName] (5).  The OS file handle is 0x000000000000095C.  The offset of the
    latest long I/O is: 0x0000054ff22000
    Questions:
    1. I assumed that the Witness keeps polling P & M on DB mirroring endpoints (in our case 5022) to check that the DBs are online, but Network team says there is no activity on that port, is my understanding correct?
    2. Is there any other reason for DB failover ? 
    Link referred:  
    http://dba.stackexchange.com/questions/22402/what-can-cause-a-mirroring-session-to-timeout-then-failover-sql-server-2005
    http://msdn.microsoft.com/en-us/library/ms179344(v=sql.90).aspx
    Any help is highly appreciated!!!
    Regards,
    Mandar

    This is common with Mirroring server it is not as resilient to changes as log shipping. Are you aware about
    below fact although not directly related to your question
    If you plan to use high-safety mode with automatic failover, the normal load on each failover partner should be less than 50 percent of the CPU. If your work load overloads the CPU, a failover partner might be unable to ping the other server instances in
    the mirroring session. This causes a unnecessary failover. If you cannot keep the CPU usage under 50 percent, we recommend that you use either high-safety mode without automatic failover or high-performance mode.
    Now to your problem
    The mirroring connection to "TCP://<server.domain.com>:5022" has timed out for database "<DBName>" after 10 seconds without a response.  Check the service and network connections.
    I would say there was network dip for more than 10 seconds and since default failover time is 10 seconds and for few databases witness thought principal cannot be reached it initiated failover.
    Network team is incorrect to say there was no dip (its common with NOC team not to take responsibility)
    This Support Article is worth reading specially the network part
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • SQL 2005: (yep!) During setup how place "ldf" files on drive D, "mdf" on drive E?

    Lovers of sql 2005 (all 2 of you) -- rejoice -- a question for you
    We have an old sql 2005 box that I am rebuilding with a newer OS (please, don't ask why!) but using the original master, msdb, etc.   The main problem I'm having is during the sql 2005 install I need to install the log files on drive D and the mdf's
    on E but the setup program does not seems to allow for this. (I can setup "Databases Services" on drive D but then the log files are on D too. Not what I wanted.)
    edm2

    I have long forgotten Installation of 2005 but I doubt, that it wont allow you .Anyways after installation you can change the location its not big deal.
    How to move system databases in sql Server 2005
    >>Lovers of sql 2005 (all 2 of you) -- rejoice -- a question for you
    Just ask question No need to add a punchline.
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Installation failed SQL 2005

    Hi all ~ I have problem on installing SQL 2005: please have a look on the following log:
    === Verbose logging started: 2/23/2015  10:59:24  Build type: SHIP UNICODE 4.05.6002.00  Calling process: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe ===
    MSI (c) (FC:98) [10:59:24:019]: Resetting cached policy values
    MSI (c) (FC:98) [10:59:24:019]: Machine policy value 'Debug' is 0
    MSI (c) (FC:98) [10:59:24:019]: ******* RunEngine:
               ******* Product: {90A40409-6000-11D3-8CFE-0150048383C9}
               ******* Action:
               ******* CommandLine: **********
    MSI (c) (FC:98) [10:59:24:020]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (FC:98) [10:59:24:020]: Grabbed execution mutex.
    MSI (c) (FC:98) [10:59:24:022]: Cloaking enabled.
    MSI (c) (FC:98) [10:59:24:022]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (FC:98) [10:59:24:022]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (EC:B8) [10:59:24:030]: Running installation inside multi-package transaction {90A40409-6000-11D3-8CFE-0150048383C9}
    MSI (s) (EC:B8) [10:59:24:030]: Grabbed execution mutex.
    MSI (s) (EC:5C) [10:59:24:032]: Resetting cached policy values
    MSI (s) (EC:5C) [10:59:24:032]: Machine policy value 'Debug' is 0
    MSI (s) (EC:5C) [10:59:24:032]: ******* RunEngine:
               ******* Product: {90A40409-6000-11D3-8CFE-0150048383C9}
               ******* Action:
               ******* CommandLine: **********
    MSI (s) (EC:5C) [10:59:24:032]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (EC:5C) [10:59:24:038]: SRSetRestorePoint skipped for this transaction.
    MSI (s) (EC:5C) [10:59:24:039]: End dialog not enabled
    MSI (s) (EC:5C) [10:59:24:039]: Original package ==> C:\WINDOWS\Installer\180ca.msi
    MSI (s) (EC:5C) [10:59:24:039]: Package we're running from ==> C:\WINDOWS\Installer\180ca.msi
    MSI (s) (EC:5C) [10:59:24:043]: APPCOMPAT: looking for appcompat database entry with ProductCode '{90A40409-6000-11D3-8CFE-0150048383C9}'.
    MSI (s) (EC:5C) [10:59:24:043]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (EC:5C) [10:59:24:050]: MSCOREE already loaded, using loaded copy
    MSI (s) (EC:5C) [10:59:24:054]: Opening existing patch 'C:\WINDOWS\Installer\57492f7.msp'.
    MSI (s) (EC:5C) [10:59:24:054]: Note: 1: 2203 2: C:\WINDOWS\Installer\57492f7.msp 3: -2147287038
    MSI (s) (EC:5C) [10:59:24:054]: Couldn't find local patch 'C:\WINDOWS\Installer\57492f7.msp'. Looking for it at its source.
    MSI (s) (EC:5C) [10:59:24:054]: Resolving Patch source.
    MSI (s) (EC:5C) [10:59:24:054]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (EC:5C) [10:59:24:054]: User policy value 'DisableMedia' is 0
    MSI (s) (EC:5C) [10:59:24:054]: Machine policy value 'AllowLockdownMedia' is 0
    MSI (s) (EC:5C) [10:59:24:054]: SOURCEMGMT: Media enabled only if package is safe.
    MSI (s) (EC:5C) [10:59:24:054]: SOURCEMGMT: Looking for sourcelist for product {34E1EB8F-BDB2-475C-BD80-A86217C41B4D}
    MSI (s) (EC:5C) [10:59:24:054]: SOURCEMGMT: Adding {34E1EB8F-BDB2-475C-BD80-A86217C41B4D}; to potential sourcelist list (pcode;disk;relpath).
    MSI (s) (EC:5C) [10:59:24:055]: SOURCEMGMT: Now checking product {34E1EB8F-BDB2-475C-BD80-A86217C41B4D}
    MSI (s) (EC:5C) [10:59:24:055]: SOURCEMGMT: Media is enabled for product.
    MSI (s) (EC:5C) [10:59:24:055]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
    MSI (s) (EC:5C) [10:59:24:055]: SOURCEMGMT: Processing net source list.
    MSI (s) (EC:5C) [10:59:24:055]: Note: 1: 1402 2: UNKNOWN\Net 3: 2
    MSI (s) (EC:5C) [10:59:24:055]: Note: 1: 1706 2: -2147483647 3: OWC11SP3.MSP
    MSI (s) (EC:5C) [10:59:24:055]: SOURCEMGMT: Processing media source list.
    MSI (s) (EC:5C) [10:59:25:063]: SOURCEMGMT: Resolved source to: 'OWC11SP3.MSP'
    MSI (s) (EC:5C) [10:59:51:327]: Note: 1: 1314 2: OWC11SP3.MSP
    MSI (s) (EC:5C) [10:59:51:327]: Unable to create a temp copy of patch 'OWC11SP3.MSP'.
    MSI (s) (EC:5C) [10:59:51:327]: Searching provided command line patches for patch code {34E1EB8F-BDB2-475C-BD80-A86217C41B4D}
    MSI (s) (EC:5C) [10:59:51:329]: Note: 1: 1708
    MSI (s) (EC:5C) [10:59:51:329]: Product: Microsoft Office 2003 Web Components -- Installation failed.
    MSI (s) (EC:5C) [10:59:51:330]: Windows Installer installed the product. Product Name: Microsoft Office 2003 Web Components. Product Version: 11.0.6558.0. Product Language: 1033. Installation success or error status: 1635.
    MSI (s) (EC:5C) [10:59:51:332]: MainEngineThread is returning 1635
    MSI (s) (EC:B8) [10:59:51:332]: No System Restore sequence number for this installation.
    This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package.
    C:\WINDOWS\Installer\180ca.msi
    MSI (s) (EC:B8) [10:59:51:333]: User policy value 'DisableRollback' is 0
    MSI (s) (EC:B8) [10:59:51:333]: Machine policy value 'DisableRollback' is 0
    MSI (s) (EC:B8) [10:59:51:333]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (EC:B8) [10:59:51:334]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (EC:B8) [10:59:51:334]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (EC:B8) [10:59:51:335]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (EC:B8) [10:59:51:335]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (EC:B8) [10:59:51:335]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (EC:B8) [10:59:51:335]: Restoring environment variables
    MSI (c) (FC:98) [10:59:51:337]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (FC:98) [10:59:51:337]: MainEngineThread is returning 1635
    === Verbose logging stopped: 2/23/2015  10:59:51 ===
    Please help help

    this problem solved, i replace back the .msi to the windows\installer, now i have another probelm::
    === Verbose logging started: 2/23/2015  14:02:33  Build type: SHIP UNICODE 4.05.6002.00  Calling process: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe ===
    MSI (c) (44:50) [14:02:33:615]: Resetting cached policy values
    MSI (c) (44:50) [14:02:33:615]: Machine policy value 'Debug' is 0
    MSI (c) (44:50) [14:02:33:615]: ******* RunEngine:
               ******* Product: {E46A76D1-9FB9-4770-BA24-3975EF4D120A}
               ******* Action:
               ******* CommandLine: **********
    MSI (c) (44:50) [14:02:33:616]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (44:50) [14:02:33:616]: Grabbed execution mutex.
    MSI (c) (44:50) [14:02:33:618]: Cloaking enabled.
    MSI (c) (44:50) [14:02:33:618]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (44:50) [14:02:33:619]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (B8:9C) [14:02:33:626]: Running installation inside multi-package transaction {E46A76D1-9FB9-4770-BA24-3975EF4D120A}
    MSI (s) (B8:9C) [14:02:33:626]: Grabbed execution mutex.
    MSI (s) (B8:64) [14:02:33:626]: Resetting cached policy values
    MSI (s) (B8:64) [14:02:33:626]: Machine policy value 'Debug' is 0
    MSI (s) (B8:64) [14:02:33:626]: ******* RunEngine:
               ******* Product: {E46A76D1-9FB9-4770-BA24-3975EF4D120A}
               ******* Action:
               ******* CommandLine: **********
    MSI (s) (B8:64) [14:02:33:626]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (B8:64) [14:02:33:632]: SRSetRestorePoint skipped for this transaction.
    MSI (s) (B8:64) [14:02:33:632]: End dialog not enabled
    MSI (s) (B8:64) [14:02:33:633]: Original package ==> C:\WINDOWS\Installer\23e28752.msi
    MSI (s) (B8:64) [14:02:33:633]: Package we're running from ==> C:\WINDOWS\Installer\23e28752.msi
    MSI (s) (B8:64) [14:02:33:637]: APPCOMPAT: looking for appcompat database entry with ProductCode '{E46A76D1-9FB9-4770-BA24-3975EF4D120A}'.
    MSI (s) (B8:64) [14:02:33:637]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (B8:64) [14:02:33:644]: MSCOREE already loaded, using loaded copy
    MSI (s) (B8:64) [14:02:33:648]: Machine policy value 'DisablePatch' is 0
    MSI (s) (B8:64) [14:02:33:648]: Machine policy value 'AllowLockdownPatch' is 0
    MSI (s) (B8:64) [14:02:33:648]: Machine policy value 'DisableLUAPatching' is 0
    MSI (s) (B8:64) [14:02:33:648]: Machine policy value 'DisableFlyWeightPatching' is 0
    MSI (s) (B8:64) [14:02:33:649]: APPCOMPAT: looking for appcompat database entry with ProductCode '{E46A76D1-9FB9-4770-BA24-3975EF4D120A}'.
    MSI (s) (B8:64) [14:02:33:649]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (B8:64) [14:02:33:649]: Transforms are not secure.
    MSI (s) (B8:64) [14:02:33:650]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0018_SV53749_MSXML6_1.log'.
    MSI (s) (B8:64) [14:02:33:650]: Command Line: STPSETUPTHREADID=1484 STPSETUPPROCESSID=9540 EXTERNALCONTROL=1 ADDLOCAL=ALL SKIPPENDINGREBOOTCHECK=1 APPGUID={FFFA78A7-BD51-4255-8470-C4D4A85B49F5} REBOOT=ReallySuppress CURRENTDIRECTORY=C:\Program Files\Microsoft
    SQL Server\90\Setup Bootstrap CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=9540
    MSI (s) (B8:64) [14:02:33:650]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{EE6525FC-1729-4E76-A8C1-12C756BA0AD0}'.
    MSI (s) (B8:64) [14:02:33:650]: Product Code passed to Engine.Initialize:           '{E46A76D1-9FB9-4770-BA24-3975EF4D120A}'
    MSI (s) (B8:64) [14:02:33:650]: Product Code from property table before transforms: '{E46A76D1-9FB9-4770-BA24-3975EF4D120A}'
    MSI (s) (B8:64) [14:02:33:650]: Product Code from property table after transforms:  '{E46A76D1-9FB9-4770-BA24-3975EF4D120A}'
    MSI (s) (B8:64) [14:02:33:650]: Product registered: entering maintenance mode
    MSI (s) (B8:64) [14:02:33:650]: Product {E46A76D1-9FB9-4770-BA24-3975EF4D120A} is admin assigned: LocalSystem owns the publish key.
    MSI (s) (B8:64) [14:02:33:650]: Product {E46A76D1-9FB9-4770-BA24-3975EF4D120A} is managed.
    MSI (s) (B8:64) [14:02:33:650]: MSI_LUA: Credential prompt not required, user is an admin
    MSI (s) (B8:64) [14:02:33:650]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
    MSI (s) (B8:64) [14:02:33:650]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
    MSI (s) (B8:64) [14:02:33:651]: Package name retrieved from configuration data: 'msxml6.msi'
    MSI (s) (B8:64) [14:02:33:651]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
    MSI (s) (B8:64) [14:02:33:654]: Note: 1: 2262 2: AdminProperties 3: -2147287038
    MSI (s) (B8:64) [14:02:33:654]: Machine policy value 'DisableMsi' is 1
    MSI (s) (B8:64) [14:02:33:654]: Machine policy value 'AlwaysInstallElevated' is 0
    MSI (s) (B8:64) [14:02:33:654]: User policy value 'AlwaysInstallElevated' is 0
    MSI (s) (B8:64) [14:02:33:654]: Product {E46A76D1-9FB9-4770-BA24-3975EF4D120A} is admin assigned: LocalSystem owns the publish key.
    MSI (s) (B8:64) [14:02:33:654]: Product {E46A76D1-9FB9-4770-BA24-3975EF4D120A} is managed.
    MSI (s) (B8:64) [14:02:33:654]: Running product '{E46A76D1-9FB9-4770-BA24-3975EF4D120A}' with elevated privileges: Product is assigned.
    MSI (s) (B8:64) [14:02:33:654]: PROPERTY CHANGE: Adding STPSETUPTHREADID property. Its value is '1484'.
    MSI (s) (B8:64) [14:02:33:654]: PROPERTY CHANGE: Adding STPSETUPPROCESSID property. Its value is '9540'.
    MSI (s) (B8:64) [14:02:33:654]: PROPERTY CHANGE: Adding EXTERNALCONTROL property. Its value is '1'.
    MSI (s) (B8:64) [14:02:33:654]: PROPERTY CHANGE: Adding ADDLOCAL property. Its value is 'ALL'.
    MSI (s) (B8:64) [14:02:33:654]: PROPERTY CHANGE: Adding SKIPPENDINGREBOOTCHECK property. Its value is '1'.
    MSI (s) (B8:64) [14:02:33:654]: PROPERTY CHANGE: Adding APPGUID property. Its value is '{FFFA78A7-BD51-4255-8470-C4D4A85B49F5}'.
    MSI (s) (B8:64) [14:02:33:654]: PROPERTY CHANGE: Adding REBOOT property. Its value is 'ReallySuppress'.
    MSI (s) (B8:64) [14:02:33:655]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap'.
    MSI (s) (B8:64) [14:02:33:655]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
    MSI (s) (B8:64) [14:02:33:655]: PROPERTY CHANGE: Adding MSICLIENTUSESEXTERNALUI property. Its value is '1'.
    MSI (s) (B8:64) [14:02:33:655]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '9540'.
    MSI (s) (B8:64) [14:02:33:655]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
    MSI (s) (B8:64) [14:02:33:655]: PROPERTY CHANGE: Adding MsiRestartManagerSessionKey property. Its value is '2bacf19a1da7c4438b188852d7df058c'.
    MSI (s) (B8:64) [14:02:33:655]: RESTART MANAGER: Session opened.
    MSI (s) (B8:64) [14:02:33:655]: TRANSFORMS property is now:
    MSI (s) (B8:64) [14:02:33:655]: PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is '1033'.
    MSI (s) (B8:64) [14:02:33:655]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '300'.
    MSI (s) (B8:64) [14:02:33:658]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming
    MSI (s) (B8:64) [14:02:33:660]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\Favorites
    MSI (s) (B8:64) [14:02:33:662]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Network Shortcuts
    MSI (s) (B8:64) [14:02:33:663]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\Documents
    MSI (s) (B8:64) [14:02:33:665]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
    MSI (s) (B8:64) [14:02:33:667]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Recent
    MSI (s) (B8:64) [14:02:33:668]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\SendTo
    MSI (s) (B8:64) [14:02:33:671]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Templates
    MSI (s) (B8:64) [14:02:33:671]: SHELL32::SHGetFolderPath returned: C:\ProgramData
    MSI (s) (B8:64) [14:02:33:673]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Local
    MSI (s) (B8:64) [14:02:33:675]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\Pictures
    MSI (s) (B8:64) [14:02:33:679]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
    MSI (s) (B8:64) [14:02:33:681]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
    MSI (s) (B8:64) [14:02:33:682]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
    MSI (s) (B8:64) [14:02:33:685]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
    MSI (s) (B8:64) [14:02:33:687]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
    MSI (s) (B8:64) [14:02:33:691]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
    MSI (s) (B8:64) [14:02:33:693]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
    MSI (s) (B8:64) [14:02:33:695]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
    MSI (s) (B8:64) [14:02:33:697]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start Menu
    MSI (s) (B8:64) [14:02:33:698]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\Desktop
    MSI (s) (B8:64) [14:02:33:701]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
    MSI (s) (B8:64) [14:02:33:701]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
    MSI (s) (B8:64) [14:02:33:702]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
    MSI (s) (B8:64) [14:02:33:711]: MSI_LUA: Setting MsiRunningElevated property to 1 because the install is already running elevated.
    MSI (s) (B8:64) [14:02:33:711]: PROPERTY CHANGE: Adding MsiRunningElevated property. Its value is '1'.
    MSI (s) (B8:64) [14:02:33:711]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
    MSI (s) (B8:64) [14:02:33:711]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'Sun Life'.
    MSI (s) (B8:64) [14:02:33:711]: PROPERTY CHANGE: Adding COMPANYNAME property. Its value is 'Sun Life Hong Kong Limited'.
    MSI (s) (B8:64) [14:02:33:711]: PROPERTY CHANGE: Adding Installed property. Its value is '00:00:00'.
    MSI (s) (B8:64) [14:02:33:711]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\WINDOWS\Installer\23e28752.msi'.
    MSI (s) (B8:64) [14:02:33:711]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'C:\WINDOWS\Installer\23e28752.msi'.
    MSI (s) (B8:64) [14:02:33:711]: Machine policy value 'MsiDisableEmbeddedUI' is 0
    MSI (s) (B8:64) [14:02:33:711]: EEUI - Disabling MsiEmbeddedUI due to existing external or embedded UI
    MSI (s) (B8:64) [14:02:33:711]: EEUI - Disabling MsiEmbeddedUI for service because it's not a quiet/basic install
    MSI (s) (B8:64) [14:02:33:712]: Note: 1: 2205 2:  3: PatchPackage
    MSI (s) (B8:64) [14:02:33:712]: Machine policy value 'DisableRollback' is 0
    MSI (s) (B8:64) [14:02:33:712]: User policy value 'DisableRollback' is 0
    MSI (s) (B8:64) [14:02:33:712]: PROPERTY CHANGE: Adding UILevel property. Its value is '2'.
    === Logging started: 2/23/2015  14:02:33 ===
    MSI (s) (B8:64) [14:02:33:713]: PROPERTY CHANGE: Adding Preselected property. Its value is '1'.
    MSI (s) (B8:64) [14:02:33:713]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
    MSI (s) (B8:64) [14:02:33:713]: Doing action: INSTALL
    Action start 14:02:33: INSTALL.
    MSI (s) (B8:64) [14:02:33:717]: Running ExecuteSequence
    MSI (s) (B8:64) [14:02:33:717]: Doing action: SkipInstallCA
    MSI (s) (B8:64) [14:02:33:720]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SkipInstallCA'
    MSI (s) (B8:B8) [14:02:33:730]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI92BC.tmp, Entrypoint: SkipInstall
    MSI (s) (B8:B0) [14:02:33:730]: Generating random cookie.
    MSI (s) (B8:B0) [14:02:33:743]: Created Custom Action Server with PID 8820 (0x2274).
    MSI (s) (B8:20) [14:02:33:788]: Running as a service.
    MSI (s) (B8:20) [14:02:33:791]: Hello, I'm your 32bit Impersonated custom action server.
    Action start 14:02:33: SkipInstallCA.
    This package is not supported on this operating system.
    Action ended 14:02:33: SkipInstallCA. Return value 3.
    Action ended 14:02:33: INSTALL. Return value 3.
    Property(S): ProductCode = {E46A76D1-9FB9-4770-BA24-3975EF4D120A}
    Property(S): Manufacturer = Microsoft Corporation
    Property(S): ProductVersion = 6.20.2016.0
    Property(S): ProductLanguage = 1033
    Property(S): UpgradeCode = {1B117BA7-5BC1-419E-820E-7D4F3F412C7B}
    Property(S): ARPPRODUCTICON = ARPIco
    Property(S): PIDTemplate = 53934<````=````=````=````=`````>@@@@@
    Property(S): PROMPTROLLBACKCOST = P
    Property(S): DiskPrompt = [1]
    Property(S): INSTALLLEVEL = 100
    Property(S): ALLUSERS = 1
    Property(S): InstallMode = Typical
    Property(S): ErrorIcon = ErrorIco
    Property(S): SuccessIcon = SuccessIco
    Property(S): WarningIcon = WarningIco
    Property(S): LicenseIcon = LicenseIco
    Property(S): SetupIcon = SetupIco
    Property(S): CompleteIcon = CompleteIco
    Property(S): CustomIcon = CustomIco
    Property(S): RepairIcon = RepairIco
    Property(S): RemoveIcon = RemoveIco
    Property(S): ModifyIcon = ModifyIco
    Property(S): NewIcon = NewIco
    Property(S): UpIcon = UpIco
    Property(S): DialogBanner = BannerBmp
    Property(S): WelcomeBmp = WelcomeBmp
    Property(S): ApplicationUsers = AllUsers
    Property(S): Details = 0
    Property(S): AgreeToLicense = No
    Property(S): _IsMaintenance = Reinstall
    Property(S): _IsMaintenance2 = Modify
    Property(S): ReinstallModeText = omus
    Property(S): Display_IsBitmapDlg = 1
    Property(S): Interrupted = 0
    Property(S): ProductID = none
    Property(S): ISENABLEDWUSFINISHDIALOG = 1
    Property(S): SQLServerText1 = 0
    Property(S): SQLServerVersionText1 = 0
    Property(S): SQLServerVersionText2 = 0
    Property(S): SQLServerVersionText3 = 0
    Property(S): CA_ERRORCOUNT = 0
    Property(S): CA_WARNINGCOUNT = 0
    Property(S): CA_SUCCESSCOUNT = 0
    Property(S): MINIMUMOS = true
    Property(S): UI_SHOWCOPYRIGHT = yes
    Property(S): ShowUserRegistrationDlg = 1
    Property(S): ErrorDialog = ErrorDlg
    Property(S): DefaultUIFont = Tahoma8
    Property(S): VersionNT = 600
    Property(S): ARPHELPLINK = http://support.microsoft.com/kb/2758696
    Property(S): SecureCustomProperties = NEWERFOUND.72DE5BCD_5CB0_4335_B118_AB4C4DA70AE1;OLDERFOUND.72DE5BCD_5CB0_4335_B118_AB4C4DA70AE1;OLDERFOUND2.72DE5BCD_5CB0_4335_B118_AB4C4DA70AE1
    Property(S): DesktopFolder = C:\Users\Public\Desktop\
    Property(S): ProgramFilesFolder = C:\Program Files\
    Property(S): ButtonTextStyle = {\ButtonTextStyle}
    Property(S): DlgTextStyle = {\DlgTextStyle}
    Property(S): DlgTextStyleB = {\DlgTextStyleB}
    Property(S): DlgTitleStyle = {\DlgTitleStyle}
    Property(S): DlgTitleStyleB = {\DlgTitleStyleB}
    Property(S): FixedStyle = {\FixedStyle}
    Property(S): Installed = 00:00:00
    Property(S): COMPANYNAME = Sun Life Hong Kong Limited
    Property(S): USERNAME = Sun Life
    Property(S): DialogTitleSetup = Setup
    Property(S): DialogTitlePatch = Patch
    Property(S): DialogTitleUpgrade = Upgrade
    Property(S): Text_ArrowLeft = <
    Property(S): Text_ArrowRight =  >
    Property(S): ButtonText_Next = Next
    Property(S): ButtonText_Next_Hot = &Next
    Property(S): ButtonText_Cancel = Cancel
    Property(S): ButtonText_Cancel_Hot = &Cancel
    Property(S): ButtonText_Back = Back
    Property(S): ButtonText_Back_Hot = &Back
    Property(S): ButtonText_Finish = Finish
    Property(S): ButtonText_Finish_Hot = &Finish
    Property(S): ButtonText_Update = Update >
    Property(S): ButtonText_Update_Hot = &Update >
    Property(S): ButtonText_Ok = OK
    Property(S): ButtonText_Ok_Hot = &OK
    Property(S): ButtonText_Yes = Yes
    Property(S): ButtonText_Yes_Hot = &Yes
    Property(S): ButtonText_No = No
    Property(S): ButtonText_No_Hot = &No
    Property(S): ButtonText_Abort = Abort
    Property(S): ButtonText_Abort_Hot = &Abort
    Property(S): ButtonText_Ignore = Ignore
    Property(S): ButtonText_Ignore_Hot = &Ignore
    Property(S): ButtonText_Retry = Retry
    Property(S): ButtonText_Retry_Hot = &Retry
    Property(S): ButtonText_Change = Change...
    Property(S): ButtonText_Change_Hot = &Change...
    Property(S): ButtonText_Help = Help
    Property(S): ButtonText_Help_Hot = &Help
    Property(S): ButtonText_Install = Install
    Property(S): ButtonText_Install_Hot = &Install
    Property(S): ButtonText_Exit = Exit
    Property(S): ButtonText_Exit_Hot = &Exit
    Property(S): ButtonText_Remove = Remove
    Property(S): ButtonText_Remove_Hot = &Remove
    Property(S): ButtonText_Space = Space
    Property(S): ButtonText_Space_Hot = &Space
    Property(S): ButtonText_Browse = Browse...
    Property(S): ButtonText_Browse_Hot = Bro&wse...
    Property(S): ButtonText_DiskCost = Disk Cost...
    Property(S): ButtonText_DiskCost_Hot = &Disk Cost...
    Property(S): LabelText_Status = Status
    Property(S): LabelText_SerialNumber = &Serial Number:
    Property(S): LabelText_UserName = &User Name
    Property(S): LabelText_PersonName = Name
    Property(S): LabelText_PersonOrganization = Company
    Property(S): LabelText_InstallTo = Install to
    Property(S): LabelText_Modify = &Modify
    Property(S): LabelText_Repair = Re&pair
    Property(S): LabelText_Remove = &Remove
    Property(S): LabelText_Complete = &Complete
    Property(S): LabelText_Custom = Cu&stom
    Property(S): LabelText_NetworkLocation = &Network location:
    Property(S): LabelText_LookIn = &Look in
    Property(S): LabelText_FolderName = &Folder name
    Property(S): LabelText_FeatureDescription = Feature description
    Property(S): LabelText_CopyFilesFrom = Copy Files from
    Property(S): LabelText_InstallFor = Install this application for
    Property(S): HeadText_AdminWelcome = Welcome to the Install Wizard for
    Property(S): HeadText_InstallWelcome = Welcome to the Install Wizard for
    Property(S): HeadText_WelcomePatch = Welcome to the Patch for
    Property(S): HeadText_SetupWelcome = Welcome to the
    Property(S): HeadText_SetupWelcome2 =  Setup
    Property(S): HeadText_ResumeInstall = Resuming the Install Wizard for
    Property(S): HeadText_SetupInterrupted =  Setup Interrupted
    Property(S): HeadText_LicenseAgreement = License Agreement
    Property(S): HeadText_FeatureSelection = Feature Selection
    Property(S): HeadText_NetworkLocation = Network Location
    Property(S): HeadText_ProgramMaintenance = Program Maintenance
    Property(S): HeadText_DiskSpaceRequirements = Disk Space Requirements
    Property(S): HeadText_FilesInUse = Files in Use
    Property(S): HeadText_DatabaseFolder = Database Folder
    Property(S): HeadText_RegistrationInformation = Registration Information
    Property(S): HeadText_CompletingSetup = Completing the
    Property(S): HeadText_CompletingSetup2 =  Setup
    Property(S): HeadText_InstallingProduct = Installing
    Property(S): HeadText_UninstallProduct = Uninstalling
    Property(S): HeadText_ChangeDestinationFolder = Change Current Destination Folder
    Property(S): HeadText_ReadyInstall = Ready to Install the Program
    Property(S): HeadText_ReadyRepair = Ready to Repair the Program
    Property(S): HeadText_ReadyModify = Ready to Modify the Program
    Property(S): HeadText_RemoveProgram = Remove the Program
    Property(S): HeadText_OutOfDiskSpace = Out of Disk Space
    Property(S): DescText_FilesInUse = Some files that need to be updated are currently in use.
    Property(S): DescText_RegistrationInformation = The following information will personalize your installation.
    Property(S): DescText_ServerImage = Setup will create a server image of
    Property(S): DescText_ServerImage2 =  at a specified network location. To continue, click Next.
    Property(S): DescText_InstallModifyRemove = Setup helps you install, modify or remove
    Property(S): DescText_InstallModifyRemove2 = . To continue, click Next.
    Property(S): DescText_PatchInstall = The Install Wizard will install the Patch for
    Property(S): DescText_PatchInstall2 =  on your computer. To continue, click Update.
    Property(S): DescText_WizardComplete = The Install Wizard will complete the installation of
    Property(S): DescText_WizardComplete2 =  on your computer. To continue, click Next.
    Property(S): DescText_CompleteSuspended = The Install Wizard will complete the suspended installation of
    Property(S): DescText_CompleteSuspended2 =  on your computer. To continue, click Next.
    Property(S): DescText_SuccessfulInstallation = Setup has installed
    Property(S): DescText_SuccessfulInstallation2 =  successfully. Click Finish to exit.
    Property(S): DescText_SuccessfulRemove = Setup has removed
    Property(S): DescText_SuccessfulRemove2 =  successfully. Click Finish to exit.
    Property(S): DescText_SuccessfulRepair = Setup has repaired
    Property(S): DescText_SuccessfulRepair2 =  successfully. Click Finish to exit.
    Property(S): DescText_SuccessfulModify = Setup has modified
    Property(S): DescText_SuccessfulModify2 =  successfully. Click Finish to exit.
    Property(S): DescText_SetupInterrupted = Setup was interrupted before
    Property(S): DescText_SetupInterrupted2 =  could be completely installed.
    Property(S): DescText_PreparingSetup =  Setup is preparing the Install Wizard which will guide you through the program setup process. Please wait.
    Property(S): DescText_FeatureSelection = Select the program features you want installed.
    Property(S): DescText_ProgramFeaturesInstall = The program features you selected are being installed.
    Property(S): DescText_ProgramFeaturesUninstall = The program features you selected are being uninstalled.
    Property(S): DescText_ReadLicense = Please read the following license agreement carefully.
    Property(S): DescText_SpecifyNetworkLocation = Specify a network location for the server image of the product.
    Property(S): DescText_BrowseDestination = Browse to the destination folder.
    Property(S): DescText_ModifyRepairRemove = Repair or remove the program.
    Property(S): DescText_ReadyInstallation = Setup is ready to begin installation.
    Property(S): DescText_ChosenRemove = You have chosen to remove the program from your system.
    Property(S): DescText_DiskSpaceRequirements = The disk space required for the installation of the selected features.
    Property(S): DescText_DiskExceedsAvailable = Disk space required for the installation exceeds available disk space.
    Property(S): Text_ReRunSetup = Your system has not been modified. To complete installation at another time, please run setup again.
    Property(S): Text_FinishExit = Click Finish to exit Setup.
    Property(S): Text_RestoreState = You can either keep any existing installed elements on your system to continue this installation at a later time or you can restore your system to its original state prior to the installation.
    Property(S): Text_RestoreClick = Click Restore or Continue Later to exit Setup.
    Property(S): Text_InstallWait = Please wait while the Install Wizard installs
    Property(S): Text_InstallWait2 = . This may take several minutes.
    Property(S): Text_UninstallWaitText = Please wait while the Install Wizard uninstalls
    Property(S): Text_UninstallWaitText2 = . This may take several minutes.
    Property(S): Text_UninstallWait = Please wait while the Install Wizard uninstalls
    Property(S): Text_UninstallWait2 = . This may take several minutes.
    Property(S): Text_ProgressDone = Progress done
    Property(S): Text_Copyright = WARNING: This program is protected by copyright law and international treaties.
    Property(S): Text_BeginInstallation = Click Install to begin the installation.
    Property(S): Text_ReviewChange = If you want to review or change any of your installation settings, click Back. Click Cancel to exit Setup.
    Property(S): Text_AlterFeatureInstall = Click an icon in the following list to change how a feature is installed.
    Property(S): Text_ConfirmExit = The installation is not yet complete. Are you sure you want to exit?
    Property(S): Text_FeatureSelectionDescription = This feature requires 4 MB on your hard drive.
    Property(S): Text_EnterNetworkLocation = Enter the network location or click Change to browse to a location. Click Install to create a server image of
    Property(S): Text_EnterNetworkLocation2 =  at the specified network location or click Cancel to exit Setup.
    Property(S): Text_SelectDifferentDrive = The highlighted volumes do not have enough disk space available for the currently selected features. You can remove files from the highlighted volumes, choose to install less features onto local drives, or select different
    destination drives.
    Property(S): Text_RepairInstallationErrors = Repair installation errors in the program. This option fixes missing or corrupt files, shortcuts, and registry entries.
    Property(S): Text_RemoveFromComputer = Remove
    Property(S): Text_RemoveFromComputer2 =  from your computer.
    Property(S): Text_UsingFilesRetry = The following applications are using files that need to be updated by this setup. Close these applications and click Retry to continue.
    Property(S): Text_ClickRemove = Click Remove to remove
    Property(S): Text_ClickRemove2 =  from your computer. After removal, this program will no longer be available for use.
    Property(S): Text_ReviewChangeBack = If you want to review or change any settings, click Back.
    Property(S): Text_AllUsers = &Anyone who uses this computer (all users)
    Property(S): Text_OnlyMe = Only for &me ([USERNAME])
    Property(S): Text_NotAcceptTerms = I &do not accept the terms in the license agreement
    Property(S): Text_AcceptTerms = I &accept the terms in the license agreement
    Property(S): Text_RegInfoNameAndOrg = Enter your name and the name of your organization in the fields below.
    Property(S): Text_RegInfoOrg = Enter the name of your organization in the field below.
    Property(S): Upgrade_Confirmation = A lower version of this product has been detected on your system. Would you like to upgrade your existing installation?
    Property(S): AdminMessage = Setup requires user to be in the administrator group in order to continue the installation process. Setup is aborting as the current user is not in the administrator group.
    Property(S): SupportedOSMessage = Installation of this product failed because it is not supported on this operating system. For information on supported configurations, see the product documentation.
    Property(S): ShortCutText = MSXML 6 Service Pack 2 (KB2758696)
    Property(S): DialogTitle = MSXML 6 Service Pack 2 (KB2758696) Setup
    Property(S): ProductName = MSXML 6 Service Pack 2 (KB2758696)
    Property(S): ShortName = MSXML 6 Service Pack 2 (KB2758696)
    Property(S): WrongPackage = This MSXML6 Service Pack 2 (KB2758696) package is not supported on the current processor type.
    Property(S): DialogPatchTitle = MSXML 6 Service Pack 2 (KB2758696) Patch
    Property(S): SystemFolder = C:\Windows\system32\
    Property(S): WdSfpCaMainModId.41646F16_4E6C_4E96_BF1B_772105414B9D = 86F857F6_A743_463D_B2FE_98CB5F727E09
    Property(S): AppGuidRegKey = Wdsfpca_Uninstall_RegKey.86F857F6_A743_463D_B2FE_98CB5F727E09
    Property(S): MsiLogFileLocation = C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0018_SV53749_MSXML6_1.log
    Property(S): PackageCode = {EE6525FC-1729-4E76-A8C1-12C756BA0AD0}
    Property(S): ProductState = 5
    Property(S): ProductToBeRegistered = 1
    Property(S): STPSETUPTHREADID = 1484
    Property(S): STPSETUPPROCESSID = 9540
    Property(S): EXTERNALCONTROL = 1
    Property(S): ADDLOCAL = ALL
    Property(S): SKIPPENDINGREBOOTCHECK = 1
    Property(S): APPGUID = {FFFA78A7-BD51-4255-8470-C4D4A85B49F5}
    Property(S): REBOOT = ReallySuppress
    Property(S): CURRENTDIRECTORY = C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap
    Property(S): CLIENTUILEVEL = 3
    Property(S): MSICLIENTUSESEXTERNALUI = 1
    Property(S): CLIENTPROCESSID = 9540
    Property(S): MsiRestartManagerSessionKey = 2bacf19a1da7c4438b188852d7df058c
    Property(S): PRODUCTLANGUAGE = 1033
    Property(S): VersionDatabase = 300
    Property(S): VersionMsi = 4.05
    Property(S): WindowsBuild = 6002
    Property(S): ServicePackLevel = 2
    Property(S): ServicePackLevelMinor = 0
    Property(S): MsiNTProductType = 3
    Property(S): WindowsFolder = C:\Windows\
    Property(S): WindowsVolume = C:\
    Property(S): System16Folder = C:\Windows\system\
    Property(S): RemoteAdminTS = 1
    Property(S): TempFolder = C:\Users\ADMINI~1\AppData\Local\Temp\
    Property(S): CommonFilesFolder = C:\Program Files\Common Files\
    Property(S): AppDataFolder = C:\Users\Administrator\AppData\Roaming\
    Property(S): FavoritesFolder = C:\Users\Administrator\Favorites\
    Property(S): NetHoodFolder = C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
    Property(S): PersonalFolder = C:\Users\Administrator\Documents\
    Property(S): PrintHoodFolder = C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
    Property(S): RecentFolder = C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Recent\
    Property(S): SendToFolder = C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\SendTo\
    Property(S): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
    Property(S): CommonAppDataFolder = C:\ProgramData\
    Property(S): LocalAppDataFolder = C:\Users\Administrator\AppData\Local\
    Property(S): MyPicturesFolder = C:\Users\Administrator\Pictures\
    Property(S): AdminToolsFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
    Property(S): StartupFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\
    Property(S): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
    Property(S): StartMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\
    Property(S): FontsFolder = C:\Windows\Fonts\
    Property(S): GPTSupport = 1
    Property(S): OLEAdvtSupport = 1
    Property(S): ShellAdvtSupport = 1
    Property(S): Intel = 6
    Property(S): PhysicalMemory = 2047
    Property(S): VirtualMemory = 2390
    Property(S): AdminUser = 1
    Property(S): LogonUser = Administrator
    Property(S): UserSID = S-1-5-21-752955860-2970973076-2057269693-500
    Property(S): UserLanguageID = 1033
    Property(S): ComputerName = SV53749
    Property(S): SystemLanguageID = 1033
    Property(S): ScreenX = 1024
    Property(S): ScreenY = 768
    Property(S): CaptionHeight = 19
    Property(S): BorderTop = 1
    Property(S): BorderSide = 1
    Property(S): TextHeight = 16
    Property(S): TextInternalLeading = 3
    Property(S): ColorBits = 32
    Property(S): TTCSupport = 1
    Property(S): Time = 14:02:33
    Property(S): Date = 2/23/2015
    Property(S): MsiNetAssemblySupport = 2.0.50727.4016
    Property(S): MsiWin32AssemblySupport = 6.0.6001.18000
    Property(S): RedirectedDllSupport = 2
    Property(S): MsiRunningElevated = 1
    Property(S): Privileged = 1
    Property(S): DATABASE = C:\WINDOWS\Installer\23e28752.msi
    Property(S): OriginalDatabase = C:\WINDOWS\Installer\23e28752.msi
    Property(S): UILevel = 2
    Property(S): Preselected = 1
    Property(S): ACTION = INSTALL
    MSI (s) (B8:64) [14:02:33:948]: Note: 1: 1729
    MSI (s) (B8:64) [14:02:33:948]: Product: MSXML 6 Service Pack 2 (KB2758696) -- Configuration failed.
    MSI (s) (B8:64) [14:02:33:949]: Windows Installer reconfigured the product. Product Name: MSXML 6 Service Pack 2 (KB2758696). Product Version: 6.20.2016.0. Product Language: 1033. Reconfiguration success or error status: 1603.
    MSI (s) (B8:64) [14:02:33:951]: Deferring clean up of packages/files, if any exist
    MSI (s) (B8:64) [14:02:33:951]: MainEngineThread is returning 1603
    MSI (s) (B8:9C) [14:02:33:952]: RESTART MANAGER: Session closed.
    MSI (s) (B8:9C) [14:02:33:952]: No System Restore sequence number for this installation.
    === Logging stopped: 2/23/2015  14:02:33 ===
    MSI (s) (B8:9C) [14:02:33:952]: User policy value 'DisableRollback' is 0
    MSI (s) (B8:9C) [14:02:33:952]: Machine policy value 'DisableRollback' is 0
    MSI (s) (B8:9C) [14:02:33:952]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (B8:9C) [14:02:33:953]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (B8:9C) [14:02:33:953]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (B8:9C) [14:02:33:954]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (B8:9C) [14:02:33:954]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (B8:9C) [14:02:33:954]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (B8:9C) [14:02:33:954]: Restoring environment variables
    MSI (s) (B8:9C) [14:02:33:955]: Destroying RemoteAPI object.
    MSI (s) (B8:B0) [14:02:33:955]: Custom Action Manager thread ending.
    MSI (c) (44:50) [14:02:33:957]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (44:50) [14:02:33:959]: MainEngineThread is returning 1603
    === Verbose logging stopped: 2/23/2015  14:02:33 ===
    MSXML6 problem

  • MS SQL 2005 clustered database instance.

    Short Text 
    MS SQL cluster database instance - ONLY! 
    Long Text 
    Hi,
    If possible could you please confirm that our planned landscape
    migration is supported by SAP.
    At present our PRD SAP system is a standalone instance that consists of
    the database & central instance running on the same "HOST".
    <u>Current SAP PRD version:</u>
    ERP 2004 ECC 5.0 32 bit
    MS SQL 2000 32 bit
    both running on same host with OS Windows 2003 32 bit
    We plan to upgrade/migrate our PRD SAP system to new 64 bit hardware
    AND to move to a "Distributed" landscape installation i.e. database
    instance & central instance installed on different HOSTS. Also, the
    database instance WILL be clustered but the central instance will NOT
    be clustered. There are also multiple NON-SAP MS SQL databases that
    will run in the same cluster as the PRD SAP database instance.
    <u>SAP PRD version after migration:</u>
    SAP ERP 2004 ECC 5.0 64bit (running on X86_64 AMD64 hardware) on HOST'X'
    MS SQL 2005 64 bit (running on IA64 hardware) on clustered HOST'Y'
    Both running on Windows 2003 64 bit
    <u>My questions are:</u>
    1) Does SAP support a clustered MS SQL 2005 database instance that is
    running on a clustered HOST along with NON-SAP MS SQL databases?
    2)During the migration our PRD SAP MS SQL database will be upgraded
    from MS SQL 2000 32 bit to MS SQL 2005 64 bit IA64, is this also
    supported in a clustered istallation (database instance ONLY)?
    3) The central PRD SAP instance will be running on x86_64 AMD64
    hardware & the database instance will be running on 64 bit IA64
    hardware. Is this configuration supported?
    Thanking you inadvance.

    Hi Greg,
    Have you figured out the answer? We are trying do the exactly the same thing -- Move our SAP WAS 6.40 clustered central instance to a 64-bit hardware/SQL 2005/Clustered system. And this system has several non-SAP database on there. The biggest concern we have is whether SAP support this architecture. I posted a message here last year and several experts like Clas Hortien, N. P. C, in this form suggest NOT go to this architecture because SAP will not support it. One example, is that SAP/SQL requires server collation setting to SQL_Latin1_General_CP850_BIN2 and other databases may work on different collations.
    Migrate SAP SQL Server database to co-exist with others
    Anyway, if you or anyone in this form have some more information please share here.
    Thanks,
    Yujun Ran

  • How to create linked server in sql 2005 to access free table visual foxpro 9 step by step

    Hi All, I want to connect to dbf file visual foxpro by using linked server in sql 2005, but i can't do, i hope getting best anwser from every body in forum.
    Thanks all.

    Hi doanpq,
    Please download and install OLE DB Provider for Visual FoxPro 9.0, which exposes OLE DB interfaces that you can use to access Visual FoxPro databases and tables from other programming languages and applications. Please see:
    http://www.microsoft.com/en-us/download/details.aspx?id=14839
    Then, please follow up the following article to create a linked server:
    Creating Linked Servers:
    http://technet.microsoft.com/en-us/library/ff772782(v=sql.105).aspx
    For more information, you can also take a look at the following article, especially Dave K's comment:
    http://blog.dbase.integralwebsolutions.co.za/2008/10/accessing-your-dbf-tables-via-linked.html
    Elvis Long
    TechNet Community Support

  • Not able to connect to MS SQL 2005 Evaluation version

    Hi,
    I have installed MS SQL 2005 Evaluation version(downloaded from microsoft site) on my win2k3 Enterprise Edition I am writing a java application that connects to MS SQL 2005.
    I have downloaded the MS SQL 2005 JDBC driver. And i unjarred the
    I have unjarred the sqljdbc.jar file and kept the com folder and my .java file in the same folder.
    When i am trying to connect, I am getting the following error:
    com.microsoft.sqlserver.jdbc.SQLServerException: Failed Logon:com.microsoft.sqlserver.jdbc.SQLServerException: TCP/IP connection failed to host:155.35.54.160 java.net.ConnectException: Connection refused:connect
    My code look like this:
    try {
    Class.forName ("com.microsoft.sqlserver.jdbc.SQLServerDriver");
    String fs = File.separator;
    String conn_str = "jdbc:sqlserver://155.35.54.160:1433;user=sa;password=SA;databaseName=asdb";
    conn = DriverManager.getConnection ( conn_str );
    catch (Exception e) {System.out.println(e); }
    Please reply.
    Thanks and Regards,
    Sudheer Gajula

    First aid check list for "connection refused":
    - Check host name in connect string.
    - Check port number in connect string.
    - Try numeric IP address of server host in connect string, in case name server is hosed.
    - Are there any firewalls between client and server blocking the port.
    - Check that the db server is running.
    - Check that the db server is listening to the port. On the server, try: "telnet localhost the-port-number". Or "netstat -an", there should be a listening entry for the port. You need to configure the database to accept TCP connections; read the documentation or google.
    - Try "telnet server-host-name the-port-number" from the client, to see if firewalls are blocking it.
    - If "telnet" fails: try telnet with the numeric ip address.
    - If "telnet" fails: does it fail immediately or after an obvious timeout? How long is the timeout?
    - Does the server respond to "ping serverhost" or "telnet serverhost" or "ssh serverhost"?

Maybe you are looking for