Hi all!

There is a problem in my site. When I want to login, I see this error:
"Object reference not set to an instance of an object."

I wanted to add a sub portal and I added it and logout. But I can't login to my site now.

What can I do?

Do you have a backup copy of your site? If so, revert and try again.

If you have access to the database with SQL Server Management Studio or another tool, take a look at the EventLog table and see if you can see more details about the error. Look at the most recent few entries.

Is adding a new portal the only thing that you did?

Also, which version of DotNetNuke are you using?

I haven't a backup and adding a new portal is the last thing that i did.
my version is 4.8.3

I remembered what I did exactly>> I added a new portal, then I removed it, then I added it again. Is the problem related to these steps?

You are going to have to look into the EventLog table to see if you can find more details on the error.

Does the site run if you don't try to login?

There is no problem to run the site.
I found the following error in EventLog table (it's the last event):

AssemblyVersion-1PortalID-1PortalNameUserID-1UserNameActiveTabID-1ActiveTabNameRawURLAbsoluteURLAbsoluteURLReferrerUserAgentDefaultDataProviderExceptionGUIDInnerExceptionError Creating BusinessControllerClass 'SuperSKa.DNN.Modules.PictureGallery.Business.PictureController,SuperSKa.DNN.Modules.PictureGallery' of module(گالری تصاویر ساده) id=(491) in tab(115) and portal(3) FileNameFileLineNumber-1FileColumnNumber-1MethodStackTraceMessageSystem.Exception: Error Creating BusinessControllerClass 'SuperSKa.DNN.Modules.PictureGallery.Business.PictureController,SuperSKa.DNN.Modules.PictureGallery' of module(گالری تصاویر ساده) id=(491) in tab(115) and portal(3) ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.En ies.Portals.PortalController.GetCurrentPortalSettings() at DotNetNuke.En ies.Tabs.TabInfo.get_IsAdminTab() at DotNetNuke.En ies.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) at DotNetNuke.En ies.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo objPortalAliasInfo) at DotNetNuke.Common.Globals.GetHostPortalSettings() at DotNetNuke.Common.Globals.GetPortalSettings() at SuperSKa.DNN.Modules.PictureGallery.Business.PictureController..ctor() --- End of inner exception stack trace --- at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck) at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache) at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache) at System.Activator.CreateInstance(Type type, Boolean nonPublic) at DotNetNuke.Framework.Reflection.CreateObject(String TypeName, String CacheKey) at DotNetNuke.Services.Search.ModuleIndexer.GetModuleList(Int32 PortalID) --- End of inner exception stack trace --- at DotNetNuke.Services.Search.ModuleIndexer.GetModuleList(Int32 PortalID)Source

I checked EventLog table again, the error is this:

AssemblyVersion04.08.03PortalID0PortalNamebusiness.irUserID-1UserNameActiveTabID36ActiveTabNameصفحه اصلیRawURL/Default.aspxAbsoluteURL/Default.aspxAbsoluteURLReferrerUserAgentMozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2)DefaultDataProviderDotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProviderExceptionGUID2ac5d032-bfd8-4d86-87f1-78230b0fe052InnerExceptionObject reference not set to an instance of an object.FileNameFileLineNumber0FileColumnNumber0MethodDotNetNuke.Modules.Admin.Authentication.Login.DisplayLoginControlStackTraceMessageDotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Modules.Admin.Authentication.Login.DisplayLoginControl(AuthenticationLoginBase authLoginControl, Boolean addHeader, Boolean addFooter) at DotNetNuke.Modules.Admin.Authentication.Login.BindLogin() at DotNetNuke.Modules.Admin.Authentication.Login.ShowPanel() at DotNetNuke.Modules.Admin.Authentication.Login.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---Source

Also I removed the portal that I had added from Portals table in database.

Is the site is running ok if you don't try to login?

Yes. There is no problem to run the site and it works well.

First, make a good backup of the exiting database and web directory.  That way, you always restore to the current point.

Next, you should take a copy of your site and install it on a local system for experimentation.  Do all of your work on the local copy.  Once you get things repaired, you can move that to your live site.

I would try upgrading, and see if that fixes this problem.  I would first try upgrading to 4.9.5.  Try that and let us know if that solves the problem.  You'll be able to do that by copying the 4.9.5 upgrade package into your web directory and then browsing to the site -- again to this on a local copy.

Please tell me if it's right >>
"Steps to upgrade:
1. download 4.5.9 version
2. copy the zip file to root directory and unzip it
3. browse the site "
What will happen after that? Do we need to make any change in web.config file?

That's close.  For Step 2 -- unzip the Upgrade package and then copy everything to the root director.

Step 0 is MAKE BACKUPS!

You do not need to make any changes to web.config.  In fact, you SHOULD NOT make any changes.

Thanks for your replies!
But I still have some questions: What will happen after all these steps? What will I see when I browse the site?
My version of dotnetnuke has been localized. Is there any problem to upgrade it?

When you first browse to the site, you will see it go through the upgrade process.  If you set AutoUpgrade to false in web.config, you will have to manually browse to the Install/Install.aspx page to start the upgrade.

There may be some changes to localization if static text has moved.  You may have to upgrade or edit your existing language packs.

Again, all of those questions are reasons to do this on a local installation and not on the live site.

Hi!
Thanks a lot for your helps! I upgrade my dnn base site but the problem wasn't related to that.
 DNN login option in Host Setting -> <!--[if gte mso 9]> Normal 0 unctuationKerning/> false false false oNotPromoteQF/> EN-US X-NONE AR-SA ontGrowAutofit/> ontVertAlignCellWithSp/> ontBreakConstrainedForcedTables/> ontVertAlignInTxbx/> MicrosoftInternetExplorer4 <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-520082689 -1073717157 41 0 66047 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:0cm; margin-right:0cm; margin-bottom:10.0pt; margin-left:0cm; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:Arial; mso-bidi-theme-font:minor-bidi;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:Arial; mso-bidi-theme-font:minor-bidi;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:115%;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.WordSection1 {page:WordSection1;} --> <!--[if gte mso 10]> Authentication part had been disabled and must be enabled in database.

So easy and I didn't know this!