| |
|
|
|
|
|
|
|
|
|
 |  | |
| | |
| | |
| | |
 | | |
|
|
|
|
Most modules will also require a DLL to be in the BIN folder, those that don't have DLLs generally require a folder in the app_code directory as well as the desktopmodules directory.
Chris Hammond
Engage Software
St. Louis, MO
314.966.4000
The leading provider of DotNetNuke skinning, training and custom module development.
Official DotNetNuke® Training Provider |
|
|
|
| |
|
|
|
Ok, We might finally be getting somewher, maybe, you never know.
So I copied the bin dlls from the live site to the local site, then I got an error, which the forum said to remove the DotNetNuke.Modules.Html.dll DotNetNuke.Modules.Html.SqlDataProvider.dll files from the bin folder. I did that and NOW it get:
Value cannot be null.
Parameter name: type
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ArgumentNullException: Value cannot be null.
Parameter name: type
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. |
Stack Trace:
[ArgumentNullException: Value cannot be null.
Parameter name: type]
System.Activator.CreateInstance(Type type, Boolean nonPublic) +2843963
DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectProviderName, String ObjectNamespace, String ObjectAssemblyName, Boolean UseCache) +582
DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectNamespace, String ObjectAssemblyName) +17
DotNetNuke.Security.Membership.Data.DataProvider.CreateProvider() +39
DotNetNuke.Security.Membership.Data.DataProvider..cctor() +13
[TypeInitializationException: The type initializer for 'DotNetNuke.Security.Membership.Data.DataProvider' threw an exception.]
DotNetNuke.Security.Membership.Data.DataProvider.Instance() +0
DotNetNuke.Security.Membership.AspNetMembershipProvider..cctor() +5
[TypeInitializationException: The type initializer for 'DotNetNuke.Security.Membership.AspNetMembershipProvider' threw an exception.]
[TargetInvocationException: Exception has been thrown by the target of an invocation.]
System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck) +0
System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache) +103
System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache) +268
System.Activator.CreateInstance(Type type, Boolean nonPublic) +66
DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectProviderName, String ObjectNamespace, String ObjectAssemblyName, Boolean UseCache) +582
DotNetNuke.Security.Membership.MembershipProvider.CreateProvider() +38
DotNetNuke.Security.Membership.MembershipProvider..cctor() +13
[TypeInitializationException: The type initializer for 'DotNetNuke.Security.Membership.MembershipProvider' threw an exception.]
DotNetNuke.Security.Membership.MembershipProvider.Instance() +0
DotNetNuke.Entities.Users.UserController..cctor() +5
[TypeInitializationException: The type initializer for 'DotNetNuke.Entities.Users.UserController' threw an exception.]
DotNetNuke.Entities.Users.UserController.GetUserCountByPortal(Int32 portalId) +0
DotNetNuke.Entities.Portals.PortalInfo.get_Users() +17
DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) +1304
DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo objPortalAliasInfo) +82
DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +3306
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64
|
|
|
|
|
| |
|
|
|
Hi Joe,
This error is most likely caused by a misconfigured web.config or a missing DNN dataprovider.
It is appearing more and more likely that you are attempting to create some sort of mutant hybrid of two DNN versions, which would cause all sorts of errors like these (in addition to just not working). I'll need some answers to the questions posited by myself (and others) above before we'll be able to help further.
Brandon
Brandon Haynes
BrandonHaynes.org |
|
|
|
| |
|
|
|
I'm simply trying to take a live system that is working and move it to a local system for testing. They are both now 4.8.4, earlier I did make a mistake of tyring to use an older database that I was told was 4.8.4, but it was not. So.....
The live system was 4.6.3 and upgraded to 4.8.4. Then I took a dump of the files and copied the the local drive under a temp folder. I did hte same with the database, taking a backup of it and moving it to the local box.
This is very straight forward from this point. (A functional 4.8.4 plain jane working system locally)
I installed all the software according the the various tutorials, using Mitchel's as the bible on this. Everythings works at this point. The site works and all.
I changed the Aliases also.
Then I took the database and imported it as noted in the tutorials and forum posts. I changed the aliases again. I then took the bin files, the DesktopModule files an copied them from the temp folder from the working live site and put them in the working local site.
Now I have all the problems. I have not found any tutorials that step you beyond the 4.8.4 install and importing the database. So I assume that I'm missing several very key points here.
How do I know that they both are 4.8.4 besides that I performed the upgrades (I checked in the database also, but is that the right answer).
The local site has the right skin and text, just the modules are missing. My assuption is that the modules have to be installed locally, but I don't know how to do that. I assume that the authentication module is why I can't log on with the live account credentials.
Joe |
|
|
|
| |
|
|
|
| SimplyJoe wrote
I'm simply trying to take a live system that is working and move it to a local system for testing. They are both now 4.8.4, earlier I did make a mistake of tyring to use an older database that I was told was 4.8.4, but it was not. So.....
The live system was 4.6.3 and upgraded to 4.8.4. Then I took a dump of the files and copied the the local drive under a temp folder. I did hte same with the database, taking a backup of it and moving it to the local box.
This is very straight forward from this point. (A functional 4.8.4 plain jane working system locally)
I installed all the software according the the various tutorials, using Mitchel's as the bible on this. Everythings works at this point. The site works and all.
I changed the Aliases also.
Then I took the database and imported it as noted in the tutorials and forum posts. I changed the aliases again. I then took the bin files, the DesktopModule files an copied them from the temp folder from the working live site and put them in the working local site.
Now I have all the problems. I have not found any tutorials that step you beyond the 4.8.4 install and importing the database. So I assume that I'm missing several very key points here.
How do I know that they both are 4.8.4 besides that I performed the upgrades (I checked in the database also, but is that the right answer).
The local site has the right skin and text, just the modules are missing. My assuption is that the modules have to be installed locally, but I don't know how to do that. I assume that the authentication module is why I can't log on with the live account credentials.
Joe
|
Hi Joe,
Please clarify your process in plain English. Are you installing 4.8.4 locally first and is that installation working perfectly? The reason I ask this is to make sure there are no issues with DNN and your local dev box.
Next, if the above is yes, why are you installing 4.8.4 locally to begin with? Zip up all the files of the live site from the root directory, backup the db, copy or ftp down the zip file and the backup of the db. Then create a new directory on your C drive/D drive or whatever drive, unzip the entire contents of the zip file there, right click on the new folder and set the appropriate permissions, go to IIS and set up a new website that points to this directory, add any host header records if needed.
Then use Studio Managment Express, attach to the db in the app data folder. Once attached, choose to restore the db from the backup db you got from the live site and make sure to choose the overwrite option. Once that is done, go into the portal alias table and set up the new portal alias.
Detach the db and you may have to go back to the app data folder and reassign the permissions as sometimes and in some cases when detaching the db in Studio Management Express it cause the db to loose its permissions.
If like Bradon says, you are trying to merge 2 versions or different versions or merge any versions at all, you are making this harder than it needs to be and according to your stated goal "to get the live site down to a local dev box for developement" you are going about it the wrong way, if indeed this is what you're doing.
So you need to chunk most of your "I Quit" frustrations out of the window as it appears most of this has been self-imposed because the process to begin with was flawed. Take a deep breath, refocus, and let's get this done
Paul |
|
|
|
| |
| | |
| | |
| | |
|  |
| |
|
|
|
These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.
For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:
1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.
|
| |
|
|
|
|
|
EMAS Pro
Strategic Enrollment Management Software for Higher Education Recruitment, Retention and Financial Aid
www.emaspro.com
|
Subzero Solutions
Dutch / English DotNetNuke consultancy services. Custom module development in any version. Complete application integration. Small business portal hosting.
Your ideas our innovation - Your success our motivation.
K.v.k Amsterdam: 34236342
www.subzero-solutions.net
|
Hosting for DotNetNuke
SiteGround.com is the best place to host your DotNetNuke website! Expert DotNetNuke support, reliable servers, low price!
www.SiteGround.com
|
|
|
|