Service Offering not being displayed on End Users Portal
Alaugon
Member IT Monkey ✭
Hi,
We've created 3 new services offering to be displayed on our end users portal.
They've some request offering attached. Also, the SO are attach to a Catalog Group, and this catalog group is assigned to a Security Group and an AD's group.
However, they are not visible on the end user's portal (The SCSM administrator are able to see them, but the Active Directory group members are not).
As far as we've two SCSM servers, and one of them still have the Out of the box portal, we've try to log into this one and we are able to see the Service Offering whitout problem.
For now we've tryed to reset the cache builder service, reset the app pool, to unpublish and publish the service offering again, to change de AD Groups for another who works with other Service Offering, but none of this has solved the problem
As far as we've two SCSM servers, and one of them still have the Out of the box portal, we've try to log into this one and we are able to see the Service Offering whitout problem.
For now we've tryed to reset the cache builder service, reset the app pool, to unpublish and publish the service offering again, to change de AD Groups for another who works with other Service Offering, but none of this has solved the problem
Do you have any idea about how to solve it?
I tryed to check the Cache Builder log but the last entry belongs to January 3 and these groups haven't been created for then
Regards
0
Best Answer
-
Rod_Marten
Customer IT Monkey ✭
If you can see the SOs and ROs in the MS as shipped portal but not the Cireson portal, that almost certainly is a CacheBuilder issue.- Backup and clear the cachebuilder log file (~\inetpub\Cireson Portal\Bin\Logs\CacheBuilder.txt)
- Stop the CacheBuilder Service
- Truncate the LastModified table in the Cireson ServiceManagement database
- Start the CacheBuilder Service
- Verify after some time that 6 entries are re-created in the LastModified table. If it doesn't complete adding last modified dates, then the log file should tell you what is blocking it.
- Check the log file for errors. The log file should be empty.
- Reset app pool in IIS
- restart website in IIS
If that's not it, then the usual stuff- Are the SOs and ROs published?
- Are the ROs related to the SOs?
- Are both the ROs and SOs in the catalog group?
- Is the catalog group assigned to the security role?
- Is the AD group a user of the security role?
- Is your test user a member of the AD group?
7
Answers
If that's not it, then the usual stuff
ilder Service and the app pool solve the problem!