Upgrading
I get the following error “Value cannot be null. Parameter name: type
at System.Activator.CreateInstance(…” at the end of the installation log
You are upgrading pre DMX3.1 to DMX 3.1+. This is a bug in
DNN which has no serious consequence. You will need
too upload the module a second time and you should not see this message again.
My existing module instances give System.IO.FileNotFound
Exceptions
There was an error in the upgrade process from DMX1 to DMX3
(e.g. file not found DesktopModules/DMX/DMX.ascx), or
from DMX3.0.x to DMX3.0.14+ (e.g. file not found
DesktopModules/Bring2mind.DMX/Dispatch.ascx). There is a script included in the
readme for DMX. This script needs to be run before
attempting these upgrades to avoid these errors. If you find yourself in this
situation please follow the following steps:
- Go
to Host > Module Definitions and verify that you have more than one of
the following names in your list of modules: Document Exchange, DMX,
Bring2mind.DMX, and Bring2mind\DMX
- Go
to your SQL database and remove the ‘Bring2mind\DMX’ record
from DesktopModules
- Download
the readme.zip or the upgrade.sql
from www.bring2mind.net
- Run
this script under Host > SQL as script.
- Verify
that the name of the remaining document exchange module is now
‘Bring2mind\DMX’. This is important as DNN recognizes the
existing module during upgrade. If the name is different a second/new
module definition is created which will not correspond to your existing
module instances throughout your portal.
- Upload
the new DMX
Note: Document exchange 1 was located under
DesktopModules/DMX, version 3.0
was located under DesktopModules/Bring2mind.DMX. Because the latter
produced
errors with url scanners
this was subsequently changed to DesktopModules/Bring2mind/DMX.
References to
the module name and directory can be found in the following tables:
DesktopModules, ModuleControls, ModuleSettings (check the value field),
DMX_Extensions.
Installation and Activation
I get an error during install: Failure because foldername/modulename
element is not declared
You are trying to install a DNN3.1 module under
DNN3.0. With
DMX you can still install under DNN3.0.13 but you will need to edit the
.dnn file in the zip: remove the elements ‘friendlyname’, ‘foldername’,
and ‘modulename’ that fall just under
‘folder’ element. It should upload after that.
If I activate now, can I activate later on my production server?
Yes. You may activate twice: once on a staging server and
once on the production server.
My copy tells me the license is OK.
Under certain conditions the current version skips the
activation process. This may change with updates. For now continue working.
How do I activate my copy of DMX Pro?
- Go
to the license screen and fill in the following details:
Account: this is the email address(es) you used
to buy the product from Snowcovered. If you have
a different billing and delivery address then fill in both separated by a
single space (note that the order is important).
Invoice: this is the invoice nr (including the ‘SCI-‘) that
you received from Snowcovered.
- CLICK
SAVE (this is a bug which will soon be taken care of)
- Go
back to the license screen and confirm your details have been stored in
the system.
- Now
click ACTIVATE
- If
activation was successful you should see an activation key appear on your
screen. Click SAVE and you’re done.
- If
activation failed a button appears. Click this and a second attempt is
made through another route. If this fails details are provided that you
need to send to us in an email.
Uninstall
The use of subdirectories to structure custom modules is
still relatively new. As a consequence a new bug was found in DNN which
prohibits the de-installation of such modules. This means that DNN3.1 is
incapable of de-installing document exchange itself. To remove all components:
- Delete
the directory DesktopModules/Bring2mind/DMX
- Delete
your repository directory
- Delete
the Bring2mind\DMX record from DesktopModules
- Delete
all tables and procedures that are preceded by DMX_ from your SQL database
- Delete
triggers from your portals table that are preceded by DMX_