[CS3] Method Generate for the object Index fails

Hello,
I will create an index in my VB script with InDesign CS3:
Set objIndex = docindex.Generate(indIndexDoc.Pages.Item(1),p)
The index is longer than one page.
I think this is the reason, when I get this error:
Runtime error -2147417851 (80010105)
Method "Generate" for the object "Index" fails
Thank you in advance!
Harald

I got this hint from Martin Fischer:
The problem is a special character in the topics.
Harald

Similar Messages

Call of the method START_ROUTINE of the class LCL_TRANSFORM failed; wrong type for parameter SOURCE_PACKAGE

Hi,
My DTP load failed due to following error.
Call of the method START_ROUTINE of the class LCL_TRANSFORM failed; wrong type for parameter SOURCE_PACKAGE
I don't think anything wrong with the following code as data loads successfully every day. Can any one check? What could be the issue?
METHOD start_routine.
*=== Segments ===
     FIELD-SYMBOLS:
       <SOURCE_FIELDS>    TYPE _ty_s_SC_1.
     DATA:
       MONITOR_REC     TYPE rstmonitor.
*$*$ begin of routine - insert your code only below this line        *-*
*   Fail safe which replaces DTP selection, just in case
     DELETE SOURCE_PACKAGE WHERE version EQ 'A'.
*   Fill lookup table for the ISPG
     SELECT p~comp_code m~mat_plant m~/bic/zi_cpispg
       INTO TABLE tb_lookup
     FROM /bi0/pplant AS p INNER JOIN /bi0/pmat_plant AS m ON
       p~objvers EQ m~objvers AND
       p~plant   EQ m~plant
     FOR ALL ENTRIES IN SOURCE_PACKAGE
     WHERE p~objvers   EQ 'A' AND
           p~comp_code EQ SOURCE_PACKAGE-comp_code AND
           m~mat_plant EQ SOURCE_PACKAGE-material.
     SORT tb_lookup BY comp_code material.
*$*$ end of routine - insert your code only before this line         *-*
   ENDMETHOD.

Hi,
Compare the data types of the fields in your table tb_lookup with the data types in your datasource. Most probably there is an inconsistency with that. One thing that I realize is that
I use the select statement in the format select ... from ... into... Maybe you need to change places of that, but I am not sure. You may put a break point and debug it with simulation.
Hope it gives an idea.
Yasemin...

SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT - Active Directory Security Group Discovery Agent reported warnings for 524 object(s). DDRs were generated for 0 object(s) that had warning(s) while reading non-critical properties.

Hi, can anyone help me troubleshoot the following please:
Active Directory Security Group Discovery Agent reported warnings for 524 object(s). DDRs were generated for 0 object(s) that had warning(s) while reading non-critical properties. DDRs were not generated for 524 object(s) that had warnings while reading
critical properties.
Possible cause: OU name or Security Group name may contain at least a Unicode character which has conversion problem between Unicode and your system ANSI locale(e.g. Korean characters in English System Locale). The site server might not have access to
some properties of this object. The container specified might not have the properties available.
Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information.
Does the error relate to 524 security groups? There are several invalid search paths listed in adsgdis.log, are these related?
Thanks,
Dale

You'll have to examine the log to determine exactly which objects its referring to. Although this is in the context of group discovery, group discovery still creates DDRs for computer objects within those groups so it could be either groups or computers.
This is not a search path issue though as it's clear that the discovery process found 524 different objects, but as stated, it could not properly read criticial properties of those objects and thus did not create DDRs for them.
As mentioned, reading the log in detail will list the objects individually and the reason it could not create a DDR for it.
Jason | http://blog.configmgrftw.com

OC4J 10.1.2 - No XPathFactory implementation found for the object model

Hello,
We are doing some maintenance on an old 10.1.2.3.0 container. The project has to be extended with a library built with xml-apis-1.3.03.jar. I know you will suggest a upgrade, but that is a no-go - sorry, since other projects also are running on this server. So I hope some of you remember or know how to avoid or replace the oracle xml parser.
It seems like it gets the wrong XPathFactory
XPathFactory#newInstance() failed to create an XPathFactory for the default object model: http://java.sun.com/jaxp/xpath/dom
with the XPathFactoryConfigurationException: javax.xml.xpath.XPathFactoryConfigurationException: No XPathFctory implementation found for the object model:
I have searched the documentation for 10.1.2 and everything relevant on the Internet for a solution, but i seems to non-trivial when dealing with oracle xml parser. We tried to put the jar-files (xml-apis-1.3.03.jar, xercesImpl-2.8.0.jar, xalan-2.6.0.jar) in the endorsed library under the jdk, and we have already added <web-app-class-loader search-local-classes-first="true" include-war-manifest-class-path="true"/> to our orion-web.xml.
I also know that the <shared-library> tag got introduced in 10.1.3 where you easily can replace the parser.
Any ideas on how to deal with this exception or comments to the interpretation on the exception are appreciated.
-MK

Hello,
You are correct, in OracleAS 10g (10.1.2), Oracle does not expose JMX MBean server.
OracleAS 10g R3 (10.1.3) is a J2EE 1.4 container will full support for JMX, and all the JSR-77 MBeans exposed. You can also create and register your own MBeans.
Could you give us the different requirements you have around JMX for your application?
Regards
Tugdual Grall

The Isolation Method property of the object you added has been set to read

Hai ,
when iam going to assign VC Iview to Page .facing strange issue
The Isolation Method property of the object you added has been set to read-only. The value must remain URL for the object to run in the page.
already for my vc iview isolation method properties set to URL .
Still iam facing this issue
any input to solve this isue
please any one brief me about isolation method property whts the use
Regards ,
venkat p

Hi ASR,
Please check page object is locked or not. if it locked then unlock it from system administraiton >> monitoring >> portal >>object locking. remove if page object is locked.
Refer to Page Editing : http://help.sap.com/saphelp_nw70/helpdata/en/a3/badf3d48b05d5ae10000000a11405a/frameset.htm
Hope it helps
Regards
Arun

Config/boot.rb:19: undefined method `gem' for main:Object (NoMethodError)

Hi,
does anybody know, how to fix this error:
config/boot.rb:19: undefined method `gem' for main:Object (NoMethodError)

Did you create this application with an older 1.1.x version of rails, then running it with a newer 1.2.x rails? Maybe you have upgraded your rails. Check your current rails version with 'script/about'.
You can freeze the rails version for your application. See this article:
http://wiki.rubyonrails.org/rails/pages/EdgeRails

SQL Server 2012 installation failure An error occurred for a dependency of the feature causing the setup process for the feature to fail.

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

Please 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

SCB indicator is missing or is not valid-No DME could be generated for the

Hi All,
Using transacttion F110,
vendor payments were generated. Payment run successful.
In 'Display Payment Run log',
Warning: Check whether a duplicate payment medium has been created
SCB indicator is missing or is not valid
No DME could be generated for the following documents
CoCd Payment document/Payment order
0100 2000199545
>
> Overview of the files generated (DME)
> Name / File name
> DME file (TemSe) - bank BK03 / DTA111128154701_3215
>> Error log / LISTFS / 0000093865
I have checked the document has SCB number stored.
please suggest.
Thanks and Regards
Reena

Hi Reena,
The error you have mentioned in the initial description is the error code F0265.
Regarding the error code F0265, this arises because the payment medium programs RFFO* look for the field bseg-landl and bseg-lzbzk to be filled.
These fields are necessary for Germany as the f1-help states and if they are missing, you receive these error messages f0265. Please have a look at note 23562 as well for more information.
Sometimes users forget to enter SCB indicator in the invoice document and thus it results in problem reported error messages
at the time of creating payment medium.
In this case either you can make the SCB indicator field "required" in the field status or create a validation rule for those invoices for which SCB indicator should be entered.
To derive SCB indicator automatically I think substitution rule could be of help too as a workaround.
Hope this helps.
Kind Regards
Soumya

Problem Instanciating BO - No default attribute defined for the object type

Hello Experts,
I am instanciating the BO BUS2038 to ZBUS2038 and when I click in u201Cto implementedu201D and follow u201Cto releasedu201D the message No default attribute defined for the object type is appearing!
Can anybody help, please?

Hello everyone,
it appears to me, that no one has a clue about the "default attribute" and is widely guessing what can be done about that.
I feel deeply sorry for that, Marcos.
At first: You don't really need to care about the missing default attribute. If it's missing, the object's instance key will be used instead. Skip the warning message.
Secondly: The default attribute is used to display the instance within the "Object links & Attachments" under the work item preview when using the SAP Business Workflow.
Thirdly: You can select any existing attribute of your business object type to be the default attribute, by navigating to the "Basic data" (it's the heat-icon within the object builder), use tab "Defaults" and use the Input Help on the field "Attribute".
There you'll go.
Best wishes,
Florin

Several idocs got generated for the PO transmission

Hi,
We have got a problem regarding the transmission of PO via email or idocs. While PO generates only one output type with NEU. there are several idocs and email (depending on the condition record for the vendor and purchasing organization) getting generated and are dispatched to the vendor. There should be only one idoc or email generated for the PO dispatching to vendor.
Did anyone of us get this problem in the past? Please share your experience with me and if you have any solution for the same.
Best regards,
Subhash

Hi BK,
Thanks for your answer but there is just one condition record for this vendor. The problem is that, there is only one successfully processed message type 'NEU" in the purchase order but multiple idocs or emails are generated within a timespan of few seconds/minutes. These multiple records can be seen is SOST list (in case of email) and WE02 (in case of idocs).
Thanks n BR,
Subhash

About report groups and read programs for the object EC_PCA_SUM

Hi Friends,
Hope every one is doing well..!
I've an issue with the report groups and read programs for the object EC_PCA_SUM. As we know that the report groups and read programs available for this object in the application customizing are used to analys the archived data.
That is these programs comes into picture after the archiving operation.
For more information, you can visit the below web site:
[http://help.sap.com/erp2005_ehp_03/helpdata/EN/e4/69f353b75a11d1b5850000e82debc6/frameset.htm]
Now, my question is how would I check the code for these analysing programs available for this object. I can't see this in SE38.
Thanks to reply for this..
Full marks will be awarded.
Regards,
Shamim

Hi Lakshman,
Thanks for the reply.
Hi Deiter,
You're right.
Your provided transaction "GR55" helped me to find out the program name for a particular group. However, these are just Write and Painter reports.
But can you please let me know the functionality of these report groups ?? what are these used for ???
Do we have these programs for other archiving objects like CO_ITEM,CO_ML_BEL,MM_MATBEL,CO_ORDER,
PP_PLAN,PP_BKFLUSH ??
More points will be awarded.
Thanks a lot.
Regards,
Shamim
Edited by: S H A M I M on Sep 19, 2008 3:19 PM

Attachment in the Services for the object (Transaction PA30)

Dear Friends
i have uploaded a file (from my desktop)using Services for the object in PA30 transaction for a particular personnel no. . The services for the object is just above the Create Icon in PA30 Transaction.
Now i would like to know where this file is being saved which was upload from my desktop . Later if i remove the file from my desktop even then i can see that file
still being there in the attachment when i click the Services for the object.
Please could any one let me know.
Regards
syamala

Hi,
Have a look at this thread.
attachment in PA30
Regards,
Manoj.

Table Maintenance Generator for the table "J_1ISTATECD"

Hi,
How to create Table Maintenance Generator for the table "J_1ISTATECD". Can anyone please explain the steps for this.
Thanks in advance....
Regards,
Sriram.

Hi Sriram,
-->Create view in SE11
-->Goto transcation SE11 ABAP Dictionary
-->Select View and type in the name of the view you want to create.
-->Press the Create button
-->In the dialog box that appears, choose Maintenance View
-->Select tables and fields for the view
-->Activate the view
or
-->Create view in SE11
-->Goto transcation SE11 ABAP Dictionary
-->enter table name
-->go to Utilities
-->select table maintainance Genarator
-->Enter single step
--> enter Function Group(all the code for Table mainaitenace is stored here)
-->eneter single step
-->enter Authorization gorup(we can restrict some user,s not tot update data)
Activate the view
function Group -->goto se37 -- > menu bar goto->create function group with five letters ..
add the same function group in table maintainenece generatoror enter the sane table name in Function group Place..
if you dont know the Authorization group ( not given by Function design) put &NA&
or if you want to know the maintainence View already exists go to table TSTCV
enter Table name you can get the view available for the table name..
Regards,
Prabhudas

Identification number for the object type H

Hello:
There is an infotype thats allow me to enter an identification number for the object type external person (H) in the training and event management module (PE)?. I was checking in the configuration and I dont find the solution for this issue.
I ask to myself if is necessary to create one infotype for this purpose?
I will appreciate your colaboration and the answer.
Thanks

Hi Vijay:
It is something similar to the infotipo 185 of object person type of the module PA. I need an identification document for external person (example: driver license)
Regards
CarlosZ

J1INQEFILE is not generating for the month of March 2011

Hi,
J1INQEFILE is not generating for the month of March 2011, we have executed Qefile from 01/01/2011 to 31/03/2011 then file is generating but March 2011 data is not available.
Problem is challans were updated in the month of April 2011 for March 2011 documents, When we executed J1INMIS report with Bank Challan status, documents are coming in the report.
As per our understanding Challan numbers and Bank Challan update should be done in the month of March 2011 but challans and Bank challans were updated in the April 2011.
Please suggest.
Thanks,
Ratnam

Hi Vara,
Please check following thing in the system.
1) When the Challan is created ( March month or April 2011)
2) When the Bank challn updated for the challans
3) If the Challan created in the April and generating returns for the month of March 2011.
4) Check in J1INMIS report for the month posting date 01.03.2011 to 31.03.2011, if the external Challan number is appearing or not for the documents.
5) If the Challan created in the April ask user to revere through J1INREV, and make Challan in the month of march 2011.
Problem will solve.
Thanks,
Ratnam.

[CS3] Method Generate for the object Index fails

Similar Messages

Maybe you are looking for