Failing to install SQL 2005 on server.

I am failing to install SQL 2005 on the server with message below:-
TITLE: Microsoft SQL Server 2005 Setup
The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=MicrosoftSQLServer&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=29503&EvtType=sqlsetuplib%5cservice.cpp%40Do_sqlScript%40sqls%3a%3aService%3a%3aStart%40x42b
BUTTONS:
&Retry
Cancel
It was removed after it started developing problems. We tried to go to MS SQL site buts its not opening the site. I thought maybe you could help although it is a SQL error. For some time we are failing to run SAP B1 because of this.
Thank you.

Hi,
Check the SQL Services go to start->AllPrograms->Microsost
SQL Server 2005->ConfigurationTools->SQL Server Configuration Manager
Pl check The following Services is Running State
1.SQL Server Browser
2.SQLServer(MSSQLSERVER)
Regards
JambuLingam.P

Similar Messages

Unable to install SQL 2005 Service Pack 3 (Unable to install Windows Installer MSI file)

I'm unable to install SQL 2005 Service Pack 3. This results in the following error message: Unable to install Windows Installer MSI file.
Could someone please help me. Thanks in advance!
=== Verbose logging started: 3-4-2009 9:33:00 Build type: SHIP UNICODE 4.05.6001.00 Calling process: d:\5ddfa356349ddf2e676c336d95c5\hotfix.exe ===
MSI (c) (E0:88) [09:33:00:404]: Resetting cached policy values
MSI (c) (E0:88) [09:33:00:404]: Machine policy value 'Debug' is 0
MSI (c) (E0:88) [09:33:00:404]: ******* RunEngine:
           ******* Product: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
           ******* Action:
           ******* CommandLine: **********
MSI (c) (E0:88) [09:33:00:404]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (E0:88) [09:33:00:404]: Grabbed execution mutex.
MSI (c) (E0:88) [09:33:00:419]: Cloaking enabled.
MSI (c) (E0:88) [09:33:00:419]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (E0:88) [09:33:00:419]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (28:28) [09:33:01:747]: Running installation inside multi-package transaction C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
MSI (s) (28:28) [09:33:01:747]: Grabbed execution mutex.
MSI (s) (28:CC) [09:33:02:029]: Resetting cached policy values
MSI (s) (28:CC) [09:33:02:029]: Machine policy value 'Debug' is 0
MSI (s) (28:CC) [09:33:02:029]: ******* RunEngine:
           ******* Product: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
           ******* Action:
           ******* CommandLine: **********
MSI (s) (28:CC) [09:33:02:685]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (28:CC) [09:33:03:450]: File will have security applied from OpCode.
MSI (s) (28:CC) [09:33:03:841]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi' against software restriction policy
MSI (s) (28:CC) [09:33:03:841]: SOFTWARE RESTRICTION POLICY: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi has a digital signature
MSI (s) (28:CC) [09:33:04:841]: SOFTWARE RESTRICTION POLICY: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (28:CC) [09:33:04:888]: End dialog not enabled
MSI (s) (28:CC) [09:33:04:888]: Original package ==> C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
MSI (s) (28:CC) [09:33:04:888]: Package we're running from ==> C:\WINDOWS\Installer\3d3a713.msi
MSI (s) (28:CC) [09:33:05:497]: APPCOMPAT: looking for appcompat database entry with ProductCode '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'.
MSI (s) (28:CC) [09:33:05:497]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (28:CC) [09:33:05:685]: MSCOREE not loaded loading copy from system32
MSI (s) (28:CC) [09:33:05:825]: Note: 1: 2203 2: C:\WINDOWS\Installer\2f1994e.msi 3: -2147287038
MSI (s) (28:CC) [09:33:05:825]: Opening existing patch 'C:\WINDOWS\Installer\e6ba0.msp'.
MSI (s) (28:CC) [09:33:05:825]: Note: 1: 2203 2: C:\WINDOWS\Installer\e6ba0.msp 3: -2147287038
MSI (s) (28:CC) [09:33:05:825]: Couldn't find local patch 'C:\WINDOWS\Installer\e6ba0.msp'. Looking for it at its source.
MSI (s) (28:CC) [09:33:05:825]: Resolving Patch source.
MSI (s) (28:CC) [09:33:05:825]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (28:CC) [09:33:05:825]: User policy value 'DisableMedia' is 0
MSI (s) (28:CC) [09:33:05:825]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Looking for sourcelist for product {EE92F683-5F5C-4970-BB0B-9AC591B60268}
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Adding {EE92F683-5F5C-4970-BB0B-9AC591B60268}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Now checking product {EE92F683-5F5C-4970-BB0B-9AC591B60268}
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Media is enabled for product.
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Trying source \\NF04\d$\3db7739bf5c1bb9c50076c418420\HotFixSqlSupport\Files\.
MSI (s) (28:CC) [09:33:06:607]: Note: 1: 2203 2: \\NF04\d$\3db7739bf5c1bb9c50076c418420\HotFixSqlSupport\Files\SqlSupport.msp 3: -2147287037
MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (28:CC) [09:33:06:607]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msp
MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Processing net source list.
MSI (s) (28:CC) [09:33:06:607]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msp
MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Processing media source list.
MSI (s) (28:CC) [09:33:07:654]: SOURCEMGMT: Resolved source to: 'SqlSupport.msp'
MSI (s) (28:CC) [09:33:37:732]: Note: 1: 1314 2: SqlSupport.msp
MSI (s) (28:CC) [09:33:37:732]: Unable to create a temp copy of patch 'SqlSupport.msp'.
MSI (s) (28:CC) [09:33:37:732]: Searching provided command line patches for patch code {EE92F683-5F5C-4970-BB0B-9AC591B60268}
MSI (s) (28:CC) [09:33:37:763]: Note: 1: 1708
MSI (s) (28:CC) [09:33:37:763]: Product: Microsoft SQL Server Setup Support Files (English) -- Installation failed.
MSI (s) (28:CC) [09:33:37:763]: Windows Installer installed the product. Product Name: Microsoft SQL Server Setup Support Files (English). Product Version: 9.00.4035.00. Product Language: 1033. Installation success or error status: 1635.
MSI (s) (28:CC) [09:33:37:779]: MainEngineThread is returning 1635
MSI (s) (28:28) [09:33:37:888]: No System Restore sequence number for this installation.
This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
MSI (s) (28:28) [09:33:37:888]: User policy value 'DisableRollback' is 0
MSI (s) (28:28) [09:33:37:888]: Machine policy value 'DisableRollback' is 0
MSI (s) (28:28) [09:33:37:888]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (28:28) [09:33:37:904]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (28:28) [09:33:37:919]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (28:28) [09:33:37:919]: Restoring environment variables
MSI (c) (E0:88) [09:33:37:935]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (E0:88) [09:33:37:935]: MainEngineThread is returning 1635
=== Verbose logging stopped: 3-4-2009 9:33:37 ===

This post should definitely help you
http://blogs.msdn.com/sqlserverfaq/archive/2009/01/30/part-1-sql-server-2005-patch-fails-to-install-with-an-error-unable-to-install-windows-installer-msp-file.aspx?CommentPosted=true
Feroz
Mark as Answer if it helps. This posting is provided "AS IS" with no warranties and confers no rights.

Error installing SQL 2005 SP4

Hi Guys,
When i am installing SQL 2005 SP4 in windows 2008r2 cluster i get following error message "your account information could not be verified. Press OK to return to Authentication Mode screen to determine reason for failure.For setup to verify your
credentials the services must be startable,connectable,and you must be a SQL Server Administrator"
I am a local admin on both the box,sql service account is also a domain a/c and has admin privileges also i have added my account as well as sql service account as sysadmin in sql server instance.I had installed SQL 2005 earlier using same accounts with
no issue.
Can anyone point out why the error.It doesn't make sense to me.
Regards,
Viv

Hello,
Could you try installing the service pack on the passive node using the /passive switch? For example:
SQLServer2005SP4-KB955706-x86-ENU.exe /passive
If the above is successful, failover and do the same on the other node.
Are you logged in as a Windows account that has the sysadmin role on SQL Server?
Could you verify the authentication information provided to SQL Server setup is correct?
I have not installed a SQL Server 2005 in more than 5 years, I am sorry if I suggest things that not make sense to you.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL 2005 Linked server to Oracle append

Hi Oracle Exprets,
i am using an SQl 2005 linked server too pull data from specific table in Oracle data base.
the thing is i have to pull data daily and append this data to the exsisting table.
here is my code :
EXEC sp_tables_ex @table_server ='LINKED_ORA',@table_schema='Myschema'
INSERT INTO dbo.ARS20091
SELECT * FROM OPENQUERY(LINKED_ORA,
'SELECT
TROUBLEID,
CREATE_DATE,
DATE ''1970-01-01'' + CREATE_DATE / 24 / 60 / 60
CREATEDATE
FROM CLIENT_TROUBLE
WHERE CREATE_DATE between ''1230768001'' AND ''1239043005''');
GO
this code works but i have to change the date daily and do a complete insert in a new table.
Is there a way to append data daily ?
thanks

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..

The unattended installation failed while installing SQL Server 2008 R2 ????

Hi gurus,
I got an error while installing SQL Server 2008 R2 in Windows 2008 R2 standard 64 bit operating system.
LOG file*
Customized installation of SQL Server 2008R2 for SAP *
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlWriter_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Full-Text Search
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Client Tools Connectivity
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Client Tools SDK
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Client Tools Backwards Compatibility
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Business Intelligence Development Studio
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SystemConfigurationCheck_Report.htm
1/16/2012 10:13:34 PM
Message Box "Installation failed"
The unattended installation failed.
Installation Step: The unattended installation failed.
Return Code:       -2068052377
Log File:          C:\Windows\SQL4SAP.log
Check the log file above.
See SAP note 1144459 for known issues.
Result: vbOK
Registry settings (2/2):
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
WRITE(REG_DWORD): 4
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{2b9034f3-b661-4d36-a5ef-60ab5a711ace}
WRITE(REG_DWORD): 4
1/16/2012 10:37:32 PM
Quit script with return code 1
Please help me out with this issue.
REGARDS,
Raj

Hello Raj,
MS SQL DB installation specific steps for SAP system is clearly documented in SAP Installation guide. Please download from SMP, read it carefully and install as mentioned in the guide.
Hope it helps.
Thanks,
Siva Kumar

Upgrade sql 2000 win xp to sql 2005 win2003 server

Hi,
We had installed sap b1 2005b on winxp and database as sql 2000.
Now ,we want to install sap b1 2007b on win 2003 and database as sql 2005.
Can the sql 2000 winxp database backup be restored on sql 2005 win2003 database.
Since both the OS are different can the backup be restored .
Pls let me know about the same.
Regards,
Rajeev

Hi Rajeev
step 1) Install SQL Server 2005.
step 2) Install [SAP Business One|http://www.brio.co.in/products/sap-business-one/] 2005
step 3) Get the new license key for your windows 2003 server if you dont have
step 4) Create a company with same name and database name this will create a company record in SBOCommon database
step 5) Take the backup of the database of the company in MS SQL 2000.
step 6) Restore it on your windows 2003 and sql server 2005 system
step 7) Download an upgrade for 2005 to 2007 from software download center
step 8) Run the upgrade exe
THATS IT, YOU ARE ON YOUR NEW SYSTEM.
Regards
[Abdul Muneem|http://www.brio.co.in]
Edited by: Muneem Abdul on Nov 22, 2010 12:22 PM

Oralce EPM Fails to install Weblogic on Windows Server 2008 R2 x64

I've run the installer on Windows Server 2008 R2 x64 and it fails to install Weblogic. I don't have MIDDLEWARE_HOME/oracle_common. Config tool log says missing jars. When I go back to install and choose products individually, Weblogic Server is gray. When I click on Weblogic Server, the message at the bottom says can not be installed.
I have checked that I have extracted the following assemblies:
Oracle Hyperion Enterprise Performance Management System Installer, Fusion Edition Release 11.1.2.0.0
Hyperion Enterprise Performance Management System Foundation Services Release 11.1.2.0.0 - Parts 1 - 4
Oracle Hyperion Enterprise Performance Management System Additional Content Release 11.1.2.0.0
I have run this same set of files on another server and Weblogic was installed. Am I missing something?

I am not sure if it is your problem but I don't think R2 is officially supported, I did have problems with it when I first installed 11.1.2 so I installed with R1 SP2.
Cheers
John
http://john-goodwin.blogspot.com/

SCOM 2012 SP1 is failing to install - SQL not compatible

I'm getting an error when installing SCOM 2012 SP1 stating the SQL is not supported. I have seen a few posts on the forum about this error message but so far none of the resolutions resolved my issue.
Using named instance on port 2433. Entering SQL\instance and port 2433 yields same message as seen in another post:
"The installed version of SQL server is not supported. Verify that the computer and installed version of SQL Server meet the minimum requirements for installation. Please see the Supported Configurations document for further information."
I noticed I get this in my OpsMgrSetupWizard.log
[15:03:28]: Error: :StackTrace:   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObjectSearcher.Initialize()
   at System.Management.ManagementObjectSearcher.Get()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.GetRemoteOSVersion(String remoteComputer)
[15:03:28]: Debug: :IsSQLOnAValidComputer: remote OS version string was null or empty.
Notice the last line - IsSQLOnAValidComputer is null/empty. The solutions I found are to open the ports between these servers but the SQL server and SCOM server are on the same network - no firewall between them. The registry key for domain firewall
policy to 'EnableFirewall' is 0. The firewall service is disabled on both machines.
I am running the installation as a domain service account - for the DAA. It has local admin on the SQL and SCOM server. It has sysadmin DB access to the instance.
SCOM Server:
Server 2008 R2 Standard SP1
SQL Server:
Server 2008 R2 Enterprise SP1 | SQL 2012 RM 64-bit version 11.0.2100.60
Any help is greatly appreciated.

Glad to hear the issue has been resolved. Thanks for the update.
Niki Han
TechNet Community Support

How to Install SQL 2005 with command MS SQL 2005.

Hello All,
Where can I get the guide for installaling ECC 6.0+MS SQL 2005/2008 from command prompt.
I checked the standard work guides at market place but no hint found for command line installation.
Please help me.
Thanks,
Anu

Wrong subject line

Fail to install web-to-go server...

I have try to install web-to-go server
on a windowsNT4.0(SP3) but failed.
When i read the install.log for reason, i
found that there is an error when creating object using Advanced Replication.
My database built on oracle805 and already support Advanced Replication.
So please suggest why? Thanks all...
null

Hi All,
I tried to run the report server in standalone, it can work.
But when change to IN_PROGRESS_SERVER. It can't.
I check the rwserver.trc file, the error message show as :
2007/8/29 0:20:52:468] Debug 50103 (EngineManager:spawnEngine): Started engine with Environment REPORTS_TMP=c:\temp
[2007/8/29 0:20:52:468] Info 56021 (EngineManager:spawnEngine): Engine rwURLEng-0 has been launched
[2007/8/29 0:20:52:468] State 56004 (EngineInfo:setState): Engine rwURLEng-0 state is: Initial
[2007/8/29 0:20:52:468] Debug 50103 (JobStore:writePersistFile): Purge persistent file
[2007/8/29 0:20:52:468] Warning 50103 (JobStore.writePersistFile): REP-50139: Cannot delete file C:\oracle\frs10\reports\server\frs10.dat
[2007/8/29 0:20:52:468] Exception 50139 (): Cannot delete file C:\oracle\frs10\reports\server\frs10.dat
oracle.reports.RWException: IDL:oracle/reports/RWException:1.0
     at oracle.reports.utility.Utility.newRWException(Utility.java:756)
     at oracle.reports.server.JobStore.writePersistFile(JobStore.java:424)
     at oracle.reports.server.RWServer.startServer(RWServer.java:948)
     at oracle.reports.server.RWServer.run(RWServer.java:287)
     at java.lang.Thread.run(Thread.java:534)
[2007/8/29 0:20:52:468] Exception 50139 (): Cannot delete file C:\oracle\frs10\reports\server\frs10.dat
oracle.reports.RWException: IDL:oracle/reports/RWException:1.0
     at oracle.reports.utility.Utility.newRWException(Utility.java:756)
     at oracle.reports.server.JobStore.writePersistFile(JobStore.java:424)
     at oracle.reports.server.RWServer.startServer(RWServer.java:948)
     at oracle.reports.server.RWServer.run(RWServer.java:287)
     at java.lang.Thread.run(Thread.java:534)
I didn't specify persist file in report.conf file, anybody have any idea ?
Thanks.
Best Regards,
Klnghau

Installing sql 2005 64 bits

Hello,
I download the sql 2005 from www.service.sap.com/sbo-swcenter but how can I do to install the sql on 64 bits? Do I need to run a special command?
Thanks in advance for your help
Graciella

Hi Graciella,
Have you read through the documents came along with the download?
Thanks,
Gordon

Silent Install fails, normal install works. Application Server 10.1.2

Hi All,
I'm setting up an automated install of Application Server 10g 10.1.2.0.2 (Forms and Reports). When I install it silently using a silent install file, the install completes succuessfully but it isn't actually fully functional, and it isn't recognized by OEM Grid Control.
When I install it normally, using the gui, it works fine and is recognized by the OEM Grid Crontrol.
I'm running on Solaris 10 zones, and I used the recording feature for Silent installations to generate a silent file, but that didn't help either.
Any advice? Tips? Information and your own personal experience would be highly appreciated.
Thanks

I realized that I was missing a few parameteres that I found at this site:
http://download.oracle.com/docs/cd/B32110_01/install.1013/b32411/basic_install.htm#BABCHEJI

DI API Deadlocks in SQL 2005 database server

Hello All,
I have an Issue, which is coming on large databases ( > 50GB) and number of users > 20.
I have read the following notes
1269591, 1489753, 1318311, 1231444 , 1344641 , 1316554
also contributed in the following thread:
Workaround:
Each SAP B1 Client is using an addon, which do a WM (Warehouse management) based on WHSE Journal. Until upgraded to 2007 version, this was working fine, no issue came up only system was slow.
Process with pseudo code like this
'incoming cases - when an item is entering into the warehouse
Add Logistics documents (action success = true)
- start transaction
- check Warehouse journal
- record changes done by this document (based on oinm) into (UDT)
- finish transaction
'outgoing cases - where an item is carried out from the warehouse - create a self pick list example: sales order:
start transaction
- loop on every rows of the sales order
- read ordered quantity
- look for place where it is stored,
- if found make a reservation in (UDT)
- add position to self created pick list (UDT)
finish transaction
'release from warehouse
start transaction
- look for pick list position (UDT)
- reduce stock value (UDT)
- update pick list with packed quantity (UTD)
- create delivery note
finish transaction
Depending from activity the users receive various error messages like Could not commit transaction / Deadlock ... / -2038 Internal error xxxx messages, when trying to access to UDT-s or any marketing documents, and the system is frozen. I go to activity monitor, and check and tell them which client is causing dead locks, they log off ,and can continue work or if the process runs to timeout, it sends the error message to SAP B1 Client.
Also we have an addon which reads (only reads) data from database from OITM / OITW / and one of these UDT above. (queries against stock value from UDT). here we receive 2 type of error messages
- Deadlock
- Timeout
I know these messages are coming from: other computers /Users are issueing documents in transaction.
Any ideas to resolve this issue / has anybody happened this issue ?
Every ideas, comments are welcome.
The system is b1 2007 SP 01 PL 10. Average document position between 50-100.
Solution Architect team? Any workaround?
Regards
János

HI Janos,
I also faced little bit same type of Issue in one of the project.
Please look
Link: [Large data processing Issue | SAP Hanging Problem using Transactions;
After applying this my issue was resolved.
regards:
Sandy
Edited by: Sandeep Saini | Roorkee | India on Sep 6, 2010 7:16 PM

SQL 2005 backup

Hi,
I'm using Small Business Server 2003.
I've installed SQL 2005 Database Server for ERP.
I need to take the backup of the both SMB 2003 and SQL Database.
If I take Full back from SMB 2003 will this also take backup of my SQL 2005. Or do I need to take SQL backup separately.
Sathish

If I take Full back from SMB 2003 will this also take backup of my SQL 2005.
Not the databases, they are permanent in access by SQL Server and therefore you can't perform file backups on them You have to use the backup Feature of SQL Server instead, see:
Introduction to Backup and Restore Strategies in SQL Server
Back Up and Restore of SQL Server Databases
Olaf Helper
[ Blog] [ Xing] [ MVP]

SQL Server 2005 SP2 Failed to install the update

I just purchased a Dell PC and during the start up one of the updates that tried to install was SQL Server 2005. I tried turning off my Anti Virus program and the install failed again. Everything I've read about this problem is too technical for me. Is
there a simple way to fix this problem?

I just purchased a Dell PC and during the start up one of the updates that tried to install was SQL Server 2005. I tried turning off my Anti Virus program and the install failed again. Everything I've read about this problem is too technical for
me. Is there a simple way to fix this problem?
I am curious which Windows update installs SQL server 2005. Were you installing any program which installed SQL 2005 as part of it ?
Anyways you can share log file as asked by Alberto. Please also give more details whether SQL server was installed by you or machine or whether it was SQL 2005 update.
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 Articles

Failing to install SQL 2005 on server.

Similar Messages

Maybe you are looking for