SQL Server – Databases are Read-Only After Reattaching

I was moving some files around today and ran into this confusing issue. I had moved a Sitecore instance to a new folder but originally left the database in it’s old location, so I went and detached them in SQL Server Management Studio (SSMS) and then moved the files from on folder to another. After that I reattached them in SQL Server and found that they were all listed as Read Only.

No problem, I thought. I checked the folder and sure enough it was marked as Read Only, so I unchecked that and hit Ok. Same problem. I went back to the folder properties and it still said Read Only. From there I tried setting several inner folders and files individually but all of them had the same problem. How odd.

After a quick search and a few min on Stack Overflow I went and tried unsetting the Read Only property in SQL Server Management Studio and once again, no dice.

Eventually what worked for me was I went and gave my windows user full write access to the folder, since that’s who I was logging into SSMS as. At that point I still couldn’t unset the option in the Windows properties but I was able to go in and reattach it through SSMS and at that point it no longer listed them as read only.

Tags: , ,

  • Del.icio.us
  • StumbleUpon
  • Reddit
  • Twitter
  • RSS
read comments

Sitecore: The Name You Entered Is Not Unique

I had to wipe an instance of Sitecore today and start fresh. I deleted the instance using the installer, made sure to delete the App Pool and website in IIS. I removed any leftover files in c:\inetput\wwwroot and then when into SQL Management studio and deleted all of the databases it used. I then went to create a fresh instance using the same instance name and ran into this lovely error:

The Name You Entered Is Not Unique

Hmmm… What did I miss?

A quick Google and I found the answer, I just had to go into the registry and clean up a few things. I deleted everything under “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sitecore CMS” and then restarted the installer. After that it let me name the instance what I had previously used and I was able to continue installing with no issues!

Tags: , ,

  • Del.icio.us
  • StumbleUpon
  • Reddit
  • Twitter
  • RSS
read comments

HTTP Error 500.21 – Internal Server Error

I was installing Sitecore tonight on a fresh install of Windows and ran into this old error:

HTTP Error 500.21 - Internal Server Error
Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list

It wasn’t the first time I’ve seen this error, but I always shave to look it up when I run into it because I hadn’t committed the solution to memory.

A quick Google and a visit to Stack Overflow got me the answer I needed. It was because ASP.Net had not been installed into IIS, and that is pretty easy to fix. Just open up command prompt with admin privileges and run the following command:

"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe" -i

You should then see the following on the screen:

Microsoft (R) ASP.NET RegIIS version 4.0.30319.0
Administration utility to install and uninstall ASP.NET on the local machine.
Copyright (C) Microsoft Corporation.  All rights reserved.
Start installing ASP.NET (4.0.30319.0).
.....
Finished installing ASP.NET (4.0.30319.0).

At that point you can close command prompt and then go back to your web browser and refresh the page. It should load without issue!

Tags: ,

  • Del.icio.us
  • StumbleUpon
  • Reddit
  • Twitter
  • RSS
read comments
 Page 2 of 71 « 1  2  3  4  5 » ...  Last »