BPC-MS 7.5 SP5 Multi-Server Installation with SQL 2008

Hi Experts,
I have problem with multiserver installation. Even though installation user is SQL and OLAP administrator, installation lacks of creating Apshell OLAP database. OLAP server is using default port and we confirmed user can access this server. At the beginning installation user also could not create SQL database but we took Apshel.db9 and use Advanced Settings in installation and now installation process creates SQL Database but not OLAP database.
Actually our problem is not with creating Apshell OLAP Database we can import it from somewhere but this is the beginning of our OLAP connection problems. I do not know how many times we checked installation document and we installed Shared Features, ADO.net components etc..
Please see error screenshot [here|http://www.navis.com.tr/BPCMultiserverInstall.png]
Any ideas?
Thanks in advance,
Ergin Ozturk

Hi There
You need to ensure that the SQL Server has the correct protocols enabled, as per Bruno's post, you need to ensure that TCP / IP is enabled.
Additionally, you may want to ensure that the SQL Server is able to allow remote connections.
Please find below a link to a How To Guide on allowing remote connections to SQL Server
[http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx]
Hope this helps
Kind Regards
Daniel

Similar Messages

Setting up Multi server environment in Sql Server 2012 - Enlist Failed Error

I am trying to Configure the Master target server / Multi server environment in Sql Server 2012.
I changed :
- `MSXENCryptChannnelOptions`-->Changed from 2 to 0
- `AllowDownloadedJobsToMatchProxyName` - changed from 0 to 1 on the target
When I run the wizard I am getting below error
>MSX Enlist failed for Job Server 'MasterServerName'
>The enlist operation Failed(Reason:SQL Server Agent Error: Unable to connect to MSX 'MasterServerName'(Microsoft Sql Server, Error : 22026)
They both servers SQL Agents are running on the same windows service account.
Any Suggestions on how to fix this?
**Adding the Log:**
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'Test3' is running (Success)
The service 'SQLSERVERAGENT' is running.
- Ensure the agent startup account for 'Test4' has rights to login as a target server (Success)
Checking to see if the startup account for 'Test4' already exists.
Login exists on server.
Checking to see if login has rights to msdb.
Login has rights to msdb.
Checking to see if user is a member of the TargetServersRole.
User is a member of the TargetServersRole.
- Enlist 'Test4' into 'Test3' (Error)
Enlisting target server 'Test4' with master server 'Test3'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'Test4'. (Microsoft.SqlServer.Smo)
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect to MSX 'TEST3'.) (Microsoft SQL Server, Error: 22026)

hi SmilingLily,
you can try to run the SQL Agent under a domain account.

Problem in SAP Server installation with Oracle DB

Hi,
We are working in SAP Server installation with Oracle DB. After some steps in our Process it is asking for a DVD called RDBMS DVD CLIENT ORACLE. We are trying to download in Service market place. But we could not get the Correct DVD for the installation. Please help in this issue. Where do we get the DVD to continue our SAP Server installation.
We are struck with our SAP Server installation. Please consider this issue as very urgent.
thanks in advance.
Regards,
Mohankumar.G

Hello Mohan,
Please specify which installation your are doing otherwise it is difficult to provide you
the correct path.
For eg if you are doing NW04's installation then path will be
downloads->entry by application group->Installations and Upgrades->SAP NetWeaver-> SAP NETWEAVER-> SAP NETWEAVER 2004S->according to OS/DB (there is oracle client cd)select the cd.
hope it helps..
Regards,
Jafer

Security issue in SQL Server replication in SQL 2008 Express edition

Hi,
I am trying to do merge replication through web sync in SQL server 2008 express edition. i tried the merge replication using RMO with C# code but no luck. i am getting the security related error.
my Publisher and distribution are on SQL server 2008 R2 Standard edition. machine name "Printserver",
I created subscription on SQL server 2008 express edition.
I hosted the web service for merge syncronization on another machine named "ANUJVMWIN7".
I installed SSL cerificate on all the machine (server, hosted server and subscriber machine.)
here is the error description.
The upload message to be sent to Publisher ‘PRINTSERVER’ is being generated
The merge process is using Exchange ID ’0B23EBE2-D502-4D92-A9A1-88B8F738CFFC’ for this web synchronization session.
A security error occurred
A security error occurred
The Merge Agent could not connect to the URL ‘https://ANUJVMWIN7.prospecta.in/WebSyncTest/replisapi.dll’ during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable.
The same process i tested with the SQL server 2008 standard edition and all the things are working fine. i could able to merge the databases but no luck with SQL 2008 express edition.
Please help.
Thanks
Anuj Sharma
Thanks Anuj Sharma Software Engineer

Hi Brandon,
I am not using self signed certificate. I installed SSL certificate provided by RapidSSL CA. This certificate is installed on my publisher machine ("Printserver"),
web hosting machine ("ANUJVMWIN7") and my subscriber machine as well.
Here are the certificate details which i installed on each machine.
Thanks
Anuj Sharma
Thanks Anuj Sharma Software Engineer

Secondry Server Installation Failing - SQL Issue

Hi Guys,
Trying to install SCCM 2012 R2 Secondary Server and getting below error everytime.... FYI... Both the Server Computer Names are sysadmin on Either of the SQL servers and also added to local Admin on both Primary and Secondary Server.
Also, user account which I'm using for installation is the local Admin on Both the server. Please Help....
Here :
ABCD.msdn.net : Server where we want to install SCCM 2012 Secondary
PQRS.msdn.net : Primary Server from where we are initiating the Secondary Server installation
~~===================== << Starting Configuration Manager 2012 Setup >> ===================== $$<Configuration Manager Setup><09-24-2014 17:10:19.332+240><thread=5948 (0x173C)>
INFO: ConfigMgr2012 Setup was started by NT AUTHORITY\SYSTEM. $$<Configuration Manager Setup><09-24-2014 17:10:19.332+240><thread=5948 (0x173C)>
INFO: Command line specified was: /script D:\SMS_BOOTSTRAP.ini /nouserinput $$<Configuration Manager Setup><09-24-2014 17:10:19.332+240><thread=5948 (0x173C)>
~FQDN for server ABCD is ABCD.msdn.net $$<Configuration Manager Setup><09-24-2014 17:10:19.348+240><thread=5948 (0x173C)>
INFO: Target computer is a 64 bit operating system. $$<Configuration Manager Setup><09-24-2014 17:10:34.354+240><thread=5948 (0x173C)>
INFO: Checking for existing setup information. $$<Configuration Manager Setup><09-24-2014 17:10:34.354+240><thread=5948 (0x173C)>
INFO: Checking for existing SQL information. $$<Configuration Manager Setup><09-24-2014 17:10:34.354+240><thread=5948 (0x173C)>
INFO: Verifying the registry entry for Asset Intelligence installation $$<Configuration Manager Setup><09-24-2014 17:10:34.354+240><thread=5948 (0x173C)>
INFO: Setting the default CSV folder path $$<Configuration Manager Setup><09-24-2014 17:10:34.354+240><thread=5948 (0x173C)>
INFO: No language packs detected. $$<Configuration Manager Setup><09-24-2014 17:10:34.354+240><thread=5948 (0x173C)>
INFO: Configuration Manager Build Number = 7958 $$<Configuration Manager Setup><09-24-2014 17:10:34.619+240><thread=5948 (0x173C)>
INFO: Configuration Manager Version = 5.0 $$<Configuration Manager Setup><09-24-2014 17:10:34.619+240><thread=5948 (0x173C)>
INFO: Configuration Manager Minimum Build Number = 800 $$<Configuration Manager Setup><09-24-2014 17:10:34.619+240><thread=5948 (0x173C)>
INFO: Verifying Configuration Manager Active Directory Schema Extensions. $$<Configuration Manager Setup><09-24-2014 17:10:34.619+240><thread=5948 (0x173C)>
INFO: Found DS Root:CN=Schema,CN=Configuration,DC=etsroot,DC=org~ $$<Configuration Manager Setup><09-24-2014 17:10:34.666+240><thread=5948 (0x173C)>
INFO: Verifying Configuration Manager Active Directory Schema Extensions. $$<Configuration Manager Setup><09-24-2014 17:10:34.697+240><thread=5948 (0x173C)>
INFO: Found DS Root:CN=Schema,CN=Configuration,DC=etsroot,DC=org~ $$<Configuration Manager Setup><09-24-2014 17:10:34.713+240><thread=5948 (0x173C)>
INFO: Command line options being used are /SCRIPT D:\SMS_BOOTSTRAP.INI /NOUSERINPUT $$<Configuration Manager Setup><09-24-2014 17:10:34.728+240><thread=5948 (0x173C)>
INFO: Checking download options... $$<Configuration Manager Setup><09-24-2014 17:10:34.744+240><thread=5948 (0x173C)>
INFO: Using product update files from the primary site server - secondary site push. $$<Configuration Manager Setup><09-24-2014 17:10:34.744+240><thread=5948 (0x173C)>
INFO: Secondary site Setup path is D:\INSTALLERS\SCCM_Source\SMSSETUP\bin\x64\SetupWPF.exe. $$<Configuration Manager Setup><09-24-2014 17:10:34.744+240><thread=5948 (0x173C)>
INFO: Cab file exists under D:\INSTALLERS\SCCM_Source\SMSSETUP\redist. $$<Configuration Manager Setup><09-24-2014 17:10:34.744+240><thread=5948 (0x173C)>
INFO: This is a secondary site push with local media. $$<Configuration Manager Setup><09-24-2014 17:10:34.744+240><thread=5948 (0x173C)>
INFO: Validating characters in path from Program Files\Microsoft Configuration Manager $$<Configuration Manager Setup><09-24-2014 17:10:34.744+240><thread=5948 (0x173C)>
INFO: 'PQRS.msdn.net' is a valid FQDN. $$<Configuration Manager Setup><09-24-2014 17:10:34.744+240><thread=5948 (0x173C)>
INFO: Script SQL Server: ABCD.msdn.net $$<Configuration Manager Setup><09-24-2014 17:10:34.744+240><thread=5948 (0x173C)>
INFO: Script SQL Server database: CONFIGMGRSEC\CM_EWZ $$<Configuration Manager Setup><09-24-2014 17:10:34.744+240><thread=5948 (0x173C)>
INFO: 'ABCD.msdn.net' is a valid FQDN. $$<Configuration Manager Setup><09-24-2014 17:10:34.744+240><thread=5948 (0x173C)>
INFO: This is a SQL Server named instance $$<Configuration Manager Setup><09-24-2014 17:10:34.759+240><thread=5948 (0x173C)>
INFO: SQL Server instance name (pSetupInf->SqlInstName): CONFIGMGRSEC $$<Configuration Manager Setup><09-24-2014 17:10:34.759+240><thread=5948 (0x173C)>
INFO: SQL Server master database (pSetupInf->SqlMasterDB): CONFIGMGRSEC\master $$<Configuration Manager Setup><09-24-2014 17:10:34.759+240><thread=5948 (0x173C)>
INFO: Site SQL Server database name (pSetupInf->SqlDatabaseName): CONFIGMGRSEC\CM_EWZ $$<Configuration Manager Setup><09-24-2014 17:10:34.759+240><thread=5948 (0x173C)>
INFO: Site SQL Server computer name (pSetupInf->SqlServer): ABCD.msdn.net $$<Configuration Manager Setup><09-24-2014 17:10:34.759+240><thread=5948 (0x173C)>
INFO: Site SQL Server service (pSetupInf->SqlService): MSSQL$CONFIGMGRSEC $$<Configuration Manager Setup><09-24-2014 17:10:34.759+240><thread=5948 (0x173C)>
INFO: Site SQL Server service port : 1433 $$<Configuration Manager Setup><09-24-2014 17:10:34.759+240><thread=5948 (0x173C)>
INFO: Site SQL Server SSB port : 4022 $$<Configuration Manager Setup><09-24-2014 17:10:34.759+240><thread=5948 (0x173C)>
Removed SQL alias ABCD.msdn.net\CONFIGMGRSEC successfully. $$<Configuration Manager Setup><09-24-2014 17:10:34.775+240><thread=5948 (0x173C)>
INFO: Registered type ABCD.msdn.net CONFIGMGRSEC\MASTER for ABCD.msdn.net CONFIGMGRSEC\master $$<Configuration Manager Setup><09-24-2014 17:10:34.791+240><thread=5948 (0x173C)>
INFO: Registered type SMS Master for ABCD.msdn.net CONFIGMGRSEC\master $$<Configuration Manager Setup><09-24-2014 17:10:34.791+240><thread=5948 (0x173C)>
INFO: Registered type ABCD.msdn.net CONFIGMGRSEC\CM_EWZ for ABCD.msdn.net CONFIGMGRSEC\CM_EWZ $$<Configuration Manager Setup><09-24-2014 17:10:34.791+240><thread=5948 (0x173C)>
INFO: Registered type SMS ACCESS for ABCD.msdn.net CONFIGMGRSEC\CM_EWZ $$<Configuration Manager Setup><09-24-2014 17:10:34.791+240><thread=5948 (0x173C)>
INFO: SQL Connection succeeded. Connection: ABCD.msdn.net CONFIGMGRSEC\MASTER, Type: Unsecure $$<Configuration Manager Setup><09-24-2014 17:10:34.853+240><thread=5948 (0x173C)>
INFO: SQL Server ABCD.msdn.net is not clustered. $$<Configuration Manager Setup><09-24-2014 17:10:34.869+240><thread=5948 (0x173C)>
INFO: Extracted file C:\Windows\TEMP\ConfigMgr.Manifest.xml $$<Configuration Manager Setup><09-24-2014 17:10:34.900+240><thread=5948 (0x173C)>
INFO: Processing file group "MSRDC" $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: Processing file "msrdcoob.exe" $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: File will be downloaded from http://go.microsoft.com/fwlink/?LinkId=95740. $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: File for msrdcoob.exe [Microsoft Remote Differential Compression Library] will be copied with file name: msrdcoob_x86.exe. $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: Processing file "msrdcoob.exe" $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: File will be downloaded from http://go.microsoft.com/fwlink/?LinkId=95741. $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: File for msrdcoob.exe [Microsoft Remote Differential Compression Library] will be copied with file name: msrdcoob_amd64.exe. $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: Processing file group "WUA" $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: Processing file "WindowsUpdateAgent30-x86.exe" $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: File will be downloaded from http://go.microsoft.com/fwlink/?LinkID=158451. $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: File for WindowsUpdateAgent30-x86.exe [Windows Update Agent 3.0] will be copied with file name: WindowsUpdateAgent30-x86.exe. $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: Processing file "WindowsUpdateAgent30-x64.exe" $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: File will be downloaded from http://go.microsoft.com/fwlink/?LinkID=158453. $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: File for WindowsUpdateAgent30-x64.exe [Windows Update Agent 3.0] will be copied with file name: WindowsUpdateAgent30-x64.exe. $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: Processing file group "Silverlight" $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: Processing file "Silverlight.exe" $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: File will be downloaded from http://go.microsoft.com/fwlink/?LinkID=317308. $$<Configuration Manager Setup><09-24-2014 17:10:34.915+240><thread=5948 (0x173C)>
INFO: File for Silverlight.exe [Silverlight Runtime] will be copied with file name: Silverlight.exe. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: Processing file group "WIC" $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: Processing file "wic_x86_enu.exe" $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File will be downloaded from http://go.microsoft.com/fwlink/?LinkId=234177. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File for wic_x86_enu.exe [Windows Imaging Component 32 Bit] will be copied with file name: wic_x86_enu.exe. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: Processing file "wic_x64_enu.exe" $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File will be downloaded from http://go.microsoft.com/fwlink/?LinkID=234176. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File for wic_x64_enu.exe [Windows Imaging Component 64 Bit] will be copied with file name: wic_x64_enu.exe. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: Processing file group "Dot_Net_Framework" $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: Processing file "dotNetFx40_Client_x86_x64.exe" $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File will be downloaded from http://go.microsoft.com/fwlink/?LinkId=199236. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File for dotNetFx40_Client_x86_x64.exe [.NET Framework Client Profile 4.0 RTM] will be copied with file name: dotNetFx40_Client_x86_x64.exe. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: Processing file "dotNetFx40_Full_x86_x64.exe" $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File will be downloaded from http://go.microsoft.com/fwlink/?LinkID=224688. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File for dotNetFx40_Full_x86_x64.exe [.NET Framework Extended 4.0 RTM] will be copied with file name: dotNetFx40_Full_x86_x64.exe. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: Processing file group "SQL_Redist" $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: Processing file "SQLEXPR_x64_ENU.exe" $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File will be downloaded from http://go.microsoft.com/fwlink/?LinkId=267646. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File for SQLEXPR_x64_ENU.exe [SQL Server 2012 Express] will be copied with file name: SQLEXPR_x64_ENU.exe. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: Processing file "msxml6_x64.msi" $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File will be downloaded from http://go.microsoft.com/fwlink/?LinkID=169539. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File for msxml6_x64.msi [MSXML 6.0 Service Pack 1] will be copied with file name: msxml6_x64.msi. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: Processing file "sqlncli.msi" $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File will be downloaded from http://go.microsoft.com/fwlink/?LinkID=261336. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File for sqlncli.msi [SQL Server 2012 Native Client] will be copied with file name: sqlncli.msi. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: Processing file "SQLSysClrTypes.msi" $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File will be downloaded from http://go.microsoft.com/fwlink/?LinkId=253284. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File for SQLSysClrTypes.msi [SQL Server 2012 System CLR Types] will be copied with file name: SQLSysClrTypes.msi. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: Processing file "SharedManagementObjects.msi" $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File will be downloaded from http://go.microsoft.com/fwlink/?LinkID=253273. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: File for SharedManagementObjects.msi [SQL Server 2012 Shared Management Objects] will be copied with file name: SharedManagementObjects.msi. $$<Configuration Manager Setup><09-24-2014 17:10:34.931+240><thread=5948 (0x173C)>
INFO: Processing file "ConfigMgr.AutoUpgradeScripts.cab" $$<Configuration Manager Setup><09-24-2014 17:10:34.947+240><thread=5948 (0x173C)>
INFO: File will be downloaded from http://go.microsoft.com/fwlink/?LinkID=316446. $$<Configuration Manager Setup><09-24-2014 17:10:34.947+240><thread=5948 (0x173C)>
INFO: File for ConfigMgr.AutoUpgradeScripts.cab [Configuration Manager Auto Upgrade Scripts] will be copied with file name: ConfigMgr.AutoUpgradeScripts.cab. $$<Configuration Manager Setup><09-24-2014 17:10:34.947+240><thread=5948 (0x173C)>
INFO: Checking Service Account: Sql server:<ABCD.msdn.net>, Instance:<CONFIGMGRSEC>, Service Account:<LocalSystem>. $$<Configuration Manager Setup><09-24-2014 17:10:34.947+240><thread=5948 (0x173C)>
INFO: MSXML60 is not installed, installing now. $$<Configuration Manager Setup><09-24-2014 17:10:34.947+240><thread=5948 (0x173C)>
INFO: csXMLPath:<\\ABCD.msdn.net\admin$\ConfigMgrTmp\msxml6_x64.msi>, csXMLCommandLine:<>, csXMLSetupLog:<\\ABCD.msdn.net\admin$\ConfigMgrTmp\msxml60.log>. $$<Configuration Manager Setup><09-24-2014 17:10:35.025+240><thread=5948
(0x173C)>
INFO: 64-Bit Visual C++ Redistributable package is already installed. Will skip installation. $$<Configuration Manager Setup><09-24-2014 17:10:35.805+240><thread=5948 (0x173C)>
INFO: SQL Server Native Client: SQLNCLI11 version:<11.2.5058.0> $$<Configuration Manager Setup><09-24-2014 17:10:35.805+240><thread=5948 (0x173C)>
INFO: Installing msxml60 $$<Configuration Manager Setup><09-24-2014 17:10:35.805+240><thread=5948 (0x173C)>
INFO: Executing Command <msiexec.exe /i "D:\INSTALLERS\SCCM_SOURCE\SMSSETUP\BIN\X64\00000409\msxml6_x64.msi" /quiet /norestart>. $$<Configuration Manager Setup><09-24-2014 17:10:35.805+240><thread=5948 (0x173C)>
INFO: D:\INSTALLERS\SCCM_SOURCE\SMSSETUP\BIN\X64\00000409\msxml6_x64.msi installation process returned 0. $$<Configuration Manager Setup><09-24-2014 17:10:36.101+240><thread=5948 (0x173C)>
INFO: Installing SQL Common Language Runtime types $$<Configuration Manager Setup><09-24-2014 17:10:36.101+240><thread=5948 (0x173C)>
INFO: Executing Command <msiexec.exe /i "D:\INSTALLERS\SCCM_SOURCE\SMSSETUP\BIN\X64\SQLSysClrTypes.msi" /quiet /norestart>. $$<Configuration Manager Setup><09-24-2014 17:10:36.101+240><thread=5948 (0x173C)>
INFO: D:\INSTALLERS\SCCM_SOURCE\SMSSETUP\BIN\X64\SQLSysClrTypes.msi installation process returned 0. $$<Configuration Manager Setup><09-24-2014 17:10:36.413+240><thread=5948 (0x173C)>
INFO: Installing SQL Server Shared Management Objects $$<Configuration Manager Setup><09-24-2014 17:10:36.413+240><thread=5948 (0x173C)>
INFO: Executing Command <msiexec.exe /i "D:\INSTALLERS\SCCM_SOURCE\SMSSETUP\BIN\X64\SharedManagementObjects.msi" /quiet /norestart>. $$<Configuration Manager Setup><09-24-2014 17:10:36.413+240><thread=5948 (0x173C)>
INFO: D:\INSTALLERS\SCCM_SOURCE\SMSSETUP\BIN\X64\SharedManagementObjects.msi installation process returned 0. $$<Configuration Manager Setup><09-24-2014 17:10:38.238+240><thread=5948 (0x173C)>
INFO: Setting -T8295 SQL Server Param already exists. $$<Configuration Manager Setup><09-24-2014 17:10:45.445+240><thread=5948 (0x173C)>
INFO: Setting -T4199 SQL Server Param already exists. $$<Configuration Manager Setup><09-24-2014 17:10:45.445+240><thread=5948 (0x173C)>
INFO: Creating SQL Server machine certificate for Server [ABCD.msdn.net]... $$<Configuration Manager Setup><09-24-2014 17:10:45.445+240><thread=5948 (0x173C)>
INFO: 'ABCD.msdn.net' is a valid FQDN. $$<Configuration Manager Setup><09-24-2014 17:10:45.445+240><thread=5948 (0x173C)>
Certificate (0x1aeb4a80) is NOT Exportable. $$<Configuration Manager Setup><09-24-2014 17:10:45.460+240><thread=5948 (0x173C)>
Successfully granted permission to certificate $$<Configuration Manager Setup><09-24-2014 17:10:45.492+240><thread=5948 (0x173C)>
SQL Server instance [CONFIGMGRSEC] is already running under the certificate with thumbprint[84746003654ef08c43dcc47e1a343d8b37d21469]. $$<Configuration Manager Setup><09-24-2014 17:10:45.492+240><thread=5948 (0x173C)>
INFO: Testing SQL Server [ABCD.msdn.net] connection ... $$<Configuration Manager Setup><09-24-2014 17:10:45.492+240><thread=5948 (0x173C)>
INFO: SQL Connection succeeded. Connection: ABCD.msdn.net CONFIGMGRSEC\MASTER, Type: Unsecure $$<Configuration Manager Setup><09-24-2014 17:10:45.492+240><thread=5948 (0x173C)>
INFO: Tested SQL Server [ABCD.msdn.net] connection successfully. Any preceding SQL connection errors may be safely ignored. $$<Configuration Manager Setup><09-24-2014 17:10:45.492+240><thread=5948 (0x173C)>
INFO: Certificate: 3082084030820628A003020102020A7E0EAA96000000008A93300D06092A864886F70D0101050500305131133011060A0992268993F22C64011916036F726731163014060A0992268993F22C64011916066574736C616E312230200603550403131949737375696E6720434120666F72204554534C616E2E6F7267301E170D3134303732313133333734375A170D3137303732303133333734375A301D311B30190603550403131245575A4E5434332E6574736C616E2E6F726730820222300D06092A864886F70D01010105000382020F003082020A0282020100D7199E6238D908EF4CB302953E4111CBFBDEBDCBA94F62C3066A334565B54B0274C3C2ABA26529A22B0C757193B713F4E6E892B3D6C87BFFC8CCA24C34CDFE0D62D67F913A9D6F950E2B22BB3C881C0EE7453644000679BA0DE77584F3F4AB3E700EF6F019738C3E4659C7FBA17390FF155762E639600828A5B8EA853EFCC7A6A2A579AEE2D322F5A57CA90E411F784870AFDEDA66176595EF0D2454A2A135ADC102B86DF3FB9DF95AF43538C96772C8D7CBF92FEDC1A0B53BEA482EFF0036E8C2BCC4A1A68C918AF65F095B2EB260C76D30CC870CA4C803E392F02ECEAF08199F8C26C389AD6DC9B79A5255C8A5819BF217A8AC37F790AEF232698CF1253BE320CE95B127F02AE5A77AEAE86382932649FB814B33C844EFB3F7931BE6FA86DE01BDD36F53BCC4CB840A24E5F94874017941D48A712F61442677578FC08F90E36CD0BD6E696E7E1D543D83CA0E29CDA81FC058987F0F2D0AB404DB5C0688B5B787C929F0FE104EF788A610E7C272CE751D59EDCEF5A78DD6FC1C742438A81DBF38F20A3D4DC03F7CC5BCF0C48868F8A6E433B6A05A6F5DC8FEBF22C69E72B499D645AC88ABFA034A4BF7917E061DFA069D9E2243EF82DC7C9A9A11DA9EE88D3C5DC23135568B170D4A5B4053516FF2CC795B98CAD1D3C12738977DA645309ED187122FCA9EE361A65645EEFEA84BEDDD8CFB444B0AB884B87970685DCA9954970203010001A382034C30820348303C06092B0601040182371507042F302D06252B06010401823715088292D01787C6C15E8D910184B5EA1684AFF052398393846682E4BF5D020164020102301D0603551D250416301406082B0601050507030106082B06010505070302300B0603551D0F0404030205A0302706092B060104018237150A041A3018300A06082B06010505070301300A06082B06010505070302301D0603551D0E041604145189BA390740BFAA1E7E8C7BFD4306523E90A454301F0603551D2304183016801467A0E5C222ED9DBE1494687B53543BA59F900F2E3082011F0603551D1F04820116308201123082010EA082010AA08201068639687474703A2F2F6364702E6574736C616E2E6F72672F49737375696E672532304341253230666F722532304554534C616E2E6F72672E63726C8681C86C6461703A2F2F2F434E3D49737375696E672532304341253230666F722532304554534C616E2E6F72672C434E3D726F73766E743031382C434E3D4344502C434E3D5075626C69632532304B657925323053657276696365732C434E3D53657276696365732C434E3D436F6E66696775726174696F6E2C44433D657473726F6F742C44433D6F72673F63657274696669636174655265766F636174696F6E4C6973743F626173653F6F626A656374436C6173733D63524C446973747269627574696F6E506F696E743082012F06082B06010505070101048201213082011D305A06082B06010505073002864E687474703A2F2F6364702E6574736C616E2E6F72672F726F73766E743031382E6574736C616E2E6F72675F49737375696E672532304341253230666F722532304554534C616E2E6F72672E6372743081BE06082B060105050730028681B16C6461703A2F2F2F434E3D49737375696E672532304341253230666F722532304554534C616E2E6F72672C434E3D4149412C434E3D5075626C69632532304B657925323053657276696365732C434E3D53657276696365732C434E3D436F6E66696775726174696F6E2C44433D657473726F6F742C44433D6F72673F634143657274696669636174653F626173653F6F626A656374436C6173733D63657274696669636174696F6E417574686F72697479301D0603551D1104163014821245575A4E5434332E6574736C616E2E6F7267300D06092A864886F70D010105050003820201000BE330377D5E135957F081F19A115926E193ABD986A868EA47BF7758D2B192B5DB12664AA7B6A27A4C3B1D5F20F81D4E04AA72686ACE3B5CF8FD168BD0525FD1688DC4404447A2ACE4AA30C61CCD9748E5AA0949430CD7C8A5F412F604807C3D49AD9CC42B89EB25BD13A6E06E1844D9BBFC2ECD0ED90D781C34DE33168666C674DA63988390B3BDAE4112F2AC1F3CAC102D930B30C7E87A195816A0DF89987F4440963CA67E2CD95C4F8698915A3B81D9B234608EB763B2FFD38134F063D8DC94C5B37C696DCFC8232088987A4C874AB6F9D43849A59EF5E8D433288192B25A7466468451F438586985C773DFCEA98990DD0161A9BBD9E831388608BE8A832B316D423360D2E57F8030100C349AFD3BA87188F193052DF1653433F7F4B38FBC95C4DAA60CA7F3AC762329B150EC3D776F1522199105446C42A012DB7722DC813C7A8702BDDB18C10AF7C541CA7EA96FE309414FECDA1F06A9F5B89C88882751503B477E3ED9BFF886DC7D67BF34E23E7B0B17F150671D8428C239A79513D7980BB47C911AFE16BFA682E7618753837A50E6E9D5259C7A39A0195E890CBA88DD8802C9553F7DDE1288CF5A5B4723572574FA166EAC105F5557A1A5845D759A668A72A6058FA12CF953C93C5E23E4FB513039A3BE02FCFB2AB284BFF0797A50CD700829DAC76E11E0773A421DBC92E7A583D8C82866051CF846D7101C1988074F
$$<Configuration Manager Setup><09-24-2014 17:10:45.492+240><thread=5948 (0x173C)>
INFO: Created SQL Server machine certificate for Server [ABCD.msdn.net] successfully. $$<Configuration Manager Setup><09-24-2014 17:10:45.585+240><thread=5948 (0x173C)>
ERROR: could not add certificate (HRESULT=0x80093102) $$<Configuration Manager Setup><09-24-2014 17:10:45.679+240><thread=5948 (0x173C)>
ERROR: Failed to write PQRS.msdn.net SQL Server certificate to store (TrustedPeople) on site server (ABCD.msdn.net). $$<Configuration Manager Setup><09-24-2014 17:10:45.679+240><thread=5948 (0x173C)>
ERROR: Failed to write certificate of primary site's SQL Server [PQRS.msdn.net] to secondary site's SQL Server [ABCD.msdn.net]. $$<Configuration Manager Setup><09-24-2014 17:10:45.679+240><thread=5948 (0x173C)>
~Fail to create SQL Server Certificate for primary on CAS, ConfigMgr installation cannot be completed.
$$<Configuration Manager Setup><09-24-2014 17:10:45.679+240><thread=5948 (0x173C)>

Hi There,
I have already installed SQL 2012 Express with SP2 on the Secondary and installing the SCCM 2012 R2 Secondary Server from Primary Console.
In smstsvc.log I get :
<09-26-2014 13:38:00> Failed SetExchangePublicKey().
<09-26-2014 13:38:00> Failed GetExchangePublicKey().
And in ConfigMgrSetup.log everything it stops with below errors :
ERROR: could not add certificate (HRESULT=0x80093102)
ERROR: Failed to write
PQRS.msdn.net SQL Server certificate to store (TrustedPeople) on site server (ABCD.msdn.net).
ERROR: Failed to write certificate of primary site's SQL Server [PQRS.msdn.net] to secondary site's
SQL Server [ABCD.msdn.net].
Fail to create SQL Server Certificate for primary on CAS, ConfigMgr installation cannot be completed.
~===================== Completed Configuration Manager 2012 Server Setup =====================
NOT GETTING ANY CLUE...... PLEASE HELP.... All the permissions on the SQL are in-place.

SharePoint Multi-Server Farm with LB and SQL Cluster.

Helllo,
We are setting up a Multi Server SharePoint 2013 Farm with a Load-Balancer.
We are also using SQL Server 2012, Two Node Cluster.
We have SQL Server Instance Running as a Service. Also I managed to install PowerPivot for SharePoint as a Instance.
Looking at various article's I have question if this Cluster Setup supported in SharePoint 2013.
Can the SharePoint Farm use this PowerPivot Instance as a failover service?
Or do I have to install Analysis services separately on Both SQL Nodes?
If so how do I configure Excel Services on SharePoint?
Thank you
Sham

PowerPivot is installed on the SharePoint server and is a scale-out service (you just install it on multiple SharePoint servers and make sure the Service Instance is started in SharePoint). Same with Excel Calc Services (but for this one you don't have
to install anything, just start it).
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Difference between database features - SQL Server 2008 R2 navtive vs SQL Server 2012 with SQL Server 2008 compatibility set?

I am investigating the impact of upgrading from SQL Server 2008 R2 to SQL Server 2012. To reduce the impact of the upgrade, I am planning to restore / create our application database onto SQL Server 2012 with compatibility level 100 (SQL Server 2008 and
SQL Server 2008 R2).
Are there any differences in feature support for database running in native mode on SQL Server 2008 R2 vs a database installed on SQL Server 2012 with compatibility level 100 set?

Are there any differences in feature support for database running in native mode on SQL Server 2008 R2 vs a database installed on SQL Server 2012 with compatibility level 100 set?
Yes there can be difference and impact there are few features deprecated in SQL Server 2012 you must be aware about that. Please see
Deprecated Database Features in SQL Server 2012
Deprecated SQL Server features in SQL Server 2012
After you migrate database to 2012 please don't move ahead with production unless you have tested your application to new created database
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

Advance features available in sql server 2008 R2 compared with SQL 2008 SP2

Hi,
Can some one brief me the advance features available in sql server 2008 R2 compared with SQL Server 2008 SP2.
I am planning to upgrade my existing sql server 2008 SP2 to sql server 2008 R2, before that i need the advantages to proceed , if the advantages are not suite to my requirements then i will drop out this option.
Please give me the detailed reply for my analysis
hemadri

Hi Hemadribabu,
There are some new features in SQL Server 2008 Service Pack 2(SP2), including SQL Server utility, Data-tier Application (DAC), Reporting Services in SharePoint Integrated mode and partitioning improvement. Features are supported by the different editions
of SQL Server 2008 R2. For example, the Report Builder 3.0, PowerPivot for excel are available on the SQL Server Datacenter and SQL Server 2008 R2 Parallel Data Warehouse, they can assist you creating business intelligence documents. Here are the Top
new features in SQL Server 2008 R2, including
Report Builder 3.0, SQL Server 2008 R2 Datacenter, SQL Server 2008 R2 Parallel Data Warehouse,
StreamInsight, Master Data Services and so on.
For more information about SQL Server 2008R2 and SQL Server 2008 SP2, you can review the following articles.
http://msdn.microsoft.com/en-us/library/cc645993(v=sql.105).ASPX
https://social.technet.microsoft.com/wiki/contents/articles/1486.microsoft-sql-server-2008-sp2-release-notes.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Connect BizTalk Server Configuration with Sql Azure - version 2013 R2

Hi,
My data resides on Sql Azure. I need to create BizTalkRuleEngineDb on Sql Azure using Microsoft BizTalk Server Configuration wizard. Subsequently manage rules from Business Rule Composer.
I am unable to connect to Sql Azure from BizTalk Server Configuration application. Without this i could not create BizTalkRuleEngineDb on Sql Azure. I gave the following details:
Database server name: <servername>.database.windows.net,1433
User name: <username>
Password: <pwd>
When i click configure button, a message pops "The database server you specified cannot be reached...."
All i need from BizTalk is to create Business Rules Engine DB on Sql Azure. Then I would like to manage rules using Business
Rule Composer connecting to Sql Azure BizTalkRuleEngineDb.<o:p></o:p>
My business logic will programmatically access BizTalkRuleEngineDb db and execute rules using Microsoft.RuleEngine.dll<o:p></o:p>
Is this a feasible solution? I would like to see your inputs.
Any help is appreciated.
Thanks,
Tushar

First I would suggest you to perform sanity check to confirm if SQL server connectivity is perfect.
1) Verify the MSDTC Settings on both the servers:- It should resemble as below.
2) UDL Test:- Create a new "Text Document"(new notepad file) rename it to ABC.udl, double click and give the SQL server details and Test connection. If this fails it means BizTalk is not at all able to connect with SQL and in this
case BizTalk Application is just a victim of Network connectivity issue.
You can also refer the below article-
Resolving the issues you may face during BizTalk Runtime Configuration
Thanks,
Prashant
Please mark this post accordingly if it answers your query or is helpful.

BPC 7.0 MS Seperated Multi Server

Hi All,
This shoud be a quick one...
Imagine a 3 Server environment (2 Web/App, 1 DB) where the web/app servers were NOT load balanced but seperate entities sharing the same DB server and AppSets, is there any reason why this would not work?
Thanks

Ok let's clarify few things.
Once with installation two tables store information of servers:
tblappsetinfo and tblserverinfo provide the information who is the application server sql server, SSAS server ....
Into tblappset info you have a lines like:
appset1 sql server1, OLAP server 1, web server 1, ....
appset 2 sql server 1, OLAP server 1....
Into tblserver info it is specify wo are the servers:
SQL Server 1 Name of your SQL Server
SSAS Server1 Name of your SSAS Server
So here you can have two application servers one Application Sererv 1 and the second Application Server 2.
If you are speaking about different appsets then it is no problem you will specify for the seond appset to use Application Server 2 instead of application server 1.
But for the same appset the main problem it is that actually you cannot specify two application servers.
So to solve this problem without using NLB you have actually to simulate kind of virtual name.
So you will input into tblserver iinfo just one application server with exactly this virtual name
Application Server1 NLBVirtualname
Into tblappsetinfo you have to use just Application Server1
Into each host file of these application server you will have to associate
NLBVirtualServerName IpofApplicationServer of that host file
In this way you can handle the request to have one multiple application servers withotu NLB.
Regards
Sorin Radulescu

SSRS configuration in multi server environment with SSL

Hi
I have read numerous articles on configuration of Reporting Services in SharePoint integrated mode but not able to figure out if I'm missing something.
Environment description
SharePoint Enterprise 2010
2 web servers, 2 app servers, 1 DB server.
Authentication is custom claims (not windows claims)
Since SSRS does not work in Custom Claims (confirmed by MS in ticket), we extended the webapplication. The URLs are
https://actualurl (custom claims)
https://EWAURL (Windows NT and Extended Web Application)
Reporting Services Add-In has been installed on 2 web and 2 app servers.
Reporting Services is running on app01 server. When we access
http://app01/reportserver we get list of site collections. However when we try to create a new Report Source in
https://EWAURL we get exception. Exception has both certificate error and SSRS SOAP exception. SSRS URL is not SSL enabled.
My question is:
Does SSRS work when it is running only on one app server? Or do I need to install reporting services on all app and web servers and then configure them to the app01 Reporting DB?
Due to limitations we are trying to use one app server as reporting server.

My apologies
I thought I was creating this in SharePoint 2010 - Setup, Upgrade, Administration and Operations.
@Admin/Moderator: could you please change this to the correct forum

X86 Workgroup Server Installation with 1 CPU

Hi Folks,
I have couple of newbie questions ..
a) Can I Install Workgroup Server mode on X86 with 1 CPU ?
b) I registered with sun to get a 60 day evaluation license. How long does it usually take for getting it?

Hi,
You should use the OpsMgrDWRead account.
www.coretech.dk - blog.coretech.dk

Connecting to MS SQL server 2000 with SSMS 2008

Hello
I have been trying to solve this problem for months now and searched lots of threads, but no success.
Our office has sql server 2000 database, which is installed on Windows XP. I am given 'sa' password. On my computer, which is Windows 7, I have SSMS 2008. I am able to connect to mentioned server using Windows ODBC data source and with MS Access.
The problem is no matter what I tried, I could not connect with SSMS. When I go to "Server Connection" > "Server Name" > > "Network Servers" in SSMS, the needed server is found automatically, but I still fail to connect.
I know that SSMS 2008 should be able to connect to server2000 (or maybe I am wrong?).
Please help.

TITLE: Connect to Server
Cannot connect to SOFODB.
ADDITIONAL INFORMATION:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
BUTTONS:
OK
I am not sure but this type of issue can be resolved by increasing time out.Time out sec is 15 by default change it to 60 or 120 and see if you can connect if not please revert.
When you are connecting using SSMS click on option button...In connection properties page see for connection timeout...change it to 60 or 120 .See if this works
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

SAP BPC 5.1 multi-tier installation

We are implementing SAP BPC 5.1 as a multi-tier installation with 2 Windows servers.
Server 1 - SQL Server 2000 Database , OLAP & Reporting Services
Server 2 - Web / Application & Fileshare
Are there any issues that i need to be aware of with a multi-tier install ?
Service-level accounts for BPC - Do these accounts need to be the same between DEV and Prod. The install giude do not seem to indicate that these accounts have to be the same, however I just want to confirm
We did a trial installation and I get the following error :
Job name : http://wdsectest01vm/osoft/Launch.aspx
Detail : Unable to generate a temporary class (result=1). -- error CS2001: Source file C:Tempa71qdytz.0.cs could not be found -- error CS2008: No inputs specified --
Any help will be greatly appreciated
Thanks
Subha

Hello Subha,
You can test the PTR dns records using nslookup.
I will use db.example.com and app.example.com as the fully qualified domain names below.
Open a command prompt (Start -> Run and type cmd) and type the following
nslookup
app.example.com
note - this should return the ip address of the application server and represents
the host (A) record in DNS. Lets assume it returns an ip of 1.1.1.10
set type=PTR
1.1.1.10
note - this will return the reverse lookup (PTR) record for the ip address and
in this example should resolve to app.example.com
exit
After you complete the nslookup for the appserver do the same for the database servers fqdn (db.example.com).
You should perform this test on each tier. If you run into any inconsistencies then your network/DNS administrator should be able to assist you in getting the appropriate records created.

BPC 70 SP4 and SQL 2008 Feature Pack

Is the SQL 2008 Feature Pack required in a BPC 70 SP4 installation with SQL 2008? It is listed as a prerequisite, but our DBA's would prefer that it not be installed. My understanding is that this is needed for backward compatability. Thre are notes related to this for SP3, but nothing for SP4.

Hi John,
I just checked it and you don't need all feature pack.
Just install Microsoft SQL Server 2005 Backward Compatibility Components on Microsoft SQL Server 2008 Feature Pack.
This is for executing custom packages that was created in SQL2005.
I hope it will help you.
James Lim.

BPC-MS 7.5 SP5 Multi-Server Installation with SQL 2008

Similar Messages

Maybe you are looking for