Unsolved
This post is more than 5 years old
4 Posts
0
1063
January 19th, 2011 05:00
Replistor gui issue
Hi all
I have installed Replistor 6.4.2 on one of our target Server (IBM x3650)
I could not open the gui so I've restarted the Server. After the reboot I was able to open the gui for just one time.
If I klick on the Icon know, the rep_clt.exe is running but without any CPU consumption.
Someone any idea`?
Thank you
No Events found!
jschrade1
106 Posts
0
January 19th, 2011 05:00
I suggest you contact EMC Support. This not normal behavior. I also recommend you download userdump.exe from the Microsoft download site. once this is installed, typically in the C:\kktools folder, you can run the "userdump.exe rep_clt.exe". This will take a snapshot of the RS GUI process and create a log file. This file can be zipped and attached to the EMC Service Request. The person who is assigned to the case can look for any obvious issues and help you upload the logs to be reviewed. Thanks
ZFSZH
4 Posts
0
January 19th, 2011 06:00
Thank you for your answer.
Will do this, it seems now RS Gui is running but it need around 10minutes to start.
ZFSZH
4 Posts
0
January 19th, 2011 07:00
It is a 2003 Enterprise Server (SP2) and it is in our Domain.
yito1
262 Posts
0
January 19th, 2011 07:00
Hi,
Is this environment Windows 2008?
Is it a domain member?
yito1
262 Posts
0
January 19th, 2011 07:00
Hi,
Please confirm the message when you were able to open GUI correctly after ten minutes.
There might be a log that becomes some hints.
When installing it, did you register in Active Directory?
ZFSZH
4 Posts
0
January 21st, 2011 05:00
I've tested it now on two different server.
With "RepliStor 6.4.SP0.HF2" the response time to open the gui is normal. With the version 6.4.SP2 i have to wait on the second server more than 10 minutes to open the gui.
Will do some more test, if I have more time, but for now I will use "6.4.SP0.HF2". Thank you for your support.
(yes, I do register in Active Directory. I've got Domain-Admin right)
yito1
262 Posts
0
January 23rd, 2011 17:00
Hi,
There is not the report of this symptom in Japan.
It does not reappear in my test environment either.
It may be symptom which depended on your environment.
It is not possible to cooperate because you don't show the log.