• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 13 subscribers
  • Views 934 views
  • Users 0 members are here
Options
Related

SP 2023 R2 error - This user does not have access to the System Platform IDE

Michael Kruger

Hi. I have a 2014 System Platform Galaxy that I am migrating to 2023 R2. I have done the migration without any issues but now when I try to open the Galaxy I get an error message saying that "This user does not have access to the System Platform IDE". The galaxy is setup with Galaxy security so I would expect the IDE to ask me for a username and password but this is not the case. I migrated the exact same galaxy to a test VM I have with SP 2023 and here it works fine, it asks me for my username and password and then the galaxy opens. Is there any way to force a galaxy to request a username and password from the SQL side as I am not able to access the galaxy at all at the moment in the 2023 R2 version. My other option is to disable security completely in the 2023 version and create a new backup and then import that into 2023 R2 but my issue is the galaxy is quite large and takes about 3 hours to backup and another 4 hours to restore. If I can only edit the correct table in the SQL db to force my galaxy to ask or the login details I will be able to log in which would be great. I have made sure my current windows user is added to aaAdministrators and aaConfigTools user groups just incase but it still does not work. Thank you for any comments.

Parents
  • 0

    Hi Michael, 

    Is this the prompt you get?

    If so, it should only care about the settings in your galaxy security settings.
    Is it the same for all users? and can you log in using the built in account "Administrator"

    An invalid user should show a different prompt.

    Keep in mind that migrating from version 2014 to 2023 R2 will require you to do an intermediate step, migrating your galaxy to either 2017 or 2020 first, as stated in the readme file.
    I have seen strange issues if this step is not applied.

    Also, when installing the 2023 R2 Version, did you unblock the installation media prior to the installation, I know it might sound far-fetched, but as long as AVEVA's official statement on this topic (through tech support) is that "wierd sh** can happen", I would still have this on the list to check.

    How did you restore the 'backup' cab file?
    Using the BackupGalaxies folder and created new galaxy from this or did you create a new galaxy with the same name and then restored from backup using SMC?

  • 0 in reply to Richard Köhlerstrand

    Hi Richard.

    That first screenshot you sent is the prompt I get yes. My big issue is I am expecting the IDE to ask for my login details, but it does not ask for it, it says connecting to galaxy and then gives that prompt.

    I am aware of the intermediate step to migrate to 2017 or 2020 before going to 2023 but I wanted to try going directly to 2023 to see what happens and it works when going directly to 2023 as far as I can tell. I then made a new backup from the 2023 version and migrated to 2023 R2 and this is where I am getting the issue now. I will try to use the original 2014 backup and use the proper process if I can’t get my 2023 R2 version to work. I have now just tried one last thing before going back to the original backup, so I have removed the security in the 2023 version and made a backup. It is currently restoring so I will see if that works.

    I did check if the installer was unlocked after I did the install but luckily it was unlocked.

    I restored the cab file using the BackupGalaxies folder.

    Once I have some proper feedback I will reply again.

    Thank you for your comments.

  • 0 in reply to Michael Kruger

    Thank you for clarifying, that does indeed sound like a corruption of the galaxy configuration.

    I guess if you, on the same node create a new galaxy and enable Security it will prompt you for a user, that will at least verify if it is an environmental or galaxy issue.

    Unfortunately there are issues like this that could appear if you migrate directly from 2014 but there is no way for me to say for certain, it sounds like you are taking appropriate actions and I look forward to any feedback on any tests.

    When I have skipped the intermediate steps in the migration i have experienced issues in the managed InTouch application where some (Swedish) characters stopped working, script did not appear in list, windows not available etc. so i know it is important to migrate the application and not only the galaxy in the intermediate steps as well.

    Good luck!

    Richard

Reply
  • 0 in reply to Michael Kruger

    Thank you for clarifying, that does indeed sound like a corruption of the galaxy configuration.

    I guess if you, on the same node create a new galaxy and enable Security it will prompt you for a user, that will at least verify if it is an environmental or galaxy issue.

    Unfortunately there are issues like this that could appear if you migrate directly from 2014 but there is no way for me to say for certain, it sounds like you are taking appropriate actions and I look forward to any feedback on any tests.

    When I have skipped the intermediate steps in the migration i have experienced issues in the managed InTouch application where some (Swedish) characters stopped working, script did not appear in list, windows not available etc. so i know it is important to migrate the application and not only the galaxy in the intermediate steps as well.

    Good luck!

    Richard

Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.