Will re-install of Cireson portal with same ServiceManagement db name cause data loss?
Daniel_Heggie
Customer IT Monkey ✭
Hi there, i'm needing to re-install Cireson portal to apply a renewed SSL certificate for the site, as when applying the cert directly in IIS only, the binding keeps being removed each time the Platform Cache service is restarted. (I've also tried removing the old certificate from the computer store before updating in IIS, but when i do this, it just reverts the selected SSL certificate in the IIS https 443 binding to 'Not selected' after the Platform Cache Service is restarted). I've also tried restarting IIS, the Cache Builder, Platform Cache, and all SCSM services after updating the new cert in IIS, but the result is the same. I've also followed the instructions on the 'Setup SSL for Cireson Platform', and updated the platform_Cache.config file with the new cert's thumbprint, but it doesn't resolve the issue. It has been suggested to re-install the Cireson portal with the new cert, that will resolve the issue. My question is, when i do this, i use all the same config details, ie. ServiceManagement database name, and when i get to the end, it says database with this name already exists, are you sure you want to over wright it? If i say yes, will it cause any data loss, or will it have data resynced from the main ServiceManager database once the Cache Builder/Platform Cache services are restarted? It is a preprod environment, so i need to understand this process before updating production in Nov/Dec. I believe the portal was maybe installed with no certificate initially, but then one was applied after, potentially causing this behaviour.
Answers
Hi Daniel,
No, this is the upgrade process; to install a new version with the same DB name.
You are doing the same but with the same version.
https://kb.cireson.com/article/install-cireson-portal-installation-and-upgrade-instructions/1349
Geoff
hi Geoff, i've tried the re-install, but keep receiving 2 x errors at the end,
ALTER DATABASE statement failed.
With error one, i've tried running the Cireson Setup.exe as the main SCSM service account, and the Portal service account, and ensure they have sysadmin rights on the db both times, but in both cases, the same error appears. From the way it reads, it's like it's thinking the ServiceManagement_db_name is the 'db server', but this may be just the wording, not sure if it indicates an issue. I am certain i entered the db server and db names into the right fields during the install.
With error two, should i ask the dba to take the db out of the availability group first?
Also, after the installer finishes, even though it shows the above 2 x errors, i'm still able to go into the portal and see all my previous requests, but the sites customisation seems to have disappeared, so it's like the data is there, but the site formatting is lost/reverted, before the re-install, the homepage had 8 main tiles for major categories displaying, the side bar was the same colour as the toe bar (darkish green), there was no extra search bar at the very top, only the one below the Home heading, and the 'My Work Items' icon was instead replaced with an icon for 'Password Reset Questions'.
I've replaced the entire folder C:\inetpub\CiresonPortal\Views with the backed up one, incase there were any customised files in it, have restarted cache services and iis, but it's still the same
I discovered the custom .css and .js files are in C:\inetpub\CiresonPortal\CustomSpace and after the re-install the files had been removed, so i replaced the entire CustomSpace folder from my backup, restarted Cache Builder and Platform Cache services and IIS, but the site hasn't updated. I think it's because the install has not completed successfully maybe (still unable to resolve the 2 x errors described above), otherwise i'm not sure why the site formatting wouldn't be updating
Sorry, i cleared my browser cache, and the site has updated :-) . The new SSL certificate is also sticking in the IIS binding, which is also good :-) . The portal also seems to be working as expected, i can submit a request and it raises a SR, and the initial config script in the first Activity also runs, populating the request Description. The only thing is the 2 x errors i received at the end of the portal re-install (as mentioned above), does the install need to be completed without those 2 x errors, or are they no issue?
hi Geoff, Cireson Team, hoping for a response, as i need to prep this process before doing it in production soon.. many thanks!
Can you please share the two errors? Or alternatively if you want to open a support case we can pick it up.
Hi Adam, the 2 x errors at the end i keep receiving are;
ALTER DATABASE statement failed.
For the first one, the dba has confirmed the db definitely has an account with the service account name i'm trying to run the install with, they have given it sysadmin access too, and also the following roles, which is all they can grant apparently;
db_accessadmin, db_backupoperator, db_datareader, db_datawriter, db_ddladmin, db_securityadmin, public
For the second one, some reading tells me the mirroring session can be 'paused' on the sql server, is this what i need to try?
hi team, i asked the dba to take the servicemanagement db out of aoag and re-installed the Cireson portal, now the second error is gone, but i get 2 more errors now (no. 1 is the same as above),
30/10/2024 2:22:12 PM Failed to Deploy DacPac via DacServices API: server=AG-SMO-03-PP01\SQL01;Trusted_Connection=True; Could not deploy package. Unable to connect to master or target server 'ServiceManagement2019_SMP_03_PP01'. You must have a user with the same password in master or target server 'ServiceManagement2019_SMP_03_PP01'.
24 2:21:55 PM Failed to create management database logins ServiceManagement2019_SMP_03_PP01 on AG-SMO-03-PP01\SQL01 : Cannot open user default database. Login failed.
Login failed for user 'PRODUCTION\SYS-SCSM-Portal-PP'.
The errors seems permissions based, but online reading tells me the 1st error could be the result of the client computer failing to pass the firewall rules of the server (which could be possible, as i do get an app-locker alert toward end of the install, so still checking that)
Hi Geoff and Adam,
After working with the DBA i'm now only getting this error at the end of the Cireson portal re-install,
1/11/2024 9:51:56 AM Failed to Deploy DacPac via DacServices API: server=AG-SMO-03-PP01\SQL01;Trusted_Connection=True; Could not deploy package. Unable to connect to master or target server 'ServiceManagement2019_SMP_03_PP01'. You must have a user with the same password in master or target server 'ServiceManagement2019_SMP_03_PP01'.
I've confirmed with the dba, they've taken the ServiceManagement db out of aoag mode, and have also given the service account that i'm running the installer as sysadmin rights on the db.I've checked the sql server db is not blocked from the app server i'm running the installer on, so no firewall issue.
Any suggestion would be much appreciated, i feel like i'm really close!
Ok, i've found this KB article describing the error and to manually deploy the dacpac to resolve it, so going to try it.
https://support.cireson.com/KnowledgeBase/View/1343#!/
Although i will mention, even though i get this error, the portal itself seems to be working fine, even after restarting everything to make sure, including the Cireson Cache Builder + Platform Cache services, and IIS, so do i even need to worry about this manual deployment of the dacpac?
Hi Daniel,
I'm not 100% on that error, I would interpret that as missing sys admin rights but you can checked that.
I would recommend installing the DACPAC manually. Just because it "seems to be working" does not mean everything is good.
There could be a fix in the DACPAC for something you haven't noticed yet and there's often performance improvements too.
Geoff