Ran repair, now can only access Altiris via http://localhost/...
Updated: 21 May 2010 | 6 comments
Hi all,
I ran a repair on Notification Server and it seems to work fine as long as I access it via http://localhost/Altiris/console on the local machine.
If I access via http://servername/Altiris/console (either local or on a remote client), I get an authentication prompt.
Sound like an IIS issue. Any ideas?
RM
discussion Filed Under:
Comments
Hi Richard612,
Hi Richard612,
Why did you need to run a nsrepair? The NSRepair not change (or correct) the settings of IIS.
What error messages appear in the logs of the NS?
Regards,
If the suggestion has helped to solve your problem, please mark the post as a solution.
Fábio Sanches
Altiris Consultant
Our Altiris was completely
Our Altiris was completely non-functional. EvtQfast was filling up and the user interface was not loading at all. CPU was continuously at 100%.
Richard, Could you post some
Richard,
Could you post some any part of the current NS Log?
Regards
If the suggestion has helped to solve your problem, please mark the post as a solution.
Fábio Sanches
Altiris Consultant
Did you repair the latest hotfix as well?
When repairing Notification Server from add\remove, you also need to repair the latest Hotfix Roll-up as well. Did you do this?
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
It does not appear that any
It does not appear that any hotfixes were installed. SP3 was installed, and yes I did perform a repair on it after doing a repair on NS itself.
Repair hotfix
I just went through this myself in order to address an issue in the Log viewer "Error trying to generate shortcut icon: System.ArgumentException: Illegal character..." I had to run a repair on the Altiris Notification Server 6.0 and on the latest Notification Server 6.0 SP3 update. After doing that I was unable to log into the console, thought it was an IIS issue as well. I rebooted the server again, opened up the 6.0 console on the NS and I was prompted to go through the setup wizard. I put in the SQL application credentials and the rest of the settings were retained and once the wizard completed I was able to get back in fine.
Would you like to reply?
Login or Register to post your comment.