Error Start Process Scheduler after configure Crystal Path

Hi All,
Kindly help me to solve this issue. I'd installed Peoplesoft HCM 9.2, Application Server and Process Scheduler run sucessfull but after i install Crystal Report Runtime Redistribute 2008 and configure crystal path (C:\Program Files(x86)\Business Objects\BusinessObjects Enterprise 12.0\win32_x86) i got this error when i try to start process scheduler
Booting admin processes ...
exec BBL -A :
process id=3164 ... started
1 process started
Attaching to active bulletin board.
> Attempting to boot ...
INFO: Oracle Tuxedo, Version 11.1.1.2.0 with VS2010, 64-bit, Patch Level (none)
Booting server processes ...
exec PSMSTPRC -0 ".\LOGS\stdout" -e ".\LOGS\stderr" -A -- -CD ORCL -PS PSNT -A start -S PSMSTPRC :
CMDTUX_CAT:1685: ERROR: Application initialization failure
CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
tmshutdown -qy

Hi all,
I am getting a similar message ...
failure: CORE3170: Configuration initialization failed: Error running init function load-modules: dlopen of /opt/SUNWwbsvr/plugins/passthrough/libpassthrough.so failed (ld.so.1: webservd: fatal: /opt/SUNWwbsvr/plugins/passthrough/libpassthrough.so: wrong ELF class: ELFCLASS64)
+/usr/bin/isainfo -kv+ gives *64-bit sparcv9 kernel modules*
I have also added the path of libpassthrough.so in LD_LIBRARY_PATH .
What can be the reason now ?
I had downloaded SP4. Does my webserver(sunone 6.1) also needs an update of service pack 4 then ? (It was installed about 2 months ago).

Similar Messages

Unable to start Process Scheduler

HRMS 9.1, PeopleTools 8.5.03, Oracle 11gR1, WebLogic 10.3, Windows XP Pro SP3.
I have app and web servers up and running on a single machine. I have configured a process scheduler but when I try to start it I get the following error:
CMDTUX_CAT:1685 ERROR: Application initialization failure
tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initializing user error handler
Shutting down all admin and server processes...
I believe I configured it properly. What could be causing this error?
Thanks...

Issue resolved. In the configuration, DBBIN was pointing to the wrong directory. Thanks

Cannot start BI services after configuring LDAP integration

Hi all,
After configuring LDAP integration with OBIEE , I have stopped all BI services and started again. It throws following error:
<Nov 24, 2012 2:05:16 PM AST> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see th
ption stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to
ore information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider>
<Nov 24, 2012 2:05:16 PM AST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializatio
tion: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root c
If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps
ception: [PolicyUtil] Exception while getting default policy Provider
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception
trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more in
ion. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1398)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsRuntimeException: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provid
        at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:293)
        at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)
        at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider
        at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:899)
        at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)
        at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)
        at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        Truncated. see log file for complete stacktrace
Caused By: java.security.PrivilegedActionException: oracle.security.jps.JpsException: [PolicyUtil] Unable to obtain default JPS Context!
        at java.security.AccessController.doPrivileged(Native Method)
        at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:844)
        at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)
        at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)
        at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)
        Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsException: [PolicyUtil] Unable to obtain default JPS Context!
        at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:860)
        at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:844)
        at java.security.AccessController.doPrivileged(Native Method)
        at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:844)
        at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)
        Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.service.idstore.IdentityStoreException: JPS-00056: Failed to create identity store service instance idstore.ldap.
er:idstore.ldap. Reason: oracle.security.jps.JpsRuntimeException: JPS-00027: internal error You configured a generic WLS LDAPAuthenticator.
The identity store type cannot be determined. Please choose an LDAP Authentication provider that matches your LDAP server.
        at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getIdStoreConfig(LdapIdentityStoreProvider.java:195)
        at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.access$300(LdapIdentityStoreProvider.java:70)
        at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance(LdapIdentityStoreProvider.java:242)
        at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:114)
        at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:70)
        Truncated. see log file for complete stacktrace
>
<Nov 24, 2012 2:05:16 PM AST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Nov 24, 2012 2:05:16 PM AST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Nov 24, 2012 2:05:16 PM AST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
D:\OraHome\Middlleware>I was not able to login to console since admin server not getting started.
Kindly help me to overcome this issue.
Thanks,
Haree

Thanks for the reply Veeravalli.
I have stoped the services and delete the config.lok file then edited the config.xml file under *%MW_HOME%\user_projects\domains\bifoundation_domain\config* . Then started the BI services. Now its working fine.
Thanks,
Haree

Error while processing dimension after add or delete property

Hi Experts,
I use BPC for MS SP6 with SQL Server 2008. I detected a problem while processing dimension after add or delete property.
The error message is: u201CMemory error: Allocation failure : Not enough storage is available to process this command. Error Code = 0x8007000E, External Code = 0x00000000.u201D
I tried to truncate and drop dimension tables and process dimension again, and it doesnu2019t work.
Any idea?
Thanks a lot for your support!
Albert

Hi Sorin,
Yestarday in the afternoon, we added a Property at another Dimension, and we continued having the same problem: we had errors when processing that dimension, but after restarting the server, we can process dimension.
Looking at the Event Viewer, at 'OutlookSoft log' environment, the following error appears:
<<
3/28/2011 6:57:15 PM
ModuleName : Olap9Manager - DeleteDimension
Message : Error Code = 0x8007000E, External Code = 0x00000000:.
Error Code = 0x8007000E, External Code = 0x00000000:.
Error Code = 0x8007000E, External Code = 0x00000000:.
Stack :    at Microsoft.AnalysisServices.AnalysisServicesClient.SendExecuteAndReadResponse(ImpactDetailCollection impacts, Boolean expectEmptyResults, Boolean throwIfError)
   at Microsoft.AnalysisServices.AnalysisServicesClient.Alter(IMajorObject obj, ObjectExpansion expansion, ImpactDetailCollection impact, Boolean allowCreate)
   at Microsoft.AnalysisServices.Server.Update(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
   at Microsoft.AnalysisServices.Server.SendUpdate(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
   at Microsoft.AnalysisServices.MajorObject.Update(UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings)
   at Microsoft.AnalysisServices.MajorObject.Update(UpdateOptions options)
   at Osoft.Services.Platform.YukonAdmin.Olap9Manager.DeleteDimension(String strAppset, String strDimension, String strCube, String dimTablePrefx, Boolean bDeleteFromDB, String& strMsg, Boolean bOnlySharedDim)
>>
Any idea in order to identify the root cause?
Thanks in advance,
Albert

"URGENT"Infopackage load error in process chian after upgrade

Hi Gurus,
We have a strange issue in one of the process chain after upgrade from 3.5 to NW 2004s. In a process chain we have 5 info packages, 3 in parallel as they load data in 3 different cubes and 2 in series after successful completion of info packages on top.
Now the process chain shows red info package with error message Last delta upload not yet completed. Cancel
When we check the RSMO, we find all the 3 loads on top finish successfully while in process chain log display as error at info package with above error message and process chain never advances. Actually loads finish successfully but process chain shows error in info package.
When we investigated further, the request ID in failed info package in process chain shows different ID which never loaded in cube but data load takes place successfully using different request ID(checked in RSMO and request in cube).
I suppose the process chain trigger the info package load twice simultaneously, one load get successful and second load request failed in log as first one is runningthis is my guess
Please help me as this is an urgent issue.
Regards,
Anil

Hi All,
We fond the root cause of the error message. Actually when we trigger the process chain, the info packages loads get triggered twice after an interval or around 2 minutes.
Here if zero records are loaded then second request ( after 2 min) get loaded too with zero records but if first request is loading some records then second request will find the data load still running and will throw error as last delta still not finished.
Have you seen this scenario before?
Regards,
Anil

Error starting the SOAMANAGER for Configuration

Hi fellows,
I've created a web service from a RFC. When I tried to start the SOAMANAGER for configuration to create the an endpoint I've got the error bellow:
"Invalid index 1 when setting lead selection; context node: MAIN.1.NODE_SEARCH_TABLE"
I tried to acess the SOAMANAGER transaction to find the service description created. I found it but when I tried to create the endpoint I got the errors:
"Error: Error when reading variant "ZWS_TESTE" of servicedefinition "ZWS_TESTE": An exception with the type CX_SY_REF_IS_INITIAL oc "
And
"No service/endpoint selected"
Someone knows what am I missing?

Hi Douglas,
While searching the service defintion in Soamanager i get the error.
"Error: Error when reading variant "ZSAPCONNECTORWEBSERVICE" of servicedefinition "ZSAPCONNECTORWEBSERVICE": An exception with the type CX_SY_REF_IS_INITIAL oc ".
How to solve this

Error in Process status after confirmation

Hi,
when we post confirmation in SRM for a particular PO it is showing the status as error in process.how can i check what is the probelm assocoiated with this confirmation.
I went to Rz20 and got the Idoc.but when i tried to process it manually in WE19.it shows partner profile not maintained
can any one suggest me what needs to be done
regards
subbu

Hi Can you reproduce the same error in development?
if so you can easily finda problem.
hope it may be error in process state in confirmation.
if you recreate this it helps.
1. error in process
2. again to create confirm - posted in a backend.
it may or may not be isolated error. try to replicate in development with same data.
muthu

Error starting HTTP right after a success install

I installed enterprise IAS 9i on Red hat 6.1. The installation is successful. And I did the post-installation steps as in the document, such as set up the PATH. However, when I try to start HTTP or HTTP with SSL, it gives me the following error:
Syntax error on line 1 of /home/ias/OraHome1/Apache/Apache/conf/mod__ose.conf:
Cannot load /home/ias/OraHome1/Apache/Apache/libexec/libjipa8i.so into server: /home/ias/OraHome1/lib/libwtc8.so: undefined symbol: LhtArbRemove
/home/ias/OraHome1/Apache/Apache/bin/apachectl start: httpd could not be started.
My ORACLE_HOME is /home/ias/OraHome1. Any idea how to solve it? Lots of thanks.

I have similiar problem on AIX. My message is as follows:
Syntax error on line 4 of /u03/app/oracle/product/ias9i/Apache/modplsql/cfg/plsql.conf:
Cannot load /u03/app/oracle/product/ias9i/Apache/modplsql/bin/modplsql.so into server: dlopen: /u03/app/oracle/product/ias9i/Apache/modplsql/bin/modplsql.so: (...)
Please let me know about solution.
best regards
Krzysztof Jungowski

Error Starting Certificate Authority after upgrading in place from Server 2003 Enterprise (32 bit) to Server 2008 Enterprise (32 bit).

Hope this is the place to seek help with Active Directory Certificate Services. We recently upgraded in place an issuing CA in our lab from 2003 to 2008 and the upgrade of the OS was successful but the CA service now will not start.
The error is:
Error 0xc8000222 (ESE: -546)
More info. We did stop the CA service prior to doing the upgrade.

Answering my own question with the hopes to help someone else.
The problem has something to do with the logs for the certificate database. There is some sort of a format conflict after upgrading to 2008.
To get around this error, and get the Certificate Authority service to start, remove all the logs from the C:\Windows\system32\CertLog directory that should be where your .edb database file lives, leave the database file there
This worked for us on three of four of our CA servers, the other one had a database that went down in a dirty state, so we had to use ESEUTIL utility to fix the database.
NOTE: there is no ESEUTIL utility on the CA servers, so we had to copy our database to an Exchange server in our test lab, then run ESEUTIL /MH to see what the Status is, it may say Dirty or Clean, then we ran ESEUTIL / P (P for Repair, go figure I know
right) anyway that fixed the database, so we copied it back over to the CA and started the service
hope this helps some of you out, we have a case opened with Microsoft Technical Support on this issue and will update this thread with their feedback as well once they get back to us (it has been a week already)

Errors starting web server after patch 6

I just applied 2005Q4 Patch 6 to the Access Manager, redeployed the web apps using amsilent and when I restart the Sun One Web Server 6.1SP8 there's a stack trace. How can I troubleshoot some of these errors and figure out what's wrong? It appears a problem with AuthD.java:720 (see below).
----- Root Cause -----
java.lang.NullPointerException
        at com.sun.identity.authentication.UI.LoginLogoutMapping.init(LoginLogoutMapping.java:71)
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:921)
        at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
        at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3528)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:3810)In the /var/opt/SUNWam/debug/amAuth file is an error:
10/31/2007 09:11:51:597 AM CST: Thread[main,5,main]
10/31/2007 09:11:51:599 AM CST: Thread[main,5,main]
Directory Host: doid.tcpip.com
Directory PORT : 636
10/31/2007 09:11:51:600 AM CST: Thread[main,5,main]
Session store using null
10/31/2007 09:11:51:602 AM CST: Thread[main,5,main]
AuthD initializing
10/31/2007 09:11:51:657 AM CST: Thread[main,5,main]
ERROR: AuthD failed to get session service instance
10/31/2007 09:11:51:658 AM CST: Thread[main,5,main]
ERROR: AuthD init()
java.lang.NullPointerException
        at com.sun.identity.authentication.service.AuthD.initAuthSessions(AuthD.java:720)
        at com.sun.identity.authentication.service.AuthD.<init>(AuthD.java:229)
        at com.sun.identity.authentication.service.AuthD.getAuth(AuthD.java:488)
        at com.sun.identity.authentication.UI.LoginLogoutMapping.init(LoginLogoutMapping.java:71)
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:921)
        at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
        at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3528)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:3810)
        at com.iplanet.ias.web.WebModule.start(WebModule.java:260)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
        at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
        at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
        at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
        at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
        at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)

look in to your amNaming debug file, most likely the AM is not able to connect to the DS or the platform service does not have the right protocol/port of the container

Mac Mini won't start with scheduler after power loss

Hello,
I have a Mac Mini here. It is configured to start at a certain time (say 1:00 AM). In the evening I shut down the Mac Mini and power off the socket where it is connected. In the morning I switch on the power socket and the Mac Mini is not starting.
When I do the same thing with an iMac everything works. The iMac will start because he missed the 1:00 AM.
I checked this with the current Mac Mini MC815D/A: here it works again!
So, what is wrong with my Mac Mini? I have this model:
APPLE #MAC MINI 2.4GHz (MC270LL/A)
Model No: A1347 (EMC 2364)
Model ID: Macmini 4,1
Can this be verified my some other user?
I use the latest firmware, and this behaviour shows up on several OSes (Snow Leopard, Lion and Mountain Lion)
Best regards
Matthias

Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, then move these files to the Desktop.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
/Users/YourUserName/Library/Preferences/com.apple.systempreferences.plist
/Library/Preferences/SystemConfiguration/com.apple.PowerManagement.plist
/Library/Preferences/SystemConfiguration/com.apple.AutoWake.plist
(Then Trash the original of these last two, as "moving" them only copies them.)
Then reboot once more.

Access denied errors in domain logs after configuring Ldap and restricting access to users

Hi Experts,
I'm getting access denied errors in my domain logs , this log is written continiously ..Has any one encountered the same issue and fixed this?
####<Sep 2, 2014 2:30:07 PM EDT> <Error> <Default> <ftizsldmwapp001.ftdc.cummins.com> <AdminServer> <[ACTIVE] ExecuteThread: '27' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <096a131bdb6c126e:6cecae89:14834848020:-8000-0000000000009bc8> <1409682607304> <J2EE JMX-46335> <MBean attribute access denied.
MBean: EMDomain:EMTargetType=j2ee_application,name=em,type=EMIntegration,Application=em
Getter for attribute HostName
Detail: Access denied. Required roles: Admin, Operator, Monitor, executing subject: principals=[]
TIA,
-Karthik

Hi Experts,
I'm getting access denied errors in my domain logs , this log is written continiously ..Has any one encountered the same issue and fixed this?
####<Sep 2, 2014 2:30:07 PM EDT> <Error> <Default> <ftizsldmwapp001.ftdc.cummins.com> <AdminServer> <[ACTIVE] ExecuteThread: '27' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <096a131bdb6c126e:6cecae89:14834848020:-8000-0000000000009bc8> <1409682607304> <J2EE JMX-46335> <MBean attribute access denied.
MBean: EMDomain:EMTargetType=j2ee_application,name=em,type=EMIntegration,Application=em
Getter for attribute HostName
Detail: Access denied. Required roles: Admin, Operator, Monitor, executing subject: principals=[]
TIA,
-Karthik

Error starting process

Hi,
I've created a process that I can finely trigger from web services navigator as well as from SOAPUI.
However, this process has to be triggered by a JEE client (non-SAP) and it is not working propertly.
I've checked the xml request sent from SOAPUI and from this specifc client and they slightly differ (see below).
Any help on finding a way to make my SAP BPM process compatible with this Java client would be appreciated.
The other way around (changing the request sent by the client) is not possible because of its vendor.
This SOAP envelope works (SOAPUI's):
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:sol="http://vetta.com/Solicitacao"
xmlns:com="http://vetta.com/ComprasCorporativas/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SOAP-ENV:Header/>
<SOAP-ENV:Body>
<com:CriarSolicitacao>
<in>
<sol:nomeSolicitante>Marcos123</sol:nomeSolicitante>
This SOAP envelope does not work (JEE client's):
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SOAP-ENV:Body>
                               <CriarSolicitacao xmlns="http://vetta.com/ComprasCorporativas/">
                                               <in xmlns="http://vetta.com/Solicitacao">
                                                               <nomeSolicitante>Marcos</nomeSolicitante>
                                                               <codigo>123456</codigo>
Best regards,
Ricardo Giacomin

Sorry, I forgot to mention the problem...
In fact, the process is triggered but all web service parameters are null.
For the beforementioned request (excerpt below), params nomeSolicitante, codigo, etc (all elements of complex type Solicitacao). are null when the process is triggered..
<in xmlns="http://vetta.com/Solicitacao">
<nomeSolicitante>Marcos</nomeSolicitante>
<codigo>123456</codigo>
Regards,
Ricardo Giacomin

I am getting the below error while bringing up the Process Scheduler error

Hello ,
I am getting the below error while bringing up the Prcs Scheduler.
Cannot open message catalog TMADMIN_CAT
Starting Process Scheduler Server PSNT for Database FSUAT ...
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 752; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
INFO: BEA Tuxedo, Version 8.1, 32-bit, Patch Level 192
NLS:4: Cannot open message catalog LIBTUX_CAT, set 1, num 1571; check TUXDIR=C:\
bea\Tuxedo8.1, LANG=English_United States.1252
NLS:4: Cannot open message catalog LIBTUX_CAT, set 1, num 1570; check TUXDIR=C:\
bea\Tuxedo8.1, LANG=English_United States.1252
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 793; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
exec BBL -A :
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 820; check TUX
DIR=C:\bea\Tuxedo8.1, LANG=English_United States.1252
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 801; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
exec PSDSTSRV -p 1,600:1,1 -sPostReport -- -C psprcs.cfg -CD FSUAT -PS PSNT -A s
tart -S PSDSTSRV :
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 1685; check TU
XDIR=C:\bea\Tuxedo8.1, LANG=English_United States.1252
tmboot: NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 827; check TUX
DIR=C:\bea\Tuxedo8.1, LANG=English_United States.1252
tmshutdown -y
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 753; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 916; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 907; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 936; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 948; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 775; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
Please suggest.

Duplicate thread :
Re: I am getting the attached error while bringing up the Prcs Scheduler
Nicolas.

Process scheduler

Hi,
I created and configured process scheduler through psadmin.exe and getting error when tried to start it......
PeopleSoft Process Scheduler Administration
1) Start a Process Scheduler Server
2) Stop a Process Scheduler Server
3) Configure a Process Scheduler Server
4) Create a Process Scheduler Server Configuration
5) Delete a Process Scheduler Server Configuration
6) Edit a Process Scheduler Configuration File
7) Import an existing Process Scheduler Configuration
8) Show Status of a Process Scheduler Server
9) Kill a Process Scheduler Server
10) Clean IPC resources of a Process Scheduler Domain
q) Quit
Command to execute (1-10, q) : 1
Database list:
1) HC
Select item number to start: 1
No Archive subdirectory, creating it...
No psprcs.cfg in the Archive subdirectory, creating it...
Installing PeopleSoft ODBC driver and Crystal libraries ...
PeopleSoft ODBC Driver installed.
Registering nVision...
PeopleSoft nVision registered.
Starting Process Scheduler Server PSNT for Database HC ...
Booting all admin and server processes in C:\PT8.49\appserv\prcs\HC\PSTUXCFG
INFO: BEA Tuxedo, Version 9.1, 32-bit, Patch Level 036
INFO: Serial #: 650522264137-2065448083901, Expiration NONE, Maxusers 1000000
INFO: Licensed to: Oracle-Peoplesoft-ISV
Booting admin processes ...
exec BBL -A :
process id=3280 ... Started.
Booting server processes ...
exec PSMSTPRC -A -- -C psprcs.cfg -CD HC -PS PSNT -A start -S PSMSTPRC :
CMDTUX_CAT:1685: ERROR: Application initialization failure
tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error ha
ndler
tmshutdown -y
Shutting down all admin and server processes in C:\PT8.49\appserv\prcs\HC\PSTUXC
FG
Shutting down server processes ...
Shutting down admin processes ...
Server Id = 0 Group Id = VIPUL-187A83D08 Machine = VIPUL-187A83D08:
shutdown succeeded
1 process stopped.
thanks in advance
Vipul

PT = 8.49
OS = Win 2003
Logs under "%PS_HOME%/appserv/prcs/HC directory"
*1)- file name = MSTRSCHDLR_1207.LOG*
PSMSTPRC.2388 (0) [12/07/09 18:23:45](0) PeopleTools Release 8.49 (WinX86) starting
PSMSTPRC.2388 (0) [12/07/09 18:23:45](0) Cache Directory being used: C:\PT8.49\appserv\prcs\HC\CACHE\CACHE\PSMSTPRC_102\
PSMSTPRC.2388 (0) [12/07/09 18:23:45](0) Server failed to start
*2)- file name = TUXLOG.120709*
181957.VIPUL-187A83D08!tmloadcf.3912.1200.-2: 12-07-2009: Tuxedo Version 9.1, 32-bit
181957.VIPUL-187A83D08!tmloadcf.3912.1200.-2: CMDTUX_CAT:879: INFO: A new file system has been created. (size = 880 512-byte blocks)
182003.VIPUL-187A83D08!tmloadcf.3912.1200.-2: CMDTUX_CAT:871: INFO: TUXCONFIG file C:\PT8.49\appserv\prcs\HC\PSTUXCFG has been created
182246.VIPUL-187A83D08!tmloadcf.3536.2376.-2: 12-07-2009: Tuxedo Version 9.1, 32-bit
182246.VIPUL-187A83D08!tmloadcf.3536.2376.-2: CMDTUX_CAT:879: INFO: A new file system has been created. (size = 880 512-byte blocks)
182252.VIPUL-187A83D08!tmloadcf.3536.2376.-2: CMDTUX_CAT:871: INFO: TUXCONFIG file C:\PT8.49\appserv\prcs\HC\PSTUXCFG has been created
182345.VIPUL-187A83D08!BBL.2052.3804.0: 12-07-2009: Tuxedo Version 9.1, 32-bit, Patch Level 036
182345.VIPUL-187A83D08!BBL.2052.3804.0: LIBTUX_CAT:262: INFO: Standard main starting
182345.VIPUL-187A83D08!PSMSTPRC.2388.892.-2: 12-07-2009: Tuxedo Version 9.1, 32-bit
182345.VIPUL-187A83D08!PSMSTPRC.2388.892.-2: LIBTUX_CAT:262: INFO: Standard main starting
182345.VIPUL-187A83D08!PSMSTPRC.2388.892.-2: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
182345.VIPUL-187A83D08!tmboot.2556.3812.-2: 12-07-2009: Tuxedo Version 9.1, 32-bit
182345.VIPUL-187A83D08!tmboot.2556.3812.-2: tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
182348.VIPUL-187A83D08!BBL.2052.3804.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
File name = PSPRCS.CFG
[Startup]
;=========================================================================
; Database Signon settings
;=========================================================================
DBName=HC
DBType=MICROSFT
UserId=PS
UserPswd=sxaYMM0Crai26F3R14m0+JWdoXJsSHVovUxlKDaxFDM=
ConnectId=people
ConnectPswd=kyD3QPxnrag=
ServerName=PSNT
[Database Options]
;=========================================================================
; Database-specific configuration options
;=========================================================================
; Please see Chapter "Tuning and Administration", in
; Sybase Installation and Administration Guide for details
SybasePacketSize=512
; Please see Chapter "Tuning and Administration", in
; Oracle Installation and Administration Guide for details
UseLocalOracleDB=0
;ORACLE_SID=
OracleDisableFirstRowsHint=0
; Dynamic change allowed for EnableDBMonitoring (PSAESRV Only)
EnableDBMonitoring=1
[Trace]
;=========================================================================
; Trace settings
;=========================================================================
; PeopleTools trace file (NT only, ignored on UNIX)
TraceFile=%PS_SERVDIR%\logs\PeopleTools.trc
; SQL Tracing Bitfield
; Bit Type of tracing
; 1 - SQL statements
; 2 - SQL statement variables
; 4 - SQL connect, disconnect, commit and rollback
; 8 - Row Fetch (indicates that it occurred, not data)
; 16 - All other API calls except ssb
; 32 - Set Select Buffers (identifies the attributes of columns
; to be selected).
; 64 - Database API specific calls
; 128 - COBOL statement timings
; 256 - Sybase Bind information
; 512 - Sybase Fetch information
; 1024 - SQL Informational Trace
; Dynamic change allowed for TraceSql and TraceSqlMask
TraceSQL=0
; PeopleCode Tracing Bitfield
; Bit Type of tracing
; 1 - Trace Evaluator instructions (not recommended)
; 2 - List Evaluator program (not recommended)
; 4 - Show assignments to variables
; 8 - Show fetched values
; 16 - Show stack
; 64 - Trace start of programs
; 128 - Trace external function calls
; 256 - Trace internal function calls
; 512 - Show parameter values
; 1024 - Show function return value
; 2048 - Trace each statement in program (recommended)
; Dynamic change allowed for TracePC
TracePC=0
; AE Tracing Bitfield
; Bit Type of tracing
; 1 - Trace STEP execution sequence to AET file
; 2 - Trace Application SQL statements to AET file
; 4 - Trace Dedicated Temp Table Allocation to AET file
; 8 - not yet allocated
; 16 - not yet allocated
; 32 - not yet allocated
; 64 - not yet allocated
; 128 - Timings Report to AET file
; 256 - Method/BuiltIn detail instead of summary in AET Timings Report
; 512 - not yet allocated
; 1024 - Timings Report to tables
; 2048 - DB optimizer trace to file
; 4096 - DB optimizer trace to tables
TraceAE=0
; Performance Monitor Tracing Bitfield
; Bit Type of tracing
; 1 - Trace All performance monitor agent activity
TracePPM=0
[Process Scheduler]
;=========================================================================
; General settings for the Process Scheduler
;=========================================================================
PrcsServerName=PSNT
DBBIN=c:\Program Files\Microsoft SQL Server\80\Tools\Binn
; Max number of attempt to try reconnect to the database when the connection
; is lost
Max Reconnect Attempt=12
; Interval in seconds between attempts to reconnect
Reconnection Interval=300
; This parameter indicates the duration in minutes allotted before
; Tools' security module will timeout authenticating a process released
; by Process Scheduler. The timer starts from the time Process Scheduler
; initiates the request
Authentication Timeout=5
; This allows for dynamic changes to certain setting without having to reboot
; the domain. The settings that can be dynamically changed are: Recycle Count,
; Consecutive Service failures, Trace SQL, Trace Mask SQL, TracePC,
; Log Fence, Enable DB Monitoring, and Enable Debugging.
; These settings are further identified by the "Dynamic change allowed for .."
; comment.
Allow Dynamic Changes=N
Log/Output Directory=C:\PT8.49\appserv\prcs\HC\log_output
; Log/Output Directory Extension Option
;An optional subdirectory structure that can be appended to the
;designated Log/Output Directory.
;Additional meta-string that can be used include
;Userid: %OPRID%
;Contentid: %REPORTID%
;Process Instance: %PRCSINSTANCE%
;Database Name: %DBNAME%
;Process Name: %PRCSNAME%
;Process Type: %PRCSTYPE%
;Scheduler Server Name: %SERVER%
;Current Date: %CURRDATE%
;Current Hour: %CURRHOUR%
;Job Name: %JOBNAME%
;Job Instance: %JOBINSTANCE%
; As an example for usage, %CURRDATE%\%CURRHOUR%
Output Directory Optional Extension=
; Logging detail level
; Level Type of information
; -100 - Suppress logging
; 0 - Status information
; 1 - Critical Information
; 2 - Errors
; 3 - Informational (default)
; 4 - Tracing Level 1
; 5 - Tracing Level 2
; Dynamic change allowed for LogFence
LogFence=3

Error Start Process Scheduler after configure Crystal Path

Similar Messages

Maybe you are looking for