Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ..."User is ambiguous in the namespace" error after server change"User is ambiguous in the namespace" error after server change
Previous
 
Next
New Post
12/4/2006 6:44 AM
 

Thanks for the tips again.

This past week has been a classic DNN nightmare really. My careful test and backup routine got me 6 months into an 8 portal instance and then crumbled. I'm not really sure how to get out of this. I think DNN needs some sort of self-test script that one could run after upgrades, module installs and other alterations. It would run through a set of actions and test all vital functionality. I believe I've been caught out somewhere in the last week by one of quite a few module updates and installs I made prior to moving to a new account. somewhere along the line, something around the profile page became buggy.

The whole drama has been made much worse by Webhost4life's inability to provide a reliable and fully functional VPS account and I'm 99% positive I'll be asking for my payment back and will move on.

In any case, today I upgraded both to DNN 4.37 and to an SQL2005 database in order to get the site back online and ensure that none of the basics were faulty. I tried removing modules going back 2-3 weeks to long before I last used the profiles page, but that failed to fix it.

I will try your suggestion Rodney, of loading a copy of the db onto a fresh blank 4.37 instance to rule it out.. I'll do that on the server tomorrow evening.

I've uploaded the ManageUsers.ascx.vb and manageusers.ascx pages fresh to the server from the latest upgrade.zip, but that didn't help. I do find it odd that occasionally the host portal's profiles page will work, but I haven't figured out exactly how to make it do so. It just does now and then like when I removed the Homepages module.

oh crappp... now there's a new error.. when I try to view the event log in DNN.. this comes up:

Error: Log Viewer is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Cannot resolve the collation conflict between "Latin1_General_CI_AI" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation. ---> System.Data.SqlClient.SqlException: Cannot resolve the collation conflict between "Latin1_General_CI_AI" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation. at
etc...................

man! Ok, I see from a search that this is from upgrading from sql200 to sql2005. I was told by the host that I merely needed to restore sql200 into a blank sql2005 db. I guess not :(

 
New Post
12/4/2006 7:11 AM
 
I had a (very) quick look at ManageUsers.vb - on line 816 it uses
ByVal e As User.UserCreatedEventArgs  (Users here is Users.vb and Users.ascx - ie. not the core User object)

and then it also references User for sending mail and elsewhere in the class. For some reason the context is not inferred.

You could try prefixing the one on line 816 with;

DotNetNuke.Modules.Admin.Users.User.UserCreatedEventArgs

I haven't tried it and it is more worrying that everything else works and this does not... it may be to do with the way WH4L have configured their .NET 2.0 compilation settings? Not sure but if you are trying things... (keep a backup of everything!)

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
New Post
12/4/2006 7:38 AM
 
robax wrote

oh crappp... now there's a new error.. when I try to view the event log in DNN.. this comes up:

Error: Log Viewer is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Cannot resolve the collation conflict between "Latin1_General_CI_AI" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation. ---> System.Data.SqlClient.SqlException: Cannot resolve the collation conflict between "Latin1_General_CI_AI" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation. at
etc...................

man! Ok, I see from a search that this is from upgrading from sql200 to sql2005. I was told by the host that I merely needed to restore sql200 into a blank sql2005 db. I guess not :(

 

This is a old bug in a stored procedure that happens if the database collation is not the same as the server.

You find the solution in gemini for next release here

Jan

 
New Post
12/4/2006 7:39 AM
 

Thanks heaps for the tips. I can still safely revert back to 4.36/sql2000 and not lose content, but I can't go any further back to before this all happened, so I'll try anything at this stage.

I'm no coder so I may have done it wrong, but I changed this:

Private Sub UserCreateCompleted(ByVal sender As Object, ByVal e As User.UserCreatedEventArgs) Handles ctlUser.UserCreateCompleted

To this:

Private Sub UserCreateCompleted(ByVal sender As Object, ByVal e As DotNetNuke.Modules.Admin.Users.User.UserCreatedEventArgs) Handles ctlUser.UserCreateCompleted

Then re-saved the web.config to let it recompile and checked again. It still returns the same error, but it seems to be much quicker at doing so. I don't know if that means anything?

Error: Manage Profile is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: c:\hosting\webhost4life\member\robax\wumpworld437\Admin\Users\ManageUsers.ascx.vb(816): error BC30560: 'User' is ambiguous in the namespace 'DotNetNuke.Modules.Admin.Users'. ---> System.Web.HttpCompileException: c:\hosting\webhost4life\member\robax\wumpworld437\Admin\Users\ManageUsers.ascx.vb(816): error BC30560: 'User' is ambiguous in the namespace 'DotNetNuke.Modules.Admin.Users'. at System.Web.Compilation.AssemblyBuilder.Compile() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---

Thanks again for your look-ins Rodney. They're much appreciated,

Rob

 
New Post
12/4/2006 7:51 AM
 
Hmm - very odd. To ensure the new page/changes are compiling, can you push it down one line (leave a blank line) so the error message should be on line 817 if it is picking up the new file?

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ..."User is ambiguous in the namespace" error after server change"User is ambiguous in the namespace" error after server change


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, 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 DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out