Upgrade problems
 
Notifications
Clear all

[Solved] Upgrade problems

17 Posts
6 Users
3 Reactions
1,216 Views
Posts: 43
Topic starter
(@mastercodefu)
Trusted Member
Joined: 8 years ago

Hi Trevor,

So I took a snapshot prior to the upgrade, it looks like during the upgrade the attached error occurred during the upgrade all servers.  The error above was then the outcome when trying to load the homepage.  The upgrade I used the PowerShell script which gave 2 options for 1.4.9 etc one beta.  I selected the one not in beta to do the upgrade. I selected the top option to update all items.  After the page failed I then reran the script and selected upgrade all servers option but the page loaded the same, I also rebooted the server.  Interesting my exchange server is saying 1.4.9 so looks like that is completed.  Any idea on the errors during the initial upgrade?

Regards

Craig

Reply
Posts: 6
(@kingj2000)
Active Member
Joined: 3 years ago

I have the same errors when using the update script and a database update error when using manual update. It looks like there are some bugs in the upgrade process, the only thing that works is a new install but we need a way to backup and restore to the new install, do you have any ideas how to do this?

Reply
Posts: 26
(@hampsons)
Eminent Member
Joined: 8 years ago

Hello

i am having the exact same issue 🙁 exchange is working but i cannot log into the portal

i went from 1.47 - 1.49 i also used Auto Upgrade Script v2.2.2

I dont mean to hijack this its just the error message i get is exactly the same

Reply
7 Replies
(@mastercodefu)
Joined: 8 years ago

Trusted Member
Posts: 43

@hampsons No problem mate, I'm just looking at it now but as rerun, I don't think will fix it.   did you see the error I got when I first ran the upgrade, etc did you have the same error.

Reply
(@hampsons)
Joined: 8 years ago

Eminent Member
Posts: 26

@mastercodefu Hi i sorted my issue check your web.configs especially server and portal,

Go here scroll down to "Updating the solid CP Portal section" and check your web.config against the suggested, you may find it is the <runtime> section is wrong on your server.

Regards

Kevan

Reply
(@mastercodefu)
Joined: 8 years ago

Trusted Member
Posts: 43

@hampsons Thanks mate, that looks like has sorted it.

 

Thanks, the solid cup team for keeping the project going.  I look forward to future releases.

Craig

 

Reply
(@hampsons)
Joined: 8 years ago

Eminent Member
Posts: 26

@mastercodefu Glad you are sorted 🙂 i do still have a little issue not sure if you have the same problem but i would assume you have, the solid CP scheduler service keeps crashing with .NET runtime errors, think i may need to start another post even though it is related to the update, i have attached a screenshot of my event viewer can you check if you do indeed have the same issue ?

Regards

Kevan

Reply
Admin
(@trobinson)
Joined: 9 years ago

Noble Member
Posts: 1456

HI,

The config file is normally removed when trying to do a upgrade via the installer.

I have uploaded a copy of the config file to https://installer.solidcp.com/Files/1.4.9/SolidCP.SchedulerService.exe.config.zip you will need to replace the connection string & crypto key with that from your enterprise server web.config.

 

You should then be able to start the service without issue.

 

Regards,

 

Trevor

Reply
(@hampsons)
Joined: 8 years ago

Eminent Member
Posts: 26

@trobinson Hi Trevor 🙂 thank you going to try it now

Reply
(@hampsons)
Joined: 8 years ago

Eminent Member
Posts: 26

@trobinson Thank you so much that did work my daily reports are coming through now 🙂

Reply
Posts: 57
(@dvoijen)
Trusted Member
Joined: 7 years ago

I have the same issue, used the powershell script but still...

Reply
Posts: 44
(@briman)
Trusted Member
Joined: 5 years ago

I tried today to upgrade from 1.4.8 to 1.4.9 using the PowerShell script, tried 3 times and still getting same error as reported in the first post.

I rolled everything back to 1.48 and after some missing file this and that (recovered from the backups) I'm now up and running but still on 1.4.8

🙁  

 

Reply
Page 2 / 2
Share: