Setup CTS+ for MDM 5.5
Hello ,
I have to configure Charms on MDM 5.5 . Can anyone please let me know whether there is a possibility of configuring CTS+ on MDM 5.5.
Please forward the Documents realted to Setup and use of CTS+ for MDM 5.5 .
Thanks in advance
Regards,
Reddi
Vrreddi,
Please refer this how to Guide for MDM 7.1,
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d0dd1ae0-36e5-2b10-f8b4-e6365e643c0b&overridelayout=true
Please check this for MDM 5.5. As per my knowledge, I think this Setup CTS + for MDM 5.5 is not available. So, I am afraid may be you have to Upgrade MDM Verson from MDM 5.5 to MDM 7.1.
Hope it will help you
Thanks,
Mandeep Saini
Similar Messages
-
How to setup CTS+ for BODS 4.1 systems
Hi all,
I am trying to setup CTS+ for BODS systems to transport the objects from dev--> QA---> Prod.
I Couldnt find any document which explains about CTS+ for BODS systems.
I have some knowledge on how CTS+ works and worked on CTS + for EP and PI.
Can someone let me know the steps involved in setting up CTS + for BODS 4.1 systems.
Thanks
Vimal.SMR
Message was edited by: Andy SilveyHi Vimal,
see if this OSS Note helps:
1762987 - How to configure LCM with CTS+
Kind regards,
Andy. -
Hello Gurus,
While configuring SMD setup for MDM system, i am getting following error, for MDIS and MDSS
[Wilyhost Agent] Failed to configure EP Agent for sapkrftmox01.krft.net (MDM Host)
My MDM system is not an EP system, strainge how am i getting this error related to EP.
Also in the Local SMD Agent Application log on MDM Host getting the error
[Thread[Thread-14,5,main]] Warning com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAPOsCol not running because status is PERMANENT_ERROR
[Thread[Thread-23,5,main]] Warning com.sap.smd.wily.hostagent.action.SapOsColAction - launchDaemon(): launchDaemon: saposcol exited with -1
[Thread[ExecutionRunner_4,5,ExecMgrThreadGroup]] Warning com.sap.smd.wily.hostagent.destination.ProcessReader - readOutput: Error output: prtdiag can only be run in the global zone
Need the help...please....
Regards
ManojHi
Implement SAP Note 1466312 -
Hello Gurus,
While configuring SMD setup for MDM system, i am getting following error, for MDIS and MDSS
[Wilyhost Agent] Failed to configure EP Agent for sapkrftmox01.krft.net (MDM Host)
My MDM system is not an EP system, strainge how am i getting this error related to EP.
Also in the Local SMD Agent Application log on MDM Host getting the error
[Thread[Thread-14,5,main]] Warning com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAPOsCol not running because status is PERMANENT_ERROR
[Thread[Thread-23,5,main]] Warning com.sap.smd.wily.hostagent.action.SapOsColAction - launchDaemon(): launchDaemon: saposcol exited with -1
[Thread[ExecutionRunner_4,5,ExecMgrThreadGroup]] Warning com.sap.smd.wily.hostagent.destination.ProcessReader - readOutput: Error output: prtdiag can only be run in the global zone
Need the help...please....
Regards
ManojHi,
Can you check your SAP OS Collector is running (SSAPOSCOL)?
What is your Solman version?
Thanks,
Pradeep -
How to configure CTS+ for Solution Manager for XI 3.0
Hi ,
We are working on XI 3.0 SP 20 and Doing a file system based transport of .TPZ files. We observed that there is a possibilit of misssing the objects while tranporting. So we are planning to set CTS+ with our Solution Manager.
Question:
1. Can we configure CTS+ through the latest version of Solution Manager for XI 3.0 landscape?
If Yes .. How? If No... Why?
2. Is there any way to make the the transport automated like ABAP tranports.
If there is.... Please send the link or documents..
Thanks
ManojHi Venkat,
Thank you for the Demo. The Demo gives me information about the CTS+ setup. I am looking for the compatability of CTS+ for XI 3.0.
We have Solution Manager 7.1 setup in place.
Please let us know if we can setup CTS+ on solution Manager (7.01 EHP1) and use it to transport XI 3.0 SP20 IR/ID objects across the XI landscape.
Regards,
Manoj -
Managed System Configuration Error for MDM 7.1 SP09
Greetings, Needed your expert advise. We are getting an error while configuring our MDM Servers (Version 7.1.08.196) in Solution Manager. As suggested in SAP Note 1798643 , I have manually filled the required details and transferred through sldreg.exe to SLD. Now when i try to perform Managed System Configuration, it is throwing the below error. The definition of Technical System '~MDM' is not correct: '~MDM': No Path found in Installed Technical System 'SID~MDM~'. I'm not sure how to manually update the Install Path for our MDM Servers. Since, the data to LMDB is automatically supplied, I might not be able to manually edit anything. Could you please advise if there is any step to solve this issue. Thanks, Haseeb Ahmed.
Dear ,
Haseeb,
I had the exact same problem with MDM managed system setup . I was on MDM 7.1 SP10.
1940337 - RCA template for Solution Manager 7.10 SP10
This note should resolve your problem. This note has the updated template for MDM.
It did for mine
Thanks
Amit -
Hi,
does anybody know an "How to Guide" for Implementing and setup CTS+ in SAP Solution Manager ?
Kind regards
AndreasHi
[How to CTS + on PI 7.1|http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20ccd0ec-2839-2b10-0097-828fcd8ed809]
[CTS + on SAP NW 7.0 sp13|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0ebf83b-6201-2b10-b58b-c14d3d3b6f61]
there just check in background information section, there you get more document link for CTS+ in different scenario,
Thanks,
Jansi -
MDM JAVA API SCA file for MDM 7.1 SP04
I need to download MDM JAVA API SCA file for MDM 7.1 SP04. When I added to the download basket through service marketplace it is looking for the approval process, just for the API file. I was able to get the other files though like webdynpro framework, change tracker. We haven't setup the Solution Manager yet. It might take a while. Meanwhile is there any other way to get the SCA file.
ThanksOpened message with SAP and they have approved the download basket. Now able to download the sca file.
-
Printers do not show up in Page Setup Format for menu
Hello. I just installed Acrobat 9 Professional. Upgrade from AP7. For some reason, when I go to select the printer in the Page Setup> Format For> dropdown menu, the printers do not show up. When I try to make a pre-set for this printer it never works and always defaults back to Language Level 3, which gives me a postscript error when I try to print. It prints fine at Language Level 2 but I can't get the setting to stay. Any clues???
thank you in advance,
RandyGeraldine,
There are some oddities in Pages' methods.
What you did was save the changed template which had been altered on the page but you also needed to "capture" and save the Layout or Section over the existing one in the document using the same name to replace it.
I will walk you through making your own version of a template.
1 Open a new document using the template you wish to customise.
2 Don't change anything yet, but open every section from the Sections pull down menu so you have a sequence of pages each with a page of a different section design.
3 Make Master Objects selectable if they are not. Change each Section to your liking.
4 +Menu > View > Page Thumbnails+
5 Select first Thumbnail in sidebar +Menu > Format > Advanced > Capture Pages… > Name : Type exactly the same name as the section > It will ask you if you want to replace the existing section > Replace+
6 Repeat this for each section until you have replaced them all.
7 +Menu > File > Save as Template… > Save with a New Name+
8 +Menu > File > New from Templates > My Templates > Choose your New Name template+
You now have a document customised to your design.
Peter -
We have two Apple ID's but share the same computer....that runs Itunes...How do i setup Icloud for ea. user ID?
You can't merge Apple IDs. What you could do is set up your phone to use the same iCloud accout you are using on your Mac. To do this, go to Settings>iCloud and turn all synced data (Contacts, Calendars, etc.) to Off. When prompted, choose to keep the data on the phone. When everything is off, scroll to the bottom and tap Delete Account. Now add the iCloud account you set up on your Mac (with the same Apple ID) and turn syncing back on for Calendars, Contacts, etc. When prompted, you will probably want to choose merge, to merge the data on your phone with the existing data on this iCloud account.
-
Error while filling setup tables for 2lis_13_vahdr
Dear friends,
I am getting below Error while filling setup tables for 2lis_13_vahdr.
More faulty documents found than the tolerated 0000000000
Message no. M2222
Can any one guide me how to address this issue.
Thanks and Regards
NithyaHello Nithya,
It seems the No of tolerated faulty documents that you have given is 0. So when you initialize try to these.
While executing OLI*BW including a value in the maintain "No. tolerated faulty documents" - 5000 or 10000.
Then execute the program in background.
Once the job is completed check the background job log if any errors.
Thanks
Chandran -
Error while filling setup table for Sales
Dear Team,
We are getting following error while filling setup table for Sales (application component 11) and for Billing (application component 13),
application component 11
Error determining rate: foreign curr. local curr. INR date 08.10.2007 (doc. 673624) (JOB - RMCVNEUA)
Message No M2810
application component 13
Billing document 480050000: error determining stats. currency rate (no updating)
More faulty documents found than the tolerated 0000000000 (JOB - RMCVNEUF)
I have seen lot of threads based on this but all r showing diffrenent currency to INR but for the above mentioned documents currency is in INR only so why it is showing the error I am not able to determine.
If anybody faced this problem kindly reply to this.
Best Regards,
SGHi There,
Might be your using a wrong document number.
I mean if your using the 11 you should use only Sales document number and for 13 you should only use billing document number.
If you use vice versa that error will throw.
Regards,
MQ -
Error while filling setup table for 2LIS_03_BF
Hello,
I am getting an error while filling set-up table for 2LIS_03_BF.
Following is the screenshot of the same.
If I check in ST22, I get following,
I could fill the setup table for other datasource 2LIS_03_BX without any problem.
Please suggest.Hi,
Can you try filling the setup table data for that range in background?
Sometimes because of huge data that you are trying to fill it might through you a dump. So please execute it in background and see if it works?.
But still can't really say what that dump tells from what you attached.
Thanks,
Sathya -
Problem while filling the Setup Table for the DS 2LIS_02_SCL.
Hi All,
When I am trying to fill the Setup table for the DataSource 2LIS_02_SCL and only for one specific Purchase Order, it is showing me a message like
u201CDataSource 2LIS_02_ITM contains data still to be transferredu201D
I have deleted the Setup Table and I want to delete the entries from SM13, but I do not have Authorization.
Also, here I am trying to fill the Setup Table for 2LIS_02_SCL and not for 2LIS_02_ITM, but the message displayed above is showing as 2LIS_02_ITM DataSource. I think the Setup Table will be same for both the DataSources.
Waiting for your valuable inputs.
Thanks in Advance.Hi,
When you want to fill the setup tables first you need to delete setup tables to avoid the duplicate entires in setup tables ( you can delete the setup tables by using t.code LBWG with application no is 02)
In your case, the data souce is 2LIS_02_SCL for purchasing.
when you want to delete the setup tables by using t.code LBWG with 02 application no it will delete all the purchasing related data from all the data sources like
2LIS_02_SCL
2LIS_02_ITM
Before the deletion of setup tables you need to clear the delta Queues and stop the V3 jobs, which loads the data to Delta Queues (RSA7) and Update tables(LBWQ).
you need to run the V3 jobs manually by using LBWE > Job control > and schedule the jobs until the delta queues will get 0 records. that means no data will be available in RSA7 and LBWQ
go to SM37 to see the jobs LIS-BW-VB_APPLICATION_02,
once the delta queues gets 0 records by running V3 Jobs manullay.
Then remove the released state jobs > remove from schedule means delete the jobs in LBWE > Go to job control > you can delete the released jobs.
Becuase No postings to be done in application tables, while running setuptable filling you should take some down time to fill the setup tables.( OLI*BW) *=Application number.
Once you clear the Queues and delete the v3 jobs, then you need to fill the setup tables after deletion of setup tables.
once you fill the setup tables , by running intialization to BW side the delta Queue is formed for the data source in R3 side
Now the postings can be done in R3 side, so you need schedule back the V3 jobs, which you already delted from LBWE to load the data from application tables to RSA7 or LBWQ.
I hope this may help yoou.
Regards.
Rambabu
Edited by: Rambabu velanati on Jun 9, 2010 4:41 PM
Edited by: Rambabu velanati on Jun 9, 2010 4:52 PM -
I am installing SQL Server 2012 Developer (from ISO image written on DVD), my machine has Windows 7 (Edit: Windows 7 with service pack 1) on it. This machine already has SQL Express and SQL 2008 R2 Express installed in it.
On running 2012 setup it goes fine from Setup Support Rules to Installation Progress. In Installation Progress after some progress installation fails.
Windows show the following components couldn't installed:
Managment Tools Complete Failed. Client Tools Connectivity Failed. Client Tools SDK Failed. Client Tools Backwards Compantibility Failed. Managment Tools Basic Failed. SQL Server Data Tools Failed. Reporting Services -Native Failed. Database Engine
Services Failed. Data Quality Services Failed. full-Text and Semantic Extractins for Search Failed. SQL Server Replication Failed. Integration Services Failed. Analysis Services Failed. SQL Client Connectivity SDK Failed.
In detail for failure of every component it provide these details:
Action required:
Use the following information to resolve the error, and then try the setup process again.
Feature failure reason:
An error occurred for a dependency of the feature causing the setup process for the feature to fail.
In summary log file it provide the following details:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068643839
Start time: 2012-07-31 16:23:37
End time: 2012-07-31 16:33:32
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Adv_SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for Conn: Use the following information to resolve the error, and then try the setup process again.
Next step for SDK: Use the following information to resolve the error, and then try the setup process again.
Next step for BC: Use the following information to resolve the error, and then try the setup process again.
Next step for SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for BIDS: Use the following information to resolve the error, and then try the setup process again.
Next step for RS: Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for DQ: Use the following information to resolve the error, and then try the setup process again.
Next step for FullText: Use the following information to resolve the error, and then try the setup process again.
Next step for Replication: Use the following information to resolve the error, and then try the setup process again.
Next step for IS: Use the following information to resolve the error, and then try the setup process again.
Next step for AS: Use the following information to resolve the error, and then try the setup process again.
Next step for SNAC_SDK: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: Haansi-PC
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
SQL Server 2005 SQLEXPRESS MSSQL.1
Database Engine Services 1033 Express Edition
9.4.5000 No
SQL Server 2005 SQLEXPRESS MSSQL.1
SQL Server Replication 1033 Express Edition
9.4.5000 No
SQL Server 2005 SQLEXPRESS MSSQL.1
SharedTools 1033
Express Edition 9.4.5000 No
SQL Server 2005
Tools 1033
Express Edition 9.4.5000 No
SQL Server 2005
ToolsClient 1033
Express Edition 9.4.5000 No
SQL Server 2005
ToolsClient\Connectivity 1033 Express Edition
9.4.5000 No
SQL Server 2008 R2 SQLSERVER08EXPR2 MSSQL10_50.SQLSERVER08EXPR2 Database Engine Services 1033
Express Edition 10.50.1617.0 No
SQL Server 2008 R2 SQLSERVER08EXPR2 MSSQL10_50.SQLSERVER08EXPR2 SQL Server Replication 1033
Express Edition 10.50.1617.0 No
SQL Server 2008 R2
Management Tools - Basic 1033 Express Edition
10.50.1617.0 No
SQL Server 2012
LocalDB 1033
Express Edition 11.0.2318.0 No
SQL Server 2012
Reporting Services - SharePoint
11.0.2100.60 No
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: F:\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLAgent$SS2012
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: TABULAR
ASSVCACCOUNT: NT Service\MSOLAP$SS2012
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Manual
ASSYSADMINACCOUNTS: PC\Haansi
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, BIDS, CONN, IS, BC, SDK, SSMS, ADV_SSMS, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SS2012
FTSVCPASSWORD: <empty>
HELP: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SS2012
INSTANCENAME: SS2012
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer$SS2012
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Manual
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SS2012
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: Haansi-PC\Haansi
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools SDK
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Server Data Tools
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Integration Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Analysis Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Client Connectivity SDK
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\SystemConfigurationCheck_Report.htmPlease help.
I did what you suggested, but, still got error message to install SQL server data tools: Here is the log.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068037632
Start time: 2014-09-29 15:05:38
End time: 2014-09-29 15:15:55
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SSDTBI_VS2012: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: MSBI
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured
SQL Server 2008 Management Tools - Basic
1033 Express Edition 10.0.1600.22 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Database Engine Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER SQL Server Replication 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Data Quality Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSAS11.MSSQLSERVER Analysis Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSRS11.MSSQLSERVER Reporting Services - Native 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Management Tools - Basic
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Management Tools - Complete
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools Connectivity
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools Backwards Compatibility
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools SDK
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 SQL Server Data Tools
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Integration Services
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Reporting Services - SharePoint
11.0.2100.60 No Yes
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: C:\9f7a58aa5d6d76ffe6be968a4ad339f5\x86\setup\
Installation edition: Express
Slipstream: True
SP Level 1
Patch Level: 11.1.3128.0
Product Update Status:
Success: KB 2674319, KB 2793634
Product Updates Selected for Installation:
Title: Service Pack 1
Knowledge Based Article: KB 2674319
Version: 11.1.3000.0
Architecture: x86
Language: 1033
Title: SQL Server 2012 SP1 GDR Product Update
Knowledge Based Article: KB 2793634
Version: 11.1.3128.0
Architecture: x86
Language: All
Update Source: MU
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SSDTBI_VS2012, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTANCEID: <empty>
INSTANCENAME: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: true
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\ConfigurationFile.ini
Detailed results:
Feature: SQL Server Data Tools - Business Intelligence for Visual Studio 2012
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: Microsoft Visual Studio Tools for Applications 2012
Component error code: 0x80044000
Component log file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\VSTA2012_LangsSupport_Cpu32_1.log
Error description: VS Shell 2012 installation has failed with exit code -2147205120.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3436.0&EvtType=VSTA2012_LangsSupport%40Install%400x-2147205120
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\SystemConfigurationCheck_Report.htm
Maybe you are looking for
-
I'm planning to build a new computer. I've got everything picked out except the case. I didn't expect the case to be the most difficult thing to choose. I'm looking at cases that support the XL-ATX mother board size (345mm x 264mm). Choices seem s
-
Nokia 701 (BELLE) problems
I have N8 and 701 both. There are some disappointments with 701. (1) Google Maps is NOT working in 701 (Belle), (2) While downloading Maps of India in Nokia Maps, the whole country map has to be downloaded at once for 701, whereas it can be downloade
-
Photoshop CC Vector Shape Fill Defaults issue
For some reason whenever I create a vector shape the default Fill is always Pattern instead of flat color. It used to default to whatever the last style I used in CS6, but for some reason in CC no matter what all shapes I make are default ugly bubbl
-
I have purchased my iphone in uae and now i m in india and my iphone hardware buttons are unreactive and i have to service or replace but i have lost my bill and on net there exist all info of my purchase can i service it in india without the bill
-
Sony HD Camcorder with hard drive-compatibility with a mac
I am considering purchasing a new Sony HD camcorder with an internal hard drive but it appears the hd format is not compatible with a mac. Does this sound correct and if so do we know how long til they can work together. Sony stated that mac would no