Notification Server 7 SP1 - Resource Membership Update error
Hello.
I have just installed a brand new Notification Server 7 and I discovered an out-of-box error on this server.
The error concerns the "Resource Membership Update" section under Notification Server Setting (formerly known as the collection update schedules). If I try to apply a different value to one of the schedules I get a NS error "There is no guid associated with this page".
I have restarted the server once just to make sure everything is running smoothly.
The log viewer unfortunately doesn't reveal more information that the standard jibberish:
Here's the juice:
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[AeXException: There is no guid associated with this page.]
Altiris.NS.UI.DataProviders.ProviderHelpers.GetGuidFromPage(HttpRequest request) +700
Altiris.NS.UI.DataProviders.NSBreadCrumbProvider..ctor(Page page) +55
Altiris.NS.UI.cfgAutomaticCollectionUpdating.OnInit(EventArgs e) +391
System.Web.UI.Control.InitRecursive(Control namingContainer) +333
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +378
Anyone that can shed I light in theis matter?
Cheers,
Patrik
Comments
A discussion on Altirigos
brought this up. Someone ran across it during the beta, and it appears to still be an issue. Altirigos link.
Scheduled to be fixed in SP1, which I think means SP1 for the platform which hasn't been released yet.
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.
Thanks for the quick reply,
Thanks for the quick reply, Jim.
Hopefully they will take care of this soon. It's not that wonderful guiding customers in the lovely world of Windows Scheduled Task once Altiris has gotten it's hands on it.
For all of you that experience the same problem.
You can bypass this by changing the schedules directly in Windows Scheduled Tasks (START/Control Panel/Scheduled tasks). The schedules you would want to change is the:
Cheers,
Patrik
Project Manager / Founder
Asterio AB, Sweden
www.asterio.se
Thanks Patrik!
My concern here is that as discussed it would be fixed in SP1, and unless I'm wrong (again) it appears the platform IS as SP1, so maybe it means NS SP1? Hopefully we can get some clarification from Symantec.
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.
Yes, you are probably right.
Yes, you are probably right. They meant that it would be fixed in NS SP1.
Isn't it confusing when they rebrand stuff ;)
Cheers,
Patrik
Project Manager / Founder
Asterio AB, Sweden
www.asterio.se
.NET Version 3.5
Just to clarify. The root cause of this problem is related to the version of .NET that is installed on the server running NS. Version 7 requires .NET 3.5 and only .NET 3.5. You cannot allow 3.5 SP1 to get installed or you will continue to find strange problems like with the Resource Membership Updates.
Yes, you can overcome the problem by manually changing the scheduled task in Windows. However, I would strongly suggest you re-build you server with the correct version of .NET installed to eliminate any risk of additonally problems later on (i.e., I also experienced issues with Patch Mgmt 7 not be properly installed and all items were not available until I corrected the .NET versions.)
~Kevin
Check out KB 46492. I worked
Check out KB 46492.
I worked through the same problem and haven't seen any issues since applying the steps in this article.
Principal Consultant
Bob Wooding
Not entirely sure if it will work with 3.5 SP1
However, I have used the tool posted here: Aaron Stebners WebLog which removes all versions of .net. You still have to manually install the correct versions back.
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.
Regular uninstall of 3.5SP1 works too
Somehow we got .NET 3.5 SP1 on our test NS box and the install (even the platform by itself with no Solutions) wouldn't complete installing. I was able to get NS installed and working by just uninstalling 3.5 SP1 from Add/Remove and letting SIM install it instead. You would think that since there is this compatibility issue with 3.5 SP1 that it would be added as one of the Preinstall checks that SIM runs before allowing the install to complete.
Thanks,
Kyle
Symantec Trusted Advisor
For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.
Would you like to reply?
Login or Register to post your comment.