Skip to main content
Solved

Dispatch Console error after upgrade to 15.2


bskallerud
Sidekick (Customer)
Forum|alt.badge.img+11

We are in the middle of upgrading our second business unit from 12.5 to 15.2. All seems fine until I try to open Dispatch Console (which works on profile already upgraded). The client trows the following error: 

 

In the server event log I find these errors:

Both profiles run on the same server, so the environment is fine.

Best answer by Phil Seifert

Hi Bjørn,

You had this problem before, if I recall.  Can you add this column with the following script which is sourced from the HF1 database scripts?

if   exists (select 'x' from sysobjects,syscolumns  where sysobjects.type='U'  and sysobjects.id = syscolumns.id  and

                              sysobjects.name ='dc_general_settings' and syscolumns.name = 'assisted_dispatch_hours_ahead')

ALTER TABLE dc_general_settings     drop column assisted_dispatch_hours_ahead

GO

 

Otherwise, I think you should run the HF1 upgrade installer with the option dbupgrade.txt and point it to your new database you migrated.  This is because your database from DK was not upgraded after connecting it.  Anytime you are connecting a new database, it needs to have the same database scripts run against it for the 15 SP2 and also HF1.

View original
Did this topic help you find an answer to your question?

5 replies

Reid Gilbert
Superhero (Employee)
Forum|alt.badge.img+15
  • Superhero (Employee)
  • 339 replies
  • March 4, 2022

Take a quick peek at the dc_general_settings table in each of these two databases, see if you see an entry in there for the assisted_disp_hours_ahead field (if it exists in one database but not the other then try rerunning the database upgrade scripts or check the log files to see if there was an error during the upgrade script execution):
 

 


bskallerud
Sidekick (Customer)
Forum|alt.badge.img+11
  • Author
  • Sidekick (Customer)
  • 206 replies
  • March 4, 2022

Thanks, Reid. As you suspect, that field is missing for the new profile. Have run the upgrade twice… Can I jsut add it manually?


Reid Gilbert
Superhero (Employee)
Forum|alt.badge.img+15
  • Superhero (Employee)
  • 339 replies
  • March 4, 2022

Are there any errors in the DB upgrade scripts log file?  You could probably add it manually but I would be worried that there are many other fields that weren’t created that should have been as well which could cause other problems later on in your testing.


Phil Seifert
Ultimate Hero (Employee)
Forum|alt.badge.img+23
  • Ultimate Hero (Employee)
  • 1297 replies
  • Answer
  • March 4, 2022

Hi Bjørn,

You had this problem before, if I recall.  Can you add this column with the following script which is sourced from the HF1 database scripts?

if   exists (select 'x' from sysobjects,syscolumns  where sysobjects.type='U'  and sysobjects.id = syscolumns.id  and

                              sysobjects.name ='dc_general_settings' and syscolumns.name = 'assisted_dispatch_hours_ahead')

ALTER TABLE dc_general_settings     drop column assisted_dispatch_hours_ahead

GO

 

Otherwise, I think you should run the HF1 upgrade installer with the option dbupgrade.txt and point it to your new database you migrated.  This is because your database from DK was not upgraded after connecting it.  Anytime you are connecting a new database, it needs to have the same database scripts run against it for the 15 SP2 and also HF1.


bskallerud
Sidekick (Customer)
Forum|alt.badge.img+11
  • Author
  • Sidekick (Customer)
  • 206 replies
  • March 4, 2022

Ran the HF1 upgrade - problem solved. 

 

Thanks guys!


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings