Does anybody know of the procedure for changing the SQL server for Docstar installations? We are upgrading to SQL Server 2019 in preparation for Kinetic, and moving the databases and updating the config files aren’t working.
Our Docstar server is staying put, just wanted to point to the new SQL server.
@Doug.C There is a SQL server entry in Astria_Host database CompanyInstance table that does not get updated by rerunning the install wizard. I had an issue with my dev instance pointing to the production data that I just got fixed by changing this record. There are also the datalinks that point your E10/11 server that you can change in the UX.
When I switched back the config to use the original SQL Server, it worked, but I got consistent errors in the event log. I think maybe both running the install and updating this record needs to be done.
Over 12 hours with no errors in the event log, I think it’s good. Thanks!
I must have missed something because I got a lot of errors when the daily maintenance tried to fire off. I don’t see anyplace where that old server is listed.
@Doug.C Here is the SearchAll script I use. I searched for my SQL server in AAAA0001 and in Astra_Host. I don’t know how the EclipseSyncDB or EclipseSignalRBackplane fit into the picture.
I also found there is a database server on the IDC server called DocstaridcServerDB.
Is your maintenance DocStar or SQL? What are the errors?
It returned no results for the old server, and the field you mentioned for the new server.
I’m wondering if it is in a cache somewhere on the server itself. I’ve searched all of the files on the server for the old server name and I only come up with a few places, but they are log files only.
If every minute I would think it is sync db, but I have no idea. I found the same kids of errors on backups failing in my event viewer, but I can’t find the backup job.
@gpayne Was this the root of your problem we discussed in Vegas? I didn’t realize there was an entry in the DB that did NOT get altered with re-running the install/setup program.
@MikeGross This was the root of the issue, but I also had a few other issues left over from cloning the servers. I got tired of waiting and untangled them myself this weekend, so I could start writing workflows.
It seems to be a configuration item in the ASP.NET installation. Looking at the DLL the error is coming from, it looks like it’s getting the server from that config. I’ve looked around at all I know to look at to see a connection string/application setting, but I came up with nothing.
I found some messages like yours from when I was doing maintenance and rebooted the sql server. I saved the service settings on my ECM client. A dialog came up that the settings were written to C:\ProgramData\Eclipse\ApplicationServices.config. I looked at that file and it is encrypted. Maybe resaving all of the ECM settings for Services and any batch imports will clear the issue.
It makes sense as to why everything was working. The errors were from the client, not the web application. My forehead will heal after a week, but the forehead size hole in the wall will need some time for me to repair…