Select the search type
  • Site
  • Web
Search
You are here:  Support/Forums
Support

Bring2mind Forums

5.1.0 Installation Errors
Last Post 06/05/2009 9:49 PM by Peter Donker. 3 Replies.
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
floatingpointmatt
New Member
New Member
Posts:9


--
06/05/2009 7:22 PM

Hello,

We just purchased 5.1.0 and have had some difficulty getting the module installed.

We're using:

  • DNN 4.9.4 (Community Edition)
  • Windows Server 2003 (patched)
  • SQL Server 2000 SP4 (a development server - live server will likely be 2005/2008)

There were errors on installation in the SqlDataProvider section of the install:

  • 5.00.00 - line 6 - incorrect syntax near MAX
  • 5.00.01 - line 16 - incorrect syntax near DISABLE
  • 5.00.02 - line 10 - incorrect syntax near DISABLE
  • 5.01.00 - line 5 - incorrect syntax near (

    NOTE: The module still states it has installed correctly.

Immediately after adding the module, an error occurs:

DotNetNuke.Services.Exceptions.ModuleLoadException: Invalid object name 'dbo.DMX_LongTexts'. Invalid object name 'dbo.DMX_LongTexts'.

(Full stack trace available upon request.)

I had previously experimented with DMX using VWD Express 2005 and SQL Express 2005 without issue, so I'm gathering its an infrastructure issue.

Any ideas while I try to sort this out?

Thanks!

Matthew (Floating-Point Communications)

floatingpointmatt
New Member
New Member
Posts:9


--
06/05/2009 7:29 PM

Ah, just noticed the requirement...

"SQL Server 2005/Express. DMX uses some of the latest enhancements in SQL 2005."

(Document Exchange > Features > Requirements)

That would do it.

Thanks!

Matthew (Floating-Point Communications)

floatingpointmatt
New Member
New Member
Posts:9


--
06/05/2009 8:51 PM

Just to clarify beyond a reasonable doubt...

Meeting the requirements, everything installed just fine.

Thanks for a great product!

Matthew (Floating-Point Communications)

Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
06/05/2009 9:49 PM
:-) thanks for clearing up .. the 'incorrect near MAX' is a SQL 2000 error giveaway ...
You are not authorized to post a reply.