none
SCOM 2019 web console issue RRS feed

  • Question

  • I am having an issue logging into the new web console after the ver 1807 to 2019 upgrade.  This was working before the upgrade.  This issue is when I try to log in as an operator role.  I can successfully login using my administrator role account.  When I try to go to https://...../operationsmanager I get the popup seen below.  I also see the corresponding event viewer message 

    OpsMgr SDK Service   Event ID:   26319

    "An exception was thrown while processing GetManagedEntitiesByManagedEntityTypesAndCriteriaWithInstanceQueryOptions for session ID uuid:abf33888-7f7f-4e2e-8143-e6c6124e5411;id=11.
     Exception message: The creator of this fault did not specify a Reason.
     Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.UnknownDatabaseException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Incorrect syntax near the keyword 'CREATE'.)."

    Tuesday, April 23, 2019 6:57 PM

Answers

All replies

  • It looks like this is a bug that comes from SCOM 2016 UR6 (which is actually more recent than 1807). Stoyan blogged about it : https://blog.pohn.ch/scom-2016-ur6-console-crashes-with-incorrect-syntax-near-the-keyword-create/
    • Edited by CyrAz Tuesday, April 23, 2019 7:04 PM
    Tuesday, April 23, 2019 7:04 PM
  • I changed the dll and it actually crashes the data access service.  I had to revert the dll file back.

    Rene

    Tuesday, April 23, 2019 7:30 PM
  • Hi,

    The workaround that CyrAz posted should work (Stoyan's blog), what is interesting is if this still occurs in SCOM 2019.

    Update Rollup 7 for SCOM 2016 just came out and there isn't listed any fix for this, which seems strange as well.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, April 23, 2019 7:30 PM
  • So I guess you'll have to raise a case with the support :/
    Tuesday, April 23, 2019 7:30 PM
  • What is the fastest way to contact support or to report this bug?

    Thanks,

    Rene

    Wednesday, April 24, 2019 2:04 PM
  • Do you have any support agreement with Microsoft?

    You can report bugs/feedback over here:

    https://systemcenterom.uservoice.com/forums/293064-general-operations-manager-feedback

    You can request for support over here:

    https://support.microsoft.com/



    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, April 24, 2019 2:11 PM
  • Also that was supposed to be fixed in 2016 UR7, which was released just a few hours ago (https://support.microsoft.com/en-us/help/4492182/update-rollup-7-for-system-center-2016-operations-manager).

    It's not very clear from the release notes if it was indeed fixed, but you could try the dll from that version; or wait for SCOM 2019 UR1 which may follow shortly.



    • Edited by CyrAz Wednesday, April 24, 2019 4:27 PM
    Wednesday, April 24, 2019 4:26 PM
  • in SCOM 2016 UR7, issue is resolved.
    Thursday, April 25, 2019 4:41 PM
  • Sourav,

    This does not add up.  My scom environment was newly built at version 1801, updated to 1807 then 2019.  This has nothing to do with version 2016.  There was no issue with version 1807.  This occurred when I upgraded to 2019.  I did take the dll file from the original 1801 version and copied it over to all management servers.  When I went to start the services the System Center Data Access Service would not start.  I don't have access to scom 2016 UR7 files so I cannot test whether that would work.

    Thanks,

    Rene

    Thursday, April 25, 2019 5:13 PM
  • Hi Rene,

    Here's the Microsoft.EnterpriseManagement.DataAccessService.Core.dll for SCOM 2016 UR7:

    https://1drv.ms/u/s!ApovQr03HsGDmDr7L1UkrTuXZ4EV


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, April 25, 2019 5:31 PM
  • Thanks Leon,

    I downloaded the file, copied them to the management servers and he same thing as above.  the data access service is not starting.  

    Thanks,

    Rene

    Thursday, April 25, 2019 5:53 PM
  • Hi Rene,

    For SCOM 2019, it would be fixed in UR1.

    Thanks,

    Sourav

    Thursday, April 25, 2019 7:04 PM
  • Hi Sourav,

    Thanks for confirming that.  Is there an eta on UR1?

    Rene

    Thursday, April 25, 2019 7:34 PM
  • Update Rollup 1 for System Center 2019 will be released in Q3 of 2019.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, April 25, 2019 7:39 PM
  • That's a long time to wait for something we would like now.  I will contact support and see what they can do.  I have to wonder if this may be a permissions issue as I can access the web console using an administrator account but not the operator account.

    Thanks,

    Rene

    Friday, April 26, 2019 1:04 PM
  • Hi,

    Is our deployment based on English version? It seems the error is encoded in base64 format and non-English. We can use any base64 decoder to decode the error message to see if there is any clue.



    Hope the above information helps.

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Monday, April 29, 2019 5:48 AM
  • Hi Alex,

    Thanks for the response.  My deployment is English.  Not sure why the error would be coded in non-English.

    Rene

    Monday, April 29, 2019 11:48 AM
  • So to throw a curveball into the issue,  I also upgraded my test environment and the web console works great for any role.  Could this then be a permissions issue?  Is there an updated security account matrix for 2019 that I can check against?  

    Rene

    Monday, April 29, 2019 6:57 PM
  • There are security changes in SCOM 2019, you can find them described by Kevin in his blog over here:

    Security changes in SCOM 2019 – Log on as a Service
    https://kevinholman.com/2019/03/14/security-changes-in-scom-2019-log-on-as-a-service


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, April 29, 2019 7:01 PM
  • Hi Leon,

    Thanks for the response.  I had come across that followed that documentation when I did the upgrade.  

    Rene

    Tuesday, April 30, 2019 12:08 PM
  • Hi Rene,

    did you find any solution for this? Waiting till Q3 seems not a very good idea....

    Regards,

    Marc


    Regards,
    Marc Klaver
    http://jama00.wordpress.com/

    Tuesday, May 28, 2019 1:57 PM
  • Hi Marc,

    I am currently working with MS support on this.  It seems that one cannot create a view in the windows console client and share it to web console users which leads to that error.  They are replicating the issue in their labs and discussing with the developers.  They are still not sure if this is a bug or a limitation.

    I will update when I know.

    Rene

    Tuesday, May 28, 2019 2:03 PM
  • Hi Marc,

    I am currently working with MS support on this.  It seems that one cannot create a view in the windows console client and share it to web console users which leads to that error.  They are replicating the issue in their labs and discussing with the developers.  They are still not sure if this is a bug or a limitation.

    I will update when I know.

    Rene

    Hi Rene,

    that would be really awesome. Thank you for that!

    Regards,


    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov

    Tuesday, May 28, 2019 2:16 PM
    Moderator
  • They are still not sure if this is a bug or a limitation.

    Since the error also appears when using the console I would classify it as a bug :)

    Thanks for the fast update. Hope there will be a solution soon!

    Marc


    Regards,
    Marc Klaver
    http://jama00.wordpress.com/

    Tuesday, May 28, 2019 2:22 PM
  • I got to know from the product group a similar Web console error would be fixed in 2019 UR1

    No updates on the release date, The issue was present in SCOM 2016 and was fixed in UR7.


    Gautam.75801


    Tuesday, May 28, 2019 8:19 PM
  • I got to know from the product group a similar Web console error would be fixed in 2019 UR1

    But that can take another 3 to 4 months.... So 3 to 4 months no implementation of scoped views? Sounds for me as a perfect candidate for a hotfix....

    Regards,

    Marc


    Regards,
    Marc Klaver
    http://jama00.wordpress.com/

    Wednesday, May 29, 2019 7:04 AM
  • I heard back from Microsoft support.  The issue that caused the error is due to that I created a custom view using a custom management pack in the desktop Operations Console and tried to share it out to users using the Web Console.  According to the developers this is default behavior.  One can only share custom views from one mode to the other ie Operations Console to users using Operations Console.  If you want to create views for users who use the web console then you have to create them in the web console.  In hindsight I guess this does make sense but I have yet to see any documentation that describes this limitation.

    Rene

    ps.  Microsoft was kind enough to provide a refund for the cost of the support call as there was no real resolution.  

     
    Friday, May 31, 2019 12:52 PM
  • I heard back from Microsoft support.  The issue that caused the error is due to that I created a custom view using a custom management pack in the desktop Operations Console and tried to share it out to users using the Web Console.  According to the developers this is default behavior.  One can only share custom views from one mode to the other ie Operations Console to users using Operations Console.  If you want to create views for users who use the web console then you have to create them in the web console.  In hindsight I guess this does make sense but I have yet to see any documentation that describes this limitation.

    Rene

    ps.  Microsoft was kind enough to provide a refund for the cost of the support call as there was no real resolution.  

     

    This is not true. There is no reason why a custom made view would not be available for users, unless there is a bug in the software which shows up when the users have a scoped view (which is currently the case).

    This always worked in the past and it does work without scoping (I have one working right now without scoping). I think they just let us wait for the next release....


    Regards,
    Marc Klaver
    http://jama00.wordpress.com/

    Tuesday, June 4, 2019 7:21 AM
  • I had a similar issue last year - not the same.. but try to uninstall your monitoring agent from the server, and delete the server from SCOM. Then reinstall a new agent.

    https://regularscomguy.wordpress.com/2018/08/08/scom-web-console-gets-503-error-after-upgrading-to-1801-1807/#more-710
    Tuesday, June 11, 2019 1:18 PM
  • Hi Stoyan,

    is there any solution for the issue "Incorrect syntax near the keyword 'CREATE' " ?

    We have SCOM 2019 and this issue exists.

    We detected this issue only if the user has not Administrator permissions on SCOM server. If the user starts SCOM Operations Console, this error will be prompted many times.

    As you see, the application version is a new one.

    Best regards

    Birdal

    Monday, December 16, 2019 9:28 AM
  • This looks like a BUG in SCOM 2016 from a specific UR and SCOM 2019.

    A private fix is available or you can wait to upgrade to SCOM 2019 UR1 which is to be released around Jan 2020 or Feb 2020.

    https://support.microsoft.com/en-my/help/4506518/system-center-operations-manager-hotfix-for-scoped-group-users


    Gautam.75801


    Monday, December 16, 2019 4:58 PM
  • Hi Birdal,

    the information provided by Gautam is interesting, maybe this will be fixed with the SCOM 2019 UR1. Let's wait and see.

    Regards,


    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov

    Tuesday, December 17, 2019 11:57 AM
    Moderator
  • Hi Guatam,

    will this bug definetly solved in the UR1?

    If yes, we want to wait till this date. We have many SCOM Management Servers and have NLB (Network Load Balancing). I am not sure if this hotfix will work also in our environment

    Best regards

    Birdal


    • Edited by _Birdal Wednesday, December 18, 2019 8:21 AM
    Wednesday, December 18, 2019 8:20 AM
  • Hi,

    Kevin also has this on his known issues list over here:
    https://kevinholman.com/2019/03/14/scom-2019-quickstart-deployment-guide/

    "4.  When using a scoped user profile, you might see a “500 – Internal server error” when using a state view in the Web Console.  You also will see the same bug that was in SCOM 2016 UR6 where state views may throw an error: Incorrect syntax near the keyword ‘CREATE’. This bug was fixed in SCOM 2016 UR7 and is scheduled to be resolved for SCOM 2019 in SCOM 2019 UR1."

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, December 18, 2019 8:24 AM
  • Hi Guatam,

    will this bug definetly solved in the UR1?

    If yes, we want to wait till this date. We have many SCOM Management Servers and have NLB (Network Load Balancing). I am not sure if this hotfix will work also in our environment

    Best regards

    Birdal


    Hi Birdal,

    If you doubt so, You can test this in your Lab environment first and then implement it to see if you see the expected results.


    Gautam.75801

    Thursday, December 19, 2019 11:42 AM
  • This looks like a BUG in SCOM 2016 from a specific UR and SCOM 2019.

    A private fix is available or you can wait to upgrade to SCOM 2019 UR1 which is to be released around Jan 2020 or Feb 2020.



    Gautam.75801


    I can confirm that this hotfix worked for me in my SCOM 2019 Environment for this exact issue.  Thanks!
    Wednesday, January 29, 2020 5:43 PM
  • Hi Guys,

    were you abvle to test this? Did you manage to install SCOM 2019 UR1? I already see that the issue is resolved for many..Would really appreaciate some feedback!

    Regards,


    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov

    Wednesday, February 19, 2020 1:09 PM
    Moderator
  • Yes, for me it is solved with UR1.

    Regards,

    Marc Klaver


    Regards,
    Marc Klaver
    http://jama00.wordpress.com/


    Wednesday, February 19, 2020 9:17 PM
  • Yes, for me it is solved with UR1.

    Regards,

    Marc Klaver


    Regards,
    Marc Klaver
    http://jama00.wordpress.com/


    Hi Marc,

    thanks, appreciate this. Will mark the thread as resolved, although it has been opened by Rene, SCOM UR1 is obviously the solution here. 

    Regards,


    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov


    Thursday, February 20, 2020 12:33 PM
    Moderator
  • Hi Stoyan,

    yes, this issue is solved after I installed UR1 for SCOM 2019.

    Best regards

    Birdal

    Thursday, February 20, 2020 2:34 PM