Home› General Discussion

Portal SRs show wrong infomation after Portal upgrade from v6 to v7

Xiaoqian_LiXiaoqian_Li Customer IT Monkey ✭
in General Discussion
After upgrading from v6 to v7, the end users report they couldn't find SRs (SR shows in Console, but not in Portal) or SR status shows wrong status info from active work/all work items search window (e.g. New instead of In-Progress). But while we browse the SR, it shows In-Progress correctly. Also we see lots of event on cache builder server "

Error in Adding WatchList User Ids

System.NullReferenceException: Object reference not set to an instance of an object.

   at Cireson.ServiceManager.Services.Implementations.RequestOfferingService.GetWatchListArray(RequestOfferingViewModel model)

Any idea? Please advise. Thank you.

Answers

  • Tony_CollettTony_Collett Cireson Support Super IT Monkey ✭✭✭✭✭
    There may be an issue with the installation of the portal when you performed the upgrade. 

    During the upgrade, did you check the properties of the install file to see if it was blocked, and proceed to unblock it? Part of Windows Server causes portions of files to be blocked if it the source is detected that it was from another computer/downloaded. 
    The installer may have completed, however some files may have been blocked from being transferred/updated

    Check the install file and see if it was blocked, if it was, you may attempt to reinstall the portal after unblocking the file. 
  • Xiaoqian_LiXiaoqian_Li Customer IT Monkey ✭

    The installation completed successfully. We saved the setuplog and I checked that log again, there is no error. Besides the issue doesn't happen on all the work items, only on a few WIs.

  • Tony_CollettTony_Collett Cireson Support Super IT Monkey ✭✭✭✭✭
    Xiaoqian_Li said:

    The installation completed successfully. We saved the setuplog and I checked that log again, there is no error. Besides the issue doesn't happen on all the work items, only on a few WIs.

    This is commonly misleading when an application is blocked, the log will still say it did everything it was supposed to and that the installation was completed successfully. Whereas in reality Windows blocked something from transferring but the installer didn't know that, so it put it down as success. 
  • Xiaoqian_LiXiaoqian_Li Customer IT Monkey ✭
    Thank you for looking into this issue. Somehow it resolves itself this morning. Looks like the Cache DB finally gets synced.
Sign In or Register to comment.