Unsolved
This post is more than 5 years old
79 Posts
0
995
April 5th, 2011 21:00
AutoStart5.4 build 195 can not start process with period set as domain name
The autostart is configured to support dual servers on Windows Server 2003 R2 SP2. And the domain of login info is set as .(a period). But the process can not be started with error:
Info PROC Wed Apr 06 11:46:39 2011
By: FT/Agent on Node: cnsqaenvision8
MESSAGE: ID00001571 Started process EriEnvRM on cnsqaenvision8 [pid = 1820]
===================================
Error PROC Wed Apr 06 11:46:46 2011
By: FT/Agent on Node: cnsqaenvision8
MESSAGE: ID00000602 Process EriEnvRM on cnsqaenvision8 failed [pid = 1820]
AutoStart 5.3.3 on Windows server 2003 and AutoStart 5.4 build 195 both can work well except 5.4 build 195 on Windows 2008 with the period domain setting. Set the domain with local hostname can works well. But it will not automatically relocated to another server -- This is not what we expect.
From Administrator's guide:
Process configuration - Settings tab-->
yito1
262 Posts
0
April 5th, 2011 21:00
Hi,
In my environment, it work with a
Moreover, even if various values are set, it operates.
For example, it is input to the domain column as test.
Still, it operates correctly.
I think that this is a bug.
EnvisionPlus
79 Posts
0
April 5th, 2011 23:00
Once again, I test the period with single server on Windows server 2003. One server can work well but the other not.
I will update with new founds.
Thanks
---------------------------------
After comparing the OS, network configurations, hosts/domain setting, no difference is found. Can you tell me how to see the detailed operations during AutoStart start process. Thanks
EnvisionPlus
79 Posts
0
April 6th, 2011 00:00
Hi Yoshinobu Ito,
From your snapshot, it seems that you are testing on Windows 2008. Yes, it works well on Windows 2008 for . It has problem on Windows 2003.
Thanks.
EnvisionPlus
79 Posts
0
April 6th, 2011 01:00
One important note: The process is configured with "Allow Access to the Windows Desktop".
Also, have you tried login the same server from different sessions on Windows 2003.
In my enviroment, one user remote login by A and it works well with .
And another user login the same server with the same name as A. Open the console and the process will fail.
I am afraid that this problem may be brouht by supporting Windows server 2008 session 0 problem.
Thanks
yito1
262 Posts
0
April 6th, 2011 01:00
Hi,
I tested with Windows2003SP2R2.
Result
Period --- It operates correctly.
Workgroup name --- It operates correctly.
test --- It doesn't operate.
EnvisionPlus
79 Posts
0
April 6th, 2011 02:00
Hi，
I can reproduce the prblem now:
I will create one service request for this problem.
Thanks