Unsolved
This post is more than 5 years old
50 Posts
0
805
March 18th, 2008 21:00
ECC6.0,Performance Manager,forgot passwd...
Hi,
I get headache because cann't enter the right passwd for PerformanceManager login!
Anybody can help me??how to login/reset passwd/....... Oo...
Ray
I get headache because cann't enter the right passwd for PerformanceManager login!
Anybody can help me??how to login/reset passwd/....... Oo...
Ray
No Events found!
bodnarg
2 Intern
•
385 Posts
0
March 19th, 2008 05:00
These were changes to require authentication for both of these modules.
Chenxt
50 Posts
0
March 19th, 2008 21:00
bodnarg
2 Intern
•
385 Posts
0
March 20th, 2008 04:00
The password is the password of the matching Windows account on the ECC server so if your username is USER1 just reset the password for USER1 on the server which runs your ECC repository and you should be fine. If you do not have rights to the server to do so get one of your local System Administrators to do it and you should be good to go.
The server name should be the same as what you see in the "ECC Repository" field on the login screen for the GUI client or the hostname in the URL you connect to if you are using the web based PM client.
Hope this clarifies things a little bit more.
RRR
2 Intern
•
5.7K Posts
0
March 20th, 2008 12:00
Chenxt
50 Posts
0
March 24th, 2008 01:00
But can NOT log on to the performance server with the same account and password!
The account name is eccadmin.
Chenxt
50 Posts
0
March 24th, 2008 01:00
bodnarg
2 Intern
•
385 Posts
0
March 24th, 2008 04:00
I'd suggest you try both the Web and Client based method if you could - that will rule out any client configuration issues. Has it ever worked or did it just stop working? Can you confirm that the WLA archiver is running?
This is probably going the route where you will want to open a case with SAC. You certainly should be able to do what you are trying so something must either be misconfigured or you may be experiencing some sort of software issue.
Chenxt
50 Posts
0
April 21st, 2008 00:00
This issue has been fixed by install the patch 4081.
We can download the patch on powerlink.