Showing posts with label Errors With Solutions. Show all posts
Showing posts with label Errors With Solutions. Show all posts

How to fix the system cannot find the file specified. (Exception from HRESULT: 0x80070002) (EnvDTE80)

How to solve the system cannot find the file specified error on receive location

If u got errors like (The system cannot find the file specified. (Exception from HRESULT: 0x80070002) (EnvDTE80))

Follow Below Steps for solution:-

1) Go to the Control Panel

2) Add or Remove

3) Repair .Net Framework

If Above Steps work, then ok. Other wise do Repair Sql server at step of 3.

Errors in visual basic with solutions

Most of times this kind of error comes at compile time in .Net so try to solve this kind of error and clear logic and make your logic perfect.

  1. 'variabler' is not a member of 'System.Data.DataTable'.
  2. 'variable' is not a member of 'System.Data.DataTable'.
  3. 'close' is not a member of 'System.Data.DataTable'.
  4. 'variable' is ambiguous.
  5. Type 'DataAccess' is not defined.

How to solve unmatching closed parenthesis in asp.net

Error 5 Invalid expression term 'protected'
Error 2 } expected
Error 7 Only assignment, call, increment, decrement, and new object expressions can be used as a statement

this kind of error comes because of unmatching closed parenthesis.

{}.

Logon failed. Details: crdb_adoplus : Object reference not set to an instance of an object. Error in File C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\temp_1abdb42c-f439-405a-a07f-627f8efa7dff {0E9A349B-44C0-44EC-BD65-2DF0B8EF4F79}.rpt:
Unable to connect: incorrect log on parameters
This kind of error comes during Displaying tha data using crystal report

Solve not all code paths return a value errors

how to solve this problem when occur during Compiling time


Data Access Layer (DAL)

using System;
using System.Data;
using System.Configuration;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Data.SqlClient;

public class AddDal

{
string constr = ConfigurationManager.ConnectionStrings["connection"].ToString();
SqlConnection con=new SqlConnection();
public AddDal()
{
}
public int Insert(int id , string name)
{
int i = 0;
con.ConnectionString = constr;
con.Open();
SqlCommand cmdinsert = new SqlCommand("insertConnection", con);
cmdinsert.CommandType = CommandType.StoredProcedure;
try
{
cmdinsert.Parameters.AddWithValue("@id", id);
cmdinsert.Parameters.AddWithValue("@nam", name);

return cmdinsert.ExecuteNonQuery();

}
catch
{throw;}
finally
{
cmdinsert.Dispose();
con.Close();
con.Dispose();
}}}
Business Access Layer (BAL)

using System;
using System.Data;
using System.Configuration;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
public class AddBal
{
public AddBal()
{ }
public int Insert(int id , string name)
{
AddDal aDal=new AddDal();
try
{ return aDal.Insert(id , name); }
catch
{ throw; }
finally
{ aDal=null; }
} }

Solve object or column name is missing or empty errors

An object or column name is missing or empty. How to solve

3.1.An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Add a name or single space as the alias name.
This error comes during Execution of Sql-server queries.
it shows that there is error in query like double "" ''fieldname '' sometimes it need like 'fieldname'
only single ' or somewhere opening and closing parenthesis.
3.2.Incorrect syntax near ','

Msg 102, Level 15, State 1, Line 18
Just click on error line and check syntax

3.3The query uses non-ANSI outer join operators ("*=" or "=*"). To run this query without modification, please set the compatibility level for current database to 80 or lower, using stored procedure sp_dbcmptlevel. It is strongly recommended to rewrite the query using ANSI outer join operators (LEFT OUTER JOIN, RIGHT OUTER JOIN). In the future versions of SQL Server, non-ANSI join operators will not be supported even in backward-compatibility modes.