Help - Error Guid should contain 32 digits with 4 dashes After Upgrade

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
6/28/2011 7:52:17 AM
vincek
Gravatar
Total Posts 44
View Posts

Re: Help - Error Guid should contain 32 digits with 4 dashes After Upgrade - RESOLVED

Hi Joe,

All is well now, I took a copy of the latest source code, linked my local project to the remote database and worked through it.

My problems arose due to my workflow, the local and remote databases were synchronised in terms of objects, but not data, so I had the correct columns in the table, but not the default data. The GUID error was caused by a NULL return as opposed to the expected empty GUID, a result of not running the upgrade scripts on both the local and remote databases.   

Lesson learnt!

Thanks for all help.

Vince.

6/28/2011 11:22:49 AM
IndigoTea
Gravatar
Total Posts 355
View Posts

Re: Help - Error Guid should contain 32 digits with 4 dashes After Upgrade

Vince - glad you sorted it through. I actually saw the same error briefly last night when upgrading a client site, but since I use the source code to compile locally before publishing to the "live" site, it was a simple thing to skip the error msg and finish running the scripts, which solved the issue. It's good to remember when you're updating any site with custom code, to make sure your upgrade scripts also set data when adding new columns.  Good luck with your project!

You must sign in to post in the forums. This thread is closed to new posts.