ConfigEngine.bat fails on Windows Server 2008 R2 Enterprise 64-bit OS version

Technote (troubleshooting)


Problem

Example:


D:\WebSphere\wp_profile\ConfigEngine>configEngine.bat list-server-ports

Licensed Materials - Property of IBM

5724-E76, 5724-E77, 5655-M44

(C) Copyright IBM Corp. All Rights Reserved.



Running Configuration Engine task 'list-server-ports'

propertiesPath is ConfigEngine_temp.prop

rootDir is D:\WebSphere\wp_profile\ConfigEngine

Executing native2ascii with native encoding 'Cp1252':
ConfigEngine_temp.prop_ ->

ConfigEngine_temp_ascii.prop_

Native2ascii execution was successful!

Loading system properties from ConfigEngine_temp_ascii.prop_

ConfigEngine: setting system property server.root=D:/WebSphere/AppServer

ConfigEngine: setting system property
was.repository.root=D:/WebSphere/wp_profile/config

ConfigEngine: setting system property
JAVA_HOME=D:/WebSphere/AppServer/java

ConfigEngine: setting system property CellName=Labportal2

ConfigEngine: setting system property
ws.ext.dirs=D:/WebSphere/AppServer/java/lib;D:/WebSphere/AppServer/classes;D:/WebSphere/AppServer/lib;D:/WebSphere
/AppServer/installedChannels;D:/WebSphere/AppServer/lib/ext;D:/WebSphere/AppServer/web/help;D:/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime;./lib;./shared/app

ConfigEngine: setting system property jvmArgFor64bit=-D64bit.args=none

ConfigEngine: setting system property NodeName=Labportal2

ConfigEngine: setting system property local.node=Labportal2

ConfigEngine: setting system property was.root=D:/WebSphere/AppServer

ConfigEngine: setting system property
was.install.root=D:/WebSphere/AppServer

ConfigEngine: setting system property
cfg.trace=D:/WebSphere/wp_profile/ConfigEngine/log/ConfigTrace.log

ConfigEngine: setting system property local.cell=Labportal2

RegistrySynchronized: true

Registry already in sync

CELL: Labportal2

NODE: Labportal2

[03/15/11 13:22:40.028 HST] WSVR0801I

[03/15/11 13:22:42.856 HST] WKSP0500

Websphere:_Websphere_Config_Data_Type=Registry,_Websphere_Config_Data_Id
=cells/Labportal2|registry.xml#Registry_1300130222128,_WEBSPHERE_CONFIG_SESSION=
anonymous1300231360013

loaded registry from WAS: registry.xml

java.io.FileNotFoundException: base_dynamic.xml (Access is denied.)

at java.io.FileOutputStream.<init>(FileOutputStream.java:179)

at java.io.FileOutputStream.<init>(FileOutputStream.java:70)



Cause

A file listing revealed a permissions problem; note in this list we have registry.xml with Administrators auth which explains why fails.

D:\WebSphere\wp_profile\ConfigEngine>dir /A:/Q/S/P
 Volume in drive D is New Volume
 Volume Serial Number is 141E-B24F
 
 Directory of D:\WebSphere\wp_profile\ConfigEngine
 
03/14/2011  09:51 AM    <DIR>          BUILTIN\Administrators .
03/14/2011  09:51 AM    <DIR>          BUILTIN\Administrators ..
08/18/2010  07:35 AM            17,352 BUILTIN\Administrators base.xml
03/14/2011  09:47 AM            65,799 BUILTIN\Administrators base_dynamic.xml
08/19/2010  03:43 PM    <DIR>          BUILTIN\Administrators cisa
03/14/2011  09:48 AM    <DIR>          BUILTIN\Administrators config
03/14/2011  09:16 AM             4,520 BUILTIN\Administrators ConfigEngine.bat
03/14/2011  09:16 AM            11,549 BUILTIN\Administrators ConfigEngine.sh
03/14/2011  09:51 AM               834 LABPORTAL2\webadmin    ConfigEngine_temp.
prop_
03/14/2011  09:51 AM               834 LABPORTAL2\webadmin    ConfigEngine_temp_
ascii.prop_
03/14/2011  09:16 AM    <DIR>          BUILTIN\Administrators lib
03/14/2011  09:51 AM    <DIR>          BUILTIN\Administrators log
03/14/2011  09:51 AM    <DIR>          BUILTIN\Administrators properties
03/14/2011  09:48 AM           178,274 BUILTIN\Administrators registry.xml
03/14/2011  09:16 AM    <DIR>          BUILTIN\Administrators uninstall
08/19/2010  03:42 PM    <DIR>          BUILTIN\Administrators version
08/18/2010  07:35 AM    <DIR>          BUILTIN\Administrators was
               7 File(s)        279,162 bytes


Resolving the problem

Run the ConfigEngine.bat command by selecting “Command Prompt/Run as administrator”. Then you can the command successfully.


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Portal

Software version:

7.0.0.0, 7.0.0.1

Operating system(s):

Windows

Software edition:

Enable, Express, Extend, Server

Reference #:

1473919

Modified date:

2013-02-19

Translate my page

Machine Translation

Content navigation