Exception Details: System.Data.SqlClient.SqlException: Invalid object name 'tablename'

Symptom
Exception Details: System.Data.SqlClient.SqlException: Invalid object name 'dbo.Events'.
Invalid object name 'dbo.Locations'.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Cause
Default schema is mismatch or no table with such name.


Solution
Change default schema for the login username to schema that is table schema.
Check table if exists.

คำสั่งใน sun solaris ที่ใช้แทนคำสั่ง yum หรือ apt-get

Instructions for Solaris package installation from Solaris Blastwave (CSW packages) site:

Run the following command for Solaris 10/Open Solaris (Intel and Sparc platforms)

pkgadd -d http://blastwave.network.com/csw/pkgutil_`/sbin/uname -p`.pkg

The above command will install CSWpkgutil package. This command can be used to install Solaris dependencies and indirect dependencies.

For example: The command below will install curl and its dependencies

# /opt/csw/bin/pkgutil --install curl

For more information about using pkgutil, click here

Limiting views on shared SQL server installations

For shared SQL Server installations, SSMS will allow all customers to see the names of other databases. You can change that default behavior with a SQL Server 2005 configuration change.

To do so, on your SQL 2005 servers, revoke "View Any Database" from public. Then, customers of a shared server, will only see their database, provided you've made the customer the owner of the database. An easy way to do this is with the stored procedure sp_changedbowner or with Alter Database.