Earnie Eng New Member Posts:28  
| 11/22/2005 2:35 AM |
|
Hi all...
I've attempted to install DMX 3.01.51 on DNN 4.0 (of course running on sql server 2005 express).
So far. Activation is successful, but when I attempt to add a new folder or new item, I get an errormessage telling me that a stored procedure is missing:
when "New Folder" is clicked:
A critical error has occurred.
The stored procedure 'dbo.DMX_GetEntryAttributeList' doesn't exist.
when "New item" is clicked:
A critical error has occurred.
The stored procedure 'dbo.DMX_GetEntryAttributeList' doesn't exist.
When I checked the database using MS SQL Server Management Studio Express, I don't see those stored procedures within the database... I see DMX tables defined, though...
Any suggestions?
|
|
|
|
Peter Donker Veteran Member Posts:4536
| 11/22/2005 7:52 AM |
|
Hi,
DMX has not been readied for DNN 4, yet. please consider it as still a DNN 3.x product.
Peter |
|
|
|
Rob Ralston Basic Member Posts:164
| 12/28/2005 12:37 AM |
|
|
Hello Peter,
What is your estimated time frame for DNN 4.0 support?
Thank you.
|
|
|
|
Peter DonkerVeteran Member Posts:4536
| 01/02/2006 7:39 PM |
|
|
I will not pin down on a timeframe right now as I need to get a lot done these days. I have tried to install it and it worked, but I have not had time to do more testing.
Peter
|
|
|
|
colt taylorNew Member Posts:1
| 01/16/2006 10:57 PM |
|
|
Drop an email to me at colt@computergolf.com when the 4.0 version is ready. My boss has already approved purchasing DMX Pro as soon as it fits into the DNN 4 that I'm currently running. Looking forward to it.
Thanks,
Colt
|
|
|
|
Peter DonkerVeteran Member Posts:4536
| 01/16/2006 11:52 PM |
|
|
The current status is: it is working in the lab and on a number of customer installations. There have been sporadic reports of errors though. These might be due to 'medium risk' and code security consequences, but it's still being investigated. Note that in the majority of cases DMX 3.2.x works fine under DNN 4.
Peter
|
|
|
|
Jakob Anker HansenNew Member Posts:3
| 04/05/2006 1:16 PM |
|
I just tried to install the latest version 3.3.1 on DNN 4.02, and got the following: Resource Upload Logs
Return
StartJob Starting Installation
StartJob Reading files
Failure ExceptionICSharpCode.SharpZipLib.ZipException: Wrong Local header signature: 0x6964654D at ICSharpCode.SharpZipLib.Zip.ZipInputStream.GetNextEntry() at DotNetNuke.Modules.Admin.ResourceInstaller.PaInstaller.ReadZipStream() at DotNetNuke.Modules.Admin.ResourceInstaller.PaInstaller.Install()
Return
So to me It appers that there is a big compatibility problem with DNN 4. I am very much looking forward to new and compatible final version... Is there a new time estimate about this ? Best regards Jakob Anker Hansen |
|
|
|
Rob RalstonBasic Member Posts:164
| 04/05/2006 2:02 PM |
|
|
Hello Jakob,
I don't what caused your error, but thought you should know I have DMX 3.3.1 running on DNN 4.0.2, W2K3 SP1, without any problem. Installation went fine. Did you attempt the upload from the Host/Module Definitions page?
Rob Ralston
|
|
|
|
Jakob Anker HansenNew Member Posts:3
| 04/10/2006 9:15 PM |
|
|
Yes, I agree... I have now done a new installation on a fresh DNN 4.0.2, and this time it worked fine... I haven't fully stress tested the solution but now we are about to go to production and I am hoping the best...
Peter: If the solution works fine, how about upgrading the status to "full DNN 4.x compatibility" ?
Best regards
Jakob Anker Hansen
|
|
|
|
Peter DonkerVeteran Member Posts:4536
| 04/13/2006 12:34 PM |
|
|
Hi all,
It's unfortunate that with two DNN versions there is confusion about compatibility. In fact: the core team made every effort to keep DNN 3.2.2 and 4.0.2 completely identical from the logic perspective. As each and every dll can run both .net 2 and .net 1.1, modules should run under both. However, when people see two stores at Snowcovered they start thinking "is it DNN3 or DNN4?". I have now done a number of tests under DNN 4 and have done some code cleaning and am confident DMX is fully DNN 4 compliant. But one should know the development here is still done on 3.2.2. There is going to be a turning point in the near future. When the DNN 4 version goes to v 4.1 and DNN 3 does not follow suit, us module developers have to choose. And probably most of us will leave .net 1.1 behind and go .net 2. Until that time we use the same module under DNN 3 and DNN 4.
Peter
|
|
|
|
Jakob Anker HansenNew Member Posts:3
| 04/13/2006 9:15 PM |
|
|
Thank you for this very clear answer...
For the sake of business for Bring2Mind and to avoid confusion, I would suggest that DMX is updated at Snowcovered to show DNN 4.x compatibility...
Regards
Jakob
|
|
|
|
Holger KopfNew Member Posts:57
| 05/12/2006 9:01 AM |
|
|
Peter,
so after DNN 4.1 will be released, you will also offer a DMX which works with that version ? I hope there will be an upgrade feature, so that the existing entries in DMX will not be lost ?!?
Regards
Holger
|
|
|
|
Peter DonkerVeteran Member Posts:4536
| 05/12/2006 10:11 AM |
|
|
Holger,
I'm not leaving DNN if that is what you mean. I will continue developing for the new DNN platforms whan they come out. DMX will follow. You might have to give us some time if changes to the platform are big.
Kind regards,
Peter
|
|
|
|
Jeff DyckNew Member Posts:2
| 06/09/2006 2:22 AM |
|
|
Hi Peter,
We use DMX on our DNN 3.2 site and we need to update the site to DNN 4 to make use of a security model enhancement for our deployment. I've got a parallel (test) site and got the DNN 4 update successfully in place on that, but I'm getting the following on the DMX module at run time: "A critical error has occurred. MinMax persistance type of cookie requires a ModuleId ". All I did was copy the 3 "add key" entries into the new DNN 4 web.config file and hoped for the best. Is there anything else I should have done? I believe our DMX version is: 03.01.03.
Thx,
Jeff Dyck
|
|
|
|
Peter DonkerVeteran Member Posts:4536
| 06/09/2006 3:06 PM |
|
|
Jeff,
The error is a pretty general error. The 'add key' additions to the web.config are no longer necessary. The module can be activated through its own interface. Note that you should upgrade to make sure you stay in sync with DMX developments (such as DNN 4 compatibility). The current version is 3.4.3. Please use that and activate through its own interface.
Peter
|
|
|
|