All Public Forums

About this Forum

Rick Stam — 2007-12-09T07:13:54Z

This Forum contains mostly brief notes and comments about issues encountered during web server software configuration and web systems development. The primary topics covered include ASP.Net, IIS, C#, VB.Net, DotNetNuke, and SharPoint development, among others. Guests are currently not allowed to make posts to this Forum. If you would like to make any comments, or just email me, please use my 'http://stamcr.com/dnn/Contact/tabid/312/Default.aspx'>Contact Page. Rick Stam

The site site_location could not be created. Value does not fall within the expected range.

Rick Stam — 2008-02-22T16:55:52Z

Update: I did not have to apply this hotfix. Apply the latest WSS and MOSS Service Packs instead... They fixed the problem... Error: The site site_location could not be created. The following exception occured: Value does not fall within the expected range. THIS IS AN QUOTE FROM THE MICROSOFT HOTFIX PAGE: 'http://support.microsoft.com/kb/937207'>http://support.microsoft.com/kb/937207

Issue that the hotfix package fixes

This hotfix package fixes the following issue that was not previously documented in a Microsoft Knowledge Base article: A user tries to create a My Site site in a portal site that has the Enable Self-Service Site Creation setting enabled in SharePoint Server 2007. However, the user cannot create the site. Instead, the user receives the following error message:
There has been an error creating the personal site. Contact your site administrator for more information.
Additionally, the following events are logged in the Application log:
Event Type: Error Event Source: Windows SharePoint Services 3 Event Category: Topology Event ID:? Date: date Time: time User: N/A Computer: computer_name Description: The site site_location could not be created. The following exception occured: Value does not fall within the expected range.
Solution: Go to the page (above) and email Microsoft for a hotfix...
Update: I did not have to apply this hotfix. Apply the latest WSS and MOSS Service Packs instead... They fixed the problem...

DCOM errors in the Application or System log

Rick Stam — 2008-02-22T16:04:54Z
I've gotten this error several times, and just wanted to include a reference to Microsoft's solution page (for my personal reference): Description: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {AppGUID} to the user User_Name SID User_SID. This security permission can be modified using the Component Services administrative tool. Microsoft's solution page for this problem: 'http://support.microsoft.com/kb/899965'>http://support.microsoft.com/kb/899965

Changing DNN Web Search

Rick Stam — 2007-12-14T09:25:33Z
To remove the Web / Site search options edit your skin's .ascx file as follows: <dnn:SEARCH runat='server' id='dnnSEARCH' showWeb='False' showSite='False' /> To change the Web search to use your Google Adsense key: edit   \admin\skins\App_LocalResources\Search.ascx.resx change the value after pub- to your Google Web Search Id <value>http://www.google.com/custom?hl=en client=pub-9770992166002654 Read more at: http://blog.scottschecter.net/2007/05/30/DisableNewSearchFeaturesInDotNetNuke452.aspx

FCK Editor Wraps ALL Text Entries with (P) tags

Rick Stam — 2007-12-14T06:54:30Z
This causes Firefox to always display some blank space before the first line of text, while IE does not. For the long story, and fix options read the DotNetNuke Forum post at: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/127/threadid/153307/scope/posts/Default.aspx Suggested fixes: 1) In the fckconfig.js file replace (in \Providers\HtmlEditorProviders\Fck\FCKeditor) FCKConfig.EnterMode = 'p' ; with FCKConfig.EnterMode = 'br' ;   /* or 'div' */ 2) Use CSS to set the properties to: p {margin-top: 0px; margin-bottom: 3px;} Both solutions have favorable arguments: The first avoids FCK from modifying the HTML, while the second provides more standardized HTML and a uniform way of controlling the tag formating. Also, check for updates to the DNN FCK Editor Provider, since these issues are currently being addressed. OK, I've had better results with the CSS solution. Setting the margin-top to 0 solves the problem with Firefox, but I'd rather not set the margin-bottom (use the default, which follows the font size). So you can set p { margin-top: 0px; } either in the \Portals\_default\default.css or in the appropriate skin.css, if you don't want to change the default for all portals.

Pinned Threads Don't Show in Agreggated Forum

Rick Stam — 2007-12-09T21:12:42Z
Pinned Threads Don't Show in Agreggated Forum. This is a result of the (way too complex!) dbo.Forum_Thread_GetAll() stored procedure. Quick Fix (Hack): Remove (or comment out) the T.IsPinned = 0 condition from the SQL WHERE clauses (3 places) in the dbo.Forum_Thread_GetAll() stored procedure. Note: I can't guarantee that this will not cause undesired side effects for other functionalities of the site. So far I haven't seen any...

HTML Text Disappears from Blog Entry Text when edited

Rick Stam — 2007-12-09T00:05:42Z
There is an issue when editing blog entries that contain textual HTML code in the text. The blog's EditEntry.ascx.cb does a call to HtmlDecode() in the Page_Load Event that eliminates any HTML code in the entry's text. Quick Fix (Hack): Change to the following code in /DesktopModules/Blog/EditEntry.ascx.vb: Change:   teBlogEntry.Text = Server.HtmlDecode(m_oEntry.Entry) to:              teBlogEntry.Text = m_oEntry.Entry Recompile and copy the Blog.dll to the dnn\bin directory of the production server.

Careful Deleting DotNetNuke Site Users

Rick Stam — 2007-12-08T09:07:06Z
Be carful when deleting users from a DotNetNuke site. You should delete all the user's 'owned' content (such as the users Blog) before deleting the user, or you might end up with 'orphaned' records in the database. You may then get the infimous 'Object Reference not set to an Instance of the Object' errors :( A safer approach could be to 'Unauthorize' the user instead of deleting it. This will also prevent the user from re-regestering again with the same credentials. Note: To be fair to the DotNetNuke developers, I'm not claiming that this 'orphaned records' problem is very common, but I have had it happen to me (when deleteing a user that owned a blog). A good recomendation, as always, is to make backups before doing anything that could cause problems.