Stored Procedures install script

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.
1/10/2007 9:22:39 AM
salazie
Gravatar
Total Posts 40
View Posts

Stored Procedures install script

Hi,

I've downloaded the latest release files for SQL Server and run the database scripts. The tables are created fine but when I run the stored procedures script I get a number of errors, mostly based around a missing PathId column, one error is:

Server: Msg 207, Level 16, State 3, Procedure mp_SitePersonalizationAllUsers_GetPageSettings, Line 18
Invalid column name 'PathId'.

Any idea what's happening? I haven't had this issue before, and am wondering if I'm just doing something daft... I have retried this on a number of databases I've created locally though and keep getting the same errors.

Thanks,
Matt

1/10/2007 9:53:31 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Stored Procedures install script

Hi Matt,

I think your dbs must be configured as case sensitive since I don't get this error. I will correct the case in the script in time for the new release this weekend. To get past the error now you can edit the script where it creates the procedure mentioned. There is a variable declared as PathId which is ok, but where it is assigned from the select and in the where clause I guess it needs to reference the table column as PathID not PathId

Hope it helps,

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