FWD

Hi Ritish,

The suggestions:

1. The current Windows session credentials are different comparing to what it enters in web fwd logon window.
2. Need to have administrator account to start web client.
3. Windows 8 has limitation for process environment block.
4. Windows error codes often do not reflect the real issue root cause.
5. May be antivirus or firewall blocks starting the child process.

I think first to try is to logon as admin and run the server and client with same user.

More questions:
1. What is the arch of OS, 32 or 64 bit?
2. What Java version do you use, 32 or 64 bit (java -version in command prompt if doubts)?

Hi Eugenie,

What is the arch of OS, 32 or 64 bit?
It is 64 bit OS.

What Java version do you use, 32 or 64 bit?

java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)

The user is an user with Administrator privileges. Also i have disabled the firewalls and still not working.

Thanks,
Ritish

Hi Greg,

Waiting for your response.

Thanks,
Ritish

At the login prompt that is displayed from https://your_hostname:7443/chui, it is very important that you are using a Windows userid and password. Do not use the hotel/hotel which is the application-level userid/password that will be used when the Hotel ChUI application screen is displayed.

Eugenie Lyzenko wrote:

Hi Ritish,

I think first to try is to logon as admin and run the server and client with same user.

Ritish,

Here I meant to use the same user/pwd to log on OS, to start the FWD server and to enter in web client logon prompt. And this user is a member of system administrator group.

Hi Greg and Eugenie,

I am using same user/pwd to log on OS, to start the FWD server and to enter in web client logon prompt.

Please help!!

Thanks,
Ritish

Ritish Mehta wrote:

Hi Greg and Eugenie,

I am using same user/pwd to log on OS, to start the FWD server and to enter in web client logon prompt.

Please help!!

Thanks,
Ritish

OK. The plan is:
I'm going to provide you the debug version of the windows module for you to rebuild, run and make some feedback for us to help you.

Is it OK?

Regards,
Eugenie.

Hi Greg and Eugenie,

what is debug version of the windows module? I am not getting you properly.

Do I need to do the all configuration and installation again?

Please provide me more information about this.

Really thanks for all of your help!!

Thanks,
Ritish

what is debug version of the windows module? I am not getting you properly.

The FWD program where the failure is occurring is src/native/winspawn.c. This is the "spawner". Eugenie will provide a temporary replacement version of this program that will output more information about the failure so that we can determine the root cause.

Do I need to do the all configuration and installation again?

No. But you would have to temporarily replace that one file, build FWD and make sure that the spawner was re-installed. Then you would run the test and send back the additional log that is created.

Eugenie will provide an exact list of steps when he posts the debug version of the spawner.

Hi Ritish,

This is the single source module winspawn.c with gathering some debug info into server.log.

1. Please copy this file into your p2j\src\native directory over existing one, make backup copy of current if you want.
2. Go to the p2j directory with command prompt and execute: gradlew.bat all
3. Go to the demo app directory and execute ant deploy.prepare
4. Reinstall spawner by install_spawner.cmd
5. Start the server again as usual
6. Try to start the web client
7. After issue happens inspect the server.log again.
- Check if the login and password written to server.log are OK. DO NOT publish full server.log here, just verify the user/pwd data for yourself.
- Provide us with other data: Command: and Working directory: .

Again, be warned, the server.log will contain user accounts data.

Regards,
Eugenie.

Hi Team,

I did all the steps mentioned in above mail and getting the same server log.

[01/31/2018 21:02:50 IST] (SessionManager.listen():INFO) {00000000:00000001:standard} Server ready
ERROR: API = CreateProcessWithLogonW
error code = 1783
message = The stub received bad data.

[01/31/2018 21:04:20 IST] (ClientSpawner.spawn():SEVERE) {qtp1841150825-39} Failed spawn with exit code: -6

I think there is no difference between both the server logs.

Thanks,
Ritish

Hi Ritish,

1. Please re-run the install_spawner.cmd
2. Make sure your deploy\spawner\spawn.exe is the module you just built (timestamp can hepl)

Your server.log must now have the entries:

Command: the java command to execute in a new process
Working directory: the value of the current directory

before
ERROR: API = CreateProcessWithLogonW

Regards,
Eugenie.

Hi Team,

I already checked that these spawner files are latest. I think there is no need to rerun install_spawner.cmd .

I donot know how to proceed now.

Thanks
Ritish

Ritish Mehta wrote:

Hi Team,

I already checked that these spawner files are latest. I think there is no need to rerun install_spawner.cmd .

I donot know how to proceed now.

Thanks
Ritish

Hi Ritish,

If the spawn.exe is latest then you will see additional debug log entries in server.log. If you do not see - something went wrong with spawner install because the source will printf to the file without any conditions.

Please execute install_spawner.cmd or manually copy spawn.exe from p2j\build\native directory to location mentioned in your directory.xml file for spawner location:

        <node class="container" name="clientConfig">
          <node class="string" name="spawner">
            <node-attribute name="value" value="Your_spawner_directory\spawn.exe"/>
          </node>
...

Meantime I'm going to set up my local copy of Windows 8.1 to check what can be wrong. This may take several hours to complete so please wait.

Hi Eugenie/Greg,

I have placed the spawn.exe(copied from p2j\build\native directory) in spawner location and checked that this spawn.exe is the latest file.

Then I ran server and client on my system and launched web client with OS credentials, but still getting the same server logs without Command: the java command to execute in a new process and Working directory: the value of the current directory before ERROR: API = CreateProcessWithLogonW.

Can you please list the versions on which you have tried this conversion?
Did you ever tried this conversion on window 8.1?
Also you were trying to setup window version 8.1. Any luck?

Please tell what will be the next step?

Thanks,
Ritish

Hi Ritish,

Ritish Mehta wrote:

Then I ran server and client on my system and launched web client with OS credentials, but still getting the same server logs without Command: the java command to execute in a new process and Working directory: the value of the current directory before ERROR: API = CreateProcessWithLogonW.

Can you please list the versions on which you have tried this conversion?

Windows XP, 7 and 10 (32 and 64 bits)

Did you ever tried this conversion on window 8.1?
Also you were trying to setup window version 8.1. Any luck?

I have installed fresh Windows 8 last night and everything is OK.

Please tell what will be the next step?

I need the debug info from you. So please recompile spawn.exe with new winspawn.c, refresh spawner directory and re-start server.

You can use install_spawner.cmd if spawner directory configured properly or execute gradlew.bat all in p2j directory and then execute ant deploy.prepare in hotel chui directory.

Note: missing Command and Working Directory entries means you still use old (not debugged) version of spawn.exe.

Regards,
Eugenie.

Hi Eugenie,

I have placed the winspawn.c(debugger version) at both paths (C:\Projects\hotel\p2j\src\native and C:\Projects\hotel\p2j\src\native) and did all the steps mentioned.

But still not getting other entries in server log(exactly same server log as before).

Thanks,
Ritish

Hi Ritish,

OK. Let's do things step by step. Please:

1. Change the C:\Projects\hotel\deploy\spawner\directory.xml as below:

        <node class="container" name="clientConfig">
          <node class="string" name="spawner">
            <node-attribute name="value" value="C:\Project\hotel\deploy\spawner\spawn.exe"/>
          </node>

This get back the spawner executable to regular location.

2. cd C:\Project\hotel\ and make dir /w. Please publish result here.

3. In the directory C:\Project\hotel\ please run install_spawner.cmd and verify there is no error during batch execution.

4. Please run dir C:\Project\hotel\deploy\spawner\, publush results here.

Then I need to inspect output provided and we will go further.

Regards,
Eugenie.

Hi Ritish,

Again, please DO NOT publish here any private info here like passwords, user ID. Anything that can potentially degrade your system's security.

Regards,
Eugenie.

Hi Ritish,

Do you have any progress to discuss?

Regards,
Eugenie.