No Pacific Application Server instance (oepas1) in new OE11.

Hi,

Is the instance created in your WRKDIR after installation

No it wasn't.

Seems like the installation failed to create the instance. Can you please send openedge_tailor,openedge_tailor_stderr and tcman_create logs in $DLC/install location

openedge_tailor.log

info: command line options: -v -Z dev -M -O -X C:\OE11\OpenEdge\jdk -D C:\OE11\OpenEdge -W C:\OE11wrk\WRK  
info: Tailoring arguments: '-v -Z dev -M -O -X C:\OE11\OpenEdge\jdk -D C:\OE11\OpenEdge -W C:\OE11wrk\WRK'
info: running tailor functions( pasTailor pasoeTailor )
info: tailoring server installed at location: C:\OE11\OpenEdge\servers\pasoe
info: verifying server directories at: C:\OE11\OpenEdge\servers\pasoe
info: verifying server scripts at: C:\OE11\OpenEdge\servers\pasoe\bin
info: verifying server configuration files at: C:\OE11\OpenEdge\servers\pasoe\conf
info: resolving server home directory...

info: Begin tailoring core Progress Application Server
info: tailoring CATALINA_HOME in server scripts at: C:\OE11\OpenEdge\servers\pasoe\bin
info: updating PAS version
info: tailoring the server's installation platform
info: tailoring the servers network ports
info: updating tailoring time in pas_tailor.txt
info: tailoring JAVA_HOME configuration with - C:\OE11\OpenEdge\jdk
info: Tailoring Windows security is not supported

info: Begin tailoring OpenEdge plugin to Progress Application Server
info: verifying OpenEdge DLC and WRKDIR paths
info: verifying OpenEdge directories at: C:\OE11\OpenEdge\servers\pasoe
info: verifying OpenEdge scripts at: \bin
info: verifying OpenEdge configuration files at: C:\OE11\OpenEdge\servers\pasoe\conf
info: tailoring CATALINA_HOME in OpenEdge scripts at: C:\OE11\OpenEdge\servers\pasoe\bin
info: tailoring DLC in OpenEdge scripts at: C:\OE11\OpenEdge\servers\pasoe\bin
info: tailoring WRKDIR in OpenEdge scripts at: C:\OE11\OpenEdge\servers\pasoe\bin
info: updating Java configuration to use OpenEdge JDK/JRE: C:\OE11\OpenEdge\servers\pasoe\bin\javacfg.bat
info: tailoring OpenEdge lib extensions for version: 1.1.1
info: deploying the OEABL service web application
info: replacing default ROOT application with OpenEdge OEABL
info: deploying OEABL to web application ROOT
info: enabling the OpenEdge naming service
info: enabling the OpenEdge lifecycle service
info: The OpenEdge remote administration manager is already deployed
info: updated https protcol list in C:\OE11\OpenEdge\servers\pasoe\conf\catalina.properties - SSLv2Hello,TLSv1,TLSv1.1,TLSv1.2
info: The Tomcat remote administration manager is already deployed
info: Updating registered instances
info: Updating existing instances found in C:\OE11\OpenEdge\servers\pasoe\conf\instances.windows
info: No instances found

openedge_tailor_stderr.log

"empty file"

tcman_create.log

info: executing create Tomcat instance command
Exception: The term 'netstat' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
in createCmd at line :
Exiting with fatal exception condition

tcman_create_stderr.log

"empty file"

Looks like you may have an older version of Windows Powershell?  To verify the version you can open Windows Powershell and type (or cut and paste):

$PSVersionTable.PSVersion

I believe we need version Major version 4.  Please upgrade your Powershell version and the run this command from the "proenv" command window:

pasman create %WRKDIR%\oepas1

This should create the oepas1 instance you are expecting without having to reinstall.

Let us know how you do or if you have further questions or problems,

Roy

If it is not the powershell version problem, then I suspect it to be the with your user privileges on the machine  because it seems to be failing as "netstat" command could not  be run.  

I used Windows 7 Professional with administrator  privileges and run SETUP as 'administrator'.

There is no Windows Powershell in my computer.

Okay, as mentioned by Roy did you try to verify if your powershell version is more than 4

Powershell is required for PASOE.  Can you download the latest version from Microsoft and try again?

Thanks, Roy

Is your c:\windows\system32\ folder present in your PATH system variable?

You need to have powershell, please install powershell version 3 or above

C:\Users\isyed>powershell

Windows PowerShell

Copyright (C) 2012 Microsoft Corporation. All rights reserved.

PS C:\Users\isyed> $PSVersionTable.PSVersion

Major  Minor  Build  Revision

-----  -----  -----  --------

3      0      -1     -1

You might also want to check if your "netstat" is working correctly from your command prompt.

I've installed PowerShell 4 and created Pacific Server without reinstallation (pasman create %WRKDIR%\oepas1). Now I can move in my Telerik demo studies

community.progress.com/.../2437.webinar-modernize-your-existing-openedge-applications-with-kendo-ui.aspx

Thank you Roy, thank you Irfan.

Regards,

Andrzej

The next problem with PAS is: I can't start oepas1 service because of error - "Starting oepas1 in xxx.oepas1 (pacific Application Server for OpenEdge 11.5) has encountered a problem. Server oepas1 in xps.oepas1 (Pacific Application Server for OpenEdge 11.5) failed to start. "

Can you please share oepas1 agent log. You can find the log in $WRKDIR/oepas1/logs/oepas1.agent.log

It give give us some information on why it did not start

The catalog is empty.

No logs at all ?

Yes. Studio is trying to run server for few minutes. Then diplays error message.

To know if the problem is with the Pacific Appserver, can you try starting the instance from proenv

First clear all your olds if created for the instance.

In proenv type

pasman clean -I oepas1

Now start your instance

pasman start -I oepas1

Note: -I means -(captial i)

then you can look at the logs in $WRKDIR/oepas1/logs to see if it shows up any error in the agent or the server logs if  the instance does not start

ERROR from "run as administrator" context:

Exception: The term 'cmd.exe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.in startupCmd at line :

Exiting with fatal exception condition

======================================================

ERROR from user adm context:

cat : Access denied to path "C:\OE11\OpenEdge\servers\pasoe\conf\instances.windows".

At C:\OE11\OpenEdge\servers\pasoe\bin\tcmanager.ps1:1572 char:19

+         $_tmp= $( cat $script:_instlist | %{

+                   ~~~~~~~~~~~~~~~~~~~~~

   + CategoryInfo          : PermissionDenied: (C:\OE11\OpenEdg...stances.win

  dows:String) [Get-Content], UnauthorizedAccessException

   + FullyQualifiedErrorId : GetContentReaderUnauthorizedAccessError,Microsof

  t.PowerShell.Commands.GetContentCommand

The instance alias name not registered - oepas1

So when did this exception occur ? I am not sure why you see access denied errors when you are running with Administrative privileges

After "pasman start" command in proenv (run as ...). In the first context "current directory" is "C:\Windows\system32", in second - "C:\OE11wrk\WRK".

The term 'netstat' is not recognized by PowerShell 4.0. Are you sure, it is suitable for OE11.5 (see previous "logs") ?

"netstat" need to work, please check why is it not working

I called Powershell_4.0 and tried to run "netstat" - it is not recognized. Is it recognized by PowerShell_3.0 ?

it should work for both the versions

Could you review the screen view I added ?

Check your path to make sure c:\windows\system32 is included. Also check to make sure netstat is actually installed on your PC by searching under system32.

Something is messed up with your Windows install.

I can run 'netstat' from cmd.exe, netstat.exe is available in c:\windows\system32 path. Could you help me with checking the path included ? Do you mean "system environment variable" PATH ?

Yes... the windows PATH environment variable. You need to verify that it is correct using control panel.

You also need to verify what the PATH is set to once you are in PowerShell.

I modified PATH variable and started service. Thank you for all suggestions and support.

Now the problem is with publishing mobile service. I'm not sure I can present it in this group ...

Next error message is: "Server returned 403 Forbidden for https://localhost:8443/oemanager/applications/oepas1/webapps/Sports/transports/rest/oeservices with an HTML response".

Your URL is wrong. It should not have "transports"  in your URL.  "Sports" is your Application name, "rest" is your transport and "oeservices" is your Service name

It should be something like https://localhost:8443/oemanager/applications/oepas1/webapps/Sports/rest/oeservices

Sorry, made a mistake copy pasting the URL - https://localhost:8443/Sports/rest/oeservice