I was doing a SharePoint reinstall at a client site today and was clearing out some of the databases on the sql server when all the sudden with 3 db’s left I got this nice Error message 4064 greeting me, and then I couldn’t log into SQL anymore.  After a few minutes of playing around I went onto the google machine and found the answer.

Turns out I detached the DB that was the set as the default database for the current user I was logged in with.  After some searching, turns out this is a pretty quick fix.

C:\> sqlcmd -E -d master


2> GO

Obviously change “[BUILTIN\Administrators]” to whatever login your having a problem with.  In addition, since my sql server was clustered, I had to specify the server name as well in with the sqlcmd, so mine was “sqlcmd –S SQLSERVERNAME –E –d master”

*** sqlcmd is a command that comes with SQL Server, do a search in the sql server program files to find it.

After the above I was all set, able to login to the server again, and finish up my work.

Posted in:   Tags:

Ideally the easiest way to setup SSL with SharePoint is when you create the web application to check off that you plan on using SSL, this will setup the AAM for you and save you a few steps (Although you still need to generate the cert, install it, etc.).


Past few times I've created web applications, SSL wasn’t a requirement at the beginning and had to be configured after the fact.

First, you’ll need to generate a CSR request from the IIS website.  Make sure you do this from the correct site, otherwise the SSL won’t be valid.

How to Generate a CSR from IIS

Steps for how to generate a CSR from Verisign












Send the CSR request off to your certificate authority.  They will send you a valid certificate that you can then install on the IIS site

How to Install SSL Certificate in IIS

Steps for how to INSTALL a certificate from Verisign


Open your IIS site that you want to install the SSL cert onto and click the “Server Certificate” button




IIS knows that you initiated an SSL request, so it asks if you want to process that request now and install the SSL cert that matches that request.


Select the SSL cert that you received from your SSL authority


Select the SSL port number that you want you use.  Default is 443, but be sure to know that only 1 site can have SSL running on port 443 for 1 IP address.  Do have multiple sites using SSL on port 443, you’ll need multiple IP addresses and each site needs to be on a separate IP address.


If the cert if valid, you’ll see a summary of its information.


Hit FINISH when you are done to install the SSL cert.


If you look at the IP configuration for your website now, you should see that you know have an entry for SSL with port 443.

FYI, I just recently found this out but IIS can ONLY do SSL on port 443 on 1, yes 1, site per IP address EVEN with host headers.  You have 2 options to get around this, 1) use a different port for SSL if you only have 1 IP address or 2) Add more IP addresses to the server and assign your SSL sites appropriately, 1 per IP address.

After all the above, if you go to your SharePoint site, you should now have it working under SSL.



Be sure to take a look in the AAM (alternate access mappings) to make sure you have entries for SSL for your site.


Force SSL

To force users to use SSL all the time, you have a few options

In order to make sure that the sites are access over SSL you need to force the request to always go over HTTPS. To accomplish this, a simple HTML page with some basic javascript is used.

Create the redirect HTML page with the following code:



<SCRIPT type=text/javascript>
if (location.protocol != 'https:')
window.location = 'https://'+ location.host + location.pathname + location.search;
//alert(location.host + location.pathname + location.search); Just for sanity check
// -->



Save the file as “redirectssl.htm” and save it to c:\inetpub\wwwroot. The reason for saving it to this location is so that multiple sites can access it and you only need 1 file to keep updated.


Open IIS manager and select properties on the site which you want to force SSL on.


Go to the Custom Errors tab and you need to change the 403;4 to point to our redirectssl.htm file.


Click edit on 403;4 and enter in the location to our “redirectssl.htm” and hit OK.


In addition we need to make sure that the IIS site needs to force the site to require SSL, that way it will throw the 403.4 error if someone access it through HTTP.

Perform an IISRESET

IIS redirect (Alternative SSL redirect option)

Another way to redirect to SSL is to use whats natively built into IIS.  I am not an expert on this solution but it looks promising as well depending on your specific needs.  If you go into an IIS site and goto the Home Tab, you’ll see the option for “a redirection to a URL” and then the “Redirect to:” field lets you specify where to redirect to.  IIS has a redirect syntax that you can use to redirect users to a site and can then force SSL as well.


IIS Redirect Syntax


Issues with Search

Forcing SSL tends to cause issues with the search crawler if not corrected.  Go into search settings and make sure that your crawler settings are point to HTTPS and not HTTP anymore.  SPS3 / SPS3S




Good link that walks through at a low level what happens behind the scenes over the wire for HTTPS


Posted in:   Tags:

Showed up to work awhile back and got an email from a client stating that their SharePoint farm was reporting "The trial period for this product has expired".

Even with valid licenses keys (we validated 3 times with MS to make sure), we got an error message saying that license was expired on only 1 of the WFE’s, causing WSS functions to work fine (team sites, etc.), but ANYTHING MOSS related would throw the error message.  Since the WFE’s were load balanced, we were able to test them individually so I was able to pinpoint which one had the issue.


I decided to reinstall the problem WFE.  After reinstall, things seemed to clear up and we were fine….for about 2 months when the OTHER WFE decided to act up and throw the same error message.  At this point, I reinstalling would probably only cause the issue to go away for awhile, then we’d hit the problem again.

I search google high and low and didn’t come up with a fix.  Some sites said to make sure that your app pool accounts were admins, or in the SharePoint Admin Group on the server, or in the local admins group.  Frankly I wasn’t confident with this solution, nor did it work for me. 

I checked the SharePoint ULS logs and came up with the following info which helped me track down the problem files, but not the solution.


10/03/2008 14:34:45.75     w3wp.exe (0x07E0)                           0x027C    CMS                               Publishing Provisioning           1ght    Medium      Publishing Feature activation event handled.    
10/03/2008 14:34:45.77     w3wp.exe (0x07E0)                           0x027C    Office Server                     Setup and Upgrade                 78ya    High        Microsoft.Office.Server.Administration.LicensingException: An error was encountered getting expiration info. ---> System.DllNotFoundException: Unable to load DLL 'OfficeServerSettings.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)     at Microsoft.Office.Server.Administration.Licensing.NativeMethods.GetExpirationTime(Int64& expirationTime)     at Microsoft.Office.Server.Administration.Licensing.GetExpirationFileTimeFromRegistry()     --- End of inner exception stack trace ---     at Microsoft.Office.Server.Administration.Licensing.GetExpirationFileTimeFromRegistry()     at Microsoft.Office.Server.Administration.Licensing..cctor()    
10/03/2008 14:34:45.77     w3wp.exe (0x07E0)                           0x027C    CMS                               Publishing                        98e6    Monitorable    The trial period for this product has expired.    
10/03/2008 14:34:45.77     w3wp.exe (0x07E0)                           0x027C    CMS                               Publishing Provisioning           75ot    Unexpected    Publishing Feature activation failed. Exception: Microsoft.SharePoint.SPException: The trial period for this product has expired.     at Microsoft.SharePoint.Publishing.CmsSecurityUtilities.EnsureEvaluationNotExpired()     at Microsoft.SharePoint.Publishing.PublishingFeatureHandler.FeatureActivated(SPFeatureReceiverProperties receiverProperties).    

Another solution was saying that McCaffe was blocking it.  Again, I tried everything and couldn’t find anything to back that up.

I spent hours in front of Sysinternals process monitor and process explorer but again, I didn’t find anything other than what I knew.  I even tried explicitly giving permissions to the folder where I knew SharePoint was looking for the files.  I even copied known good files to the problem WFE but no luck.

I broke down and decided to use one of our MS support tickets.  Thankfully it was a “production” issue, which meant that we got immediate support and support from a highly qualified support tech.  He instantly knew what the problem was and was able to give us the remedy.


  • Add "%CommonProgramFiles%\Microsoft Shared\Web Server Extensions\12\Bin;%ProgramFiles%\Microsoft Office Servers\12.0\Bin;" to the MIDDLE of the PATH environment variable.
  • Reboot server

We had to paste this in our PATH variable and paste it somewhere in the middle.  Apparently when updates in windows occur, installs, etc. but sometimes they truncate off the last section of the PATH variable for some reason.  Due to this, SharePoint can’t find the license code that it needs and therefore throws the error message.

After adding the strings to the path variable, make sure to restart the PC so that the settings take affect.

Additionally, we had to apply the “fix” to all servers in the farm to make sure that this message wouldn’t come up again.

Posted in:   Tags:
tony testa posted on June 22, 2009 09:37

I’ve put my house up on the market so I am going to have to find a new home for my web server for the time being.  Luckily I have some friends that live only about 15 minutes away whom are kind enough to let me leave my server there till I find a new place.  I’m going to move the server sometime this evening and get it setup in the new place.  I’m hoping for only about 2-3hrs of downtime, but we all know how that goes. 

Posted in:   Tags:

First, as a CYA, I don’t endorse any of these products so take my opinion with a grain of salt.

I see this a lot on the MSDN forums as well as pretty much every client wants as well.  So the question is always the same, either they don’t like the out of the box SharePoint forums, or the out of the box SharePoint forums don’t meet their specific needs.

First, before I mention ANY 3rd party options, etc. just keep in mind that most likely no one solution will meet your specific needs, most likely it will only meet a most or only a few of them.  Therefore my recommendation up front is this: if you have specific needs, or detailed needs, have a look at the 3rd party options, but I think most likely you find that writing your own custom forums for SharePoint will be your best option, although its not exactly an easy process.

To my knowledge, below are your main options that don’t require you to code anything, just buy it or download it install it, and your all set..

SharePoint Forums Project

Link: http://www.codeplex.com/SPFORUMS

Cost: Free (as is, no support)

My Thoughts: I’ve personally used this on a project with mixed results.  I would say the downfalls of SPForums are more due to the client specific needs than SPForums.  The client wanted NTLM, FBA, and anonymous access to the forums, and SPForums just wasn’t built for that.  It did work as advertised for NTLM so I give it props for that.  Also, all the code is given, so you can modify it to meet your specific needs.  I think I modified it to allow attachments and it wasn’t all that difficult to do so.  It also had a so so administration interface as well.  All data for the forums was stored in backend hidden lists inside of SharePoint which was nice because there was no extra DB dependency.



KwizCom SharePoint Forum WebPart

Link: http://www.kwizcom.com/ProductPage.asp?ProductID=716&ProductSubNodeID=717

Cost: Contact KwizCom

My Thoughts: I haven’t personally used this one, but frankly nothing on their website looks-wise makes me want to run out and try this.  In addition, they bundle it with this web part “bundles” which makes me really wonder how good the forum is if its offered in their bundles, seems almost like its an after thought to them.  Again, I haven’t used it, so don’t take my word for it.  As with most vendors though, they have a trial that you can download and try.

KWizCom SharePoint Forum Web Part


Lightning Storm Forums for SharePoint

Link: http://www.lightningtools.com/lightning-storm-forums-for-sharepoint/default.aspx

Cost: Contact Lightning Storm (according to their site, $600.00)

My Thoughts: Based on pure looks/functionality, this looks like probably the one that I would actually pay money for if I were to use it.  In addition, they offer a trial download, so if you have questions about it, you can always try before you buy.


DataSprings MOSS Forums Web Part

Link: http://www.datasprings.com/Products/SharePointWebParts/MOSSForums/tabid/822/language/en-US/Default.aspx

Cost: ??? couldn’t tell from website

My Thoughts: As with the KwizCom web part, nothing visually attracts me to this forum but their feature set looks promising and seems to touch on  most of the hot button forum features.  The benefit I see here is that it looks to take on the style of the site your own, so if you use different themes/styles, this web part MAY inherit that.  They also offer a trial of the web part.

SharePoint Forums Web Part

Posted in:   Tags:
The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2017 Tony Testa's World