Monday, December 30, 2013
Saturday, December 21, 2013
"Error 0 loading DMCL32.DLL. Make sure the DLL and supporting files are in your path"
issue we have index plus on the client computer and we forgot install the dfc.
solution:
Make sure the DFC installed on the client computer where you have installed index plus client.
solution:
Make sure the DFC installed on the client computer where you have installed index plus client.
Wednesday, December 11, 2013
How to get the repository log: (on CONTENT SERVER MACHINE)
It is <repository_name>.log you can find
in <DOCUMENTUM_INSTALL_FOLDER>\dba\log .
How to get WDK logs: (on APP SERVER MACHINE)
By default, the log4j.properties (….found in
<webtop_home>\WEB-INF\classes) will contain..
log4j.rootCategory=WARN, file, stdout
log4j.category.MUTE=OFF
log4j.appender.stdout.threshold=ERROR
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d{ABSOLUTE} %5p [%t] %c - %m%n
log4j.appender.file.File=${user.dir}/documentum/logs/documentum.log
log4j.appender.file.MaxFileSize=10MB
log4j.appender.file.MaxBackupIndex=10
log4j.appender.file.Append=false
log4j.appender.file=org.apache.log4j.RollingFileAppender
log4j.appender.file.layout=org.apache.log4j.PatternLayout
log4j.appender.file.layout.ConversionPattern=%d{ABSOLUTE} %5p [%t] %c - %m%n
…we can leave it as such. The WDK log is the documentum.log.
Note: This will need an app server restart.
log4j.rootCategory=WARN, file, stdout
log4j.category.MUTE=OFF
log4j.appender.stdout.threshold=ERROR
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d{ABSOLUTE} %5p [%t] %c - %m%n
log4j.appender.file.File=${user.dir}/documentum/logs/documentum.log
log4j.appender.file.MaxFileSize=10MB
log4j.appender.file.MaxBackupIndex=10
log4j.appender.file.Append=false
log4j.appender.file=org.apache.log4j.RollingFileAppender
log4j.appender.file.layout=org.apache.log4j.PatternLayout
log4j.appender.file.layout.ConversionPattern=%d{ABSOLUTE} %5p [%t] %c - %m%n
…we can leave it as such. The WDK log is the documentum.log.
Note: This will need an app server restart.
How to get DFC trace: (on APP SERVER MACHINE)
The "dfc.properties"
file to use would be the one that Webtop uses. This should be found in the
<webapp deployment directory>/webtop/WEB-INF/classes folder. For
instance if you were using tomcat on windows you might find the file in the
following location
<webtop_home>\WEB-INF\classes.
Can you try the following settings in your dfc.properties for capturing the DFC trace
dfc.tracing.enable=true
dfc.tracing.include_rpcs=true
dfc.tracing.verbose=true
dfc.tracing.mode=standard
dfc.tracing.log.level = DEBUG
dfc.tracing.timing_style=date
dfc.tracing.date_column_width=12
dfc.tracing.date_format=yyyy-MM-dd hh:mm:ss.SSS
dfc.tracing.max_stack_depth=10
dfc.tracing.include_session_id=true
dfc.tracing.dir=${user.dir}/documentum/logs/
and then send us on the resultant trace file from <$TOMCAT_HOME>\documentum\logs.
You can reset dfc.tracing.enable=false when you have captured the trace
<webtop_home>\WEB-INF\classes.
Can you try the following settings in your dfc.properties for capturing the DFC trace
dfc.tracing.enable=true
dfc.tracing.include_rpcs=true
dfc.tracing.verbose=true
dfc.tracing.mode=standard
dfc.tracing.log.level = DEBUG
dfc.tracing.timing_style=date
dfc.tracing.date_column_width=12
dfc.tracing.date_format=yyyy-MM-dd hh:mm:ss.SSS
dfc.tracing.max_stack_depth=10
dfc.tracing.include_session_id=true
dfc.tracing.dir=${user.dir}/documentum/logs/
and then send us on the resultant trace file from <$TOMCAT_HOME>\documentum\logs.
You can reset dfc.tracing.enable=false when you have captured the trace
Subscribe to:
Posts (Atom)