A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified) 

I got this error when I started using LoginStatus Control. It seemed very wiered. After lot of struggle I found out this is caused by CSSAdapters.

Open CSSFriendlyAdapters.browser  (or something similar)

Look for this line and remove or comment it.

<adapter controlType="System.Web.UI.WebControls.LoginStatus"

 adapterType="CSSFriendly.LoginStatusAdapter" />

Now you LoginControl will work without any issues.

The Microsoft Jet database engine could not find the object ‘ ‘. Make sure the object exists and that you spell its name and the path name correctly.

Today I got this error when I was trying to import a CSV file into Access database 2003. Even though I was trying to load this from my C: drive I was getting this error.

After couple of tries found that filename “currentproc.20090531.csv” had an extra “.”  and that was the problem.

So renamed the file to 20090531.csv and it worked

Happy importing.

SSIS 2005 Business Intelligence

Unable to instantiate XML DOM document, please verify that MSXML binaries are properly installed and registered.

 Other variations are  Failed to save package file “.dtsx” with error 0x8002801D “Library not registered.”

The reason you see this error is because MSXML got corrupted.

The fix is

1. Close Studio / Business Intelligence

2. Download Latest MSXML 4.0 (sp3)  as of today.

3. Install it. Done

2a. Some cases you may need to install MSXML 6.0.

Could not load type  Namespace.Class or Global.asax

This is one of the annoying error messages in an Asp.net application. 

Few verifications can fix this error.

1. Make sure you have right Asp.net version in IIS

2. Make sure the Application Root Namespace and Inherits=”" (on .aspx page) are the same (including case)

3. If you are using Multiple Projects (Project > Sub Project) make sure the Build Output Path (Project Properties > Compile) is pointing to Main application.

If you have come across any other scenario feel free to write it.

Server Application Unavailable

The web application you are attempting to access on this web server is currently unavailable.  Please hit the “Refresh” button in your web browser to retry your request.

Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.

———

Solution

Open Windows Explorer and  navigate to project folder

Right Click > Properties > Security Tab

Make sure following users have atleast READ access to the folder (and subfolder)

1. ASPNET
2. IUSR_{machinename}
3. IIS_WPG

Now test your url.