Problems with CKS:EBE

Topics: Enhanced Blog Edition
Apr 20, 2009 at 3:26 PM
Okay, here is the situation. We are attempting to get CKS:EBE up in running. We have installed it in our test environment and it works 100%. We installed it into or production environment, the installation goes without any problems, but it does not work. The feature activates not problems, we can view/modify the settings no problem. However, when we go to the blog we are sent to the default blog instead of the new CKS:EBE setup blog. If we manually change the URL from default.aspx to home.aspx, we see the template, but if we try to use any links we get a 404. The only difference between the test environment and the live environment is, we have a 2006 ISA server in production and don't in test. I have checked to web.config to make sure the changes have been made, they are there. I have checked file permissions, all are correct. I have checked the assembly everything is there correctly. I am running out of ideas on what could cause this. We are getting no errors logged what-so-ever. If anyone has any idea what could cause this problem I would greatly appreciate the info. If you need any other information, just let me know and I will get that here.

Thanks!
Developer
Apr 20, 2009 at 7:42 PM
Hi,
you can try to deactivate the web and webapplication feature, and then reactivate them both.
While you are reactivating them, please run debugview from sysinternals, as it will give some additional hints where to look at.

René
Apr 20, 2009 at 9:48 PM
Okay,

I have done that and I can see where the error (at least I think) is happening.... I have included what I see on the test server verse the production server. I have done the exact same action on each server...

Basically all I did was activate the feature and then click on a link...

As for deactivating the web, are you talking about the web in IIS? I only disabled/enabled the feature for now (Have to wait until scheduled downtime to take anything major down) .

Here are the results:
Test Server:
00000000    0.00000000    [4008] Enabling Events    
00000001    0.02314903    [4008] Events enabled    
00000002    0.05224435    [4008] Showing the Categories column    
00000003    0.06527059    [4008] Updating post list    
00000004    0.12006526    [4008] Adding the themes feature    
00000005    1.51834834    [4008] Setting up linkback lists    
00000006    1.52476311    [4008] Web Feature Activated    


Production Server:

00000049    389.20327759    [5684] Enabling Events    
00000050    389.22442627    [5684] Events enabled    
00000051    389.26321411    [5684] Showing the Categories column    
00000052    389.28063965    [5684] Updating post list    
00000053    389.41949463    [5684] Adding the themes feature    
00000054    390.75134277    [5684] Setting up linkback lists    
00000055    390.76153564    [5684] Web Feature Activated    
00000056    398.88668823    [5684] System.Threading.ThreadAbortException: Thread was being aborted.     
00000057    398.88668823    [5684]    at System.Threading.Thread.AbortInternal()     
00000058    398.88668823    [5684]    at System.Threading.Thread.Abort(Object stateInfo)     
00000059    398.88668823    [5684]    at System.Web.HttpResponse.End()     
00000060    398.88668823    [5684]    at System.Web.HttpResponse.Redirect(String url, Boolean endResponse)     
00000061    398.88668823    [5684]    at System.Web.HttpResponse.Redirect(String url)     
00000062    398.88668823    [5684]    at CKS.EBE.BlogHttpModule._app_PostAuthorizeRequest(Object sender, EventArgs e)
Developer
Apr 21, 2009 at 9:45 PM
Hi,
what I meant was to deactivate/activate the two features. Nothing more. You did the right thing :-)

The ThreadAbortException is nothing to worry about. It is always thrown, if we redirect via program code. I will change that one in the code, so the exception is not thrown any more.

Could you also post the debugview output while you try to access your blog after the features have been activated?

René
Apr 23, 2009 at 9:58 PM
First thank you for your help. That log was exactly what debugview showed after we activated and tried to use the feature. I have listed below the steps we went through.


First Deactivated the feature on all the sites using it.
Second Deactivated the feature in central admin
Third started debugview
Fourth activated the feature in central admin
Fifth activated the feature on a site
Sixth went to that blog (which was still pulling the theme from the default sharepoint)
Seventh clicked on a link to a post, which returned a 404

The interesting part is if we go to home.aspx instead of default.aspx the EBE  theme does load.
Also when we went to a link the link changed from https://SITE/sites/it/DevTeam/TestBlog/Lists/Posts/Post.aspx?ID=1
to theEBE format: https://SITE/sites/it/DevTeam/TestBlog/archive/2009/04/21/test.aspx

Here again is the log, which is exactly what I had before:

00000000    0.00000000    [6204] Enabling Events    
00000001    0.04357048    [6204] Events enabled    
00000002    0.07699788    [6204] Showing the Categories column    
00000003    0.09966339    [6204] Updating post list    
00000004    0.49998304    [6204] Adding the themes feature    
00000005    2.56445813    [6204] Setting up linkback lists    
00000006    2.57208467    [6204] Web Feature Activated   

- The exception appeared after I clicked on the link to a post

00000007    14.16861057    [6204] System.Threading.ThreadAbortException: Thread was being aborted.     
00000008    14.16861057    [6204]    at System.Threading.Thread.AbortInternal()     
00000009    14.16861057    [6204]    at System.Threading.Thread.Abort(Object stateInfo)     
00000010    14.16861057    [6204]    at System.Web.HttpResponse.End()     
00000011    14.16861057    [6204]    at System.Web.HttpResponse.Redirect(String url, Boolean endResponse)     
00000012    14.16861057    [6204]    at System.Web.HttpResponse.Redirect(String url)     
00000013    14.16861057    [6204]    at CKS.EBE.BlogHttpModule._app_PostAuthorizeRequest(Object sender, EventArgs e)



Aug 3, 2009 at 6:48 PM

Well it's been a while since I spent any time investigating this problem. Today, I decided to try and figure out what was going on. I know what is causing the problem, but was hoping someone would be able to shed more light on the problem. This is entirely being caused by us running HTTPS on our production system. I accessed the exact same blog with HTTP and EBE functioned 100% correct. When I access it via HTTPS none of the http handling seems to be working. IE We get 404s when an EBE page is being served.

Developer
Aug 5, 2009 at 8:53 PM

Hi,

the problem exists if you do not enter the URL which the webapplication knows.

To solve it, you can either enter the correct URL or set up "Alternate Access Mappings".

I've implemented a better error handling. If the feature activation fails, it will not tell you why.

René

Developer
Aug 5, 2009 at 8:55 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.