Problem: While surfing around, I came across a website whose content encoding is not being supported with my latest Firefox v3.5.4 showed me unsupported compression error.

Content Encoding Error
The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.
* Please contact the website owners to inform them of this problem.

Solution: As per my knowledge web-servers generally use GZ compression and Firefox well supports that. Then what’s wrong here? Digging a bit into Firefox’s ‘about:config‘, I did a search for ‘gz’. The setting network.http.accept-encoding was set to gzip,deflate. What’s wrong? Let’s try setting it gzip,deflate,gz. And it worked!. The catch here is gzip and gz are two different extensions used for the same gzip compression. Eventually, the questions is who’s in fault, Firefox or the website?

- ankit

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified)

The database project requires an active database connection to load at design time. Probably it uses that to compile/verify scripts. The problem here is Visual Studio is not able to connect to any such instance. Following are few solutions (these worked for me)

1. Make sure the instance to which you want to connect is running and allows remote connections.
2. After performing step 1, if it is still not loading then you may need to start the SQL Browser Service. Make sure it’s running.
3. If the problem is still there, it has to be fixed from Visual Studio itself. Actually database project do not store to which instance it can connect. It’s a Visual Studio setting.In VS2008 go to Tool > Options > Database Tools > Design-time Validation Database > Connection Options. Specify your instance name here like “\SQLEXPRESS”

If the problem is still there post it to MSDN forums

Ankit

1. Make sure the webpart class is inherited either from Microsoft.SharePoint.WebPartPages.WebPart or System.Web.UI.WebControls.WebParts.WebPart
2. The webpart class needs to be declared public.
3. Safe controls entry in web.config file.
4. If you are referring a webpart from GAC (i.e. assembly containing webpart class is placed in GAC) make sure the GAC version is the latest build and IIS is re-started.

- Ankit

My solution for this: Installed SSP (Shared Services Provider) and this problem is solved!
[ Edited:2008-03-24
I got this error while playing with stsadm.exe command
]