Hi,
This time, I got a new Server Error
"Fill: selectcommand.connection property has not been initialized" in
another asp page. This also comes only ONCE IN A WHILE.
The error is coming in the line with "Fill" in the code given below
*-------------------------------------
DBConnection = OnlineConn.OnlineDBConnection(Database)
Sql = KeyWord
Dim SqlCommand As New SqlCommand(Sql, DBConnection)
Dim SqlAdapter As New SqlDataAdapter(SqlCommand)
Dim DataSet As New DataSet
SqlAdapter.Fill(DataSet)
*-------------------------------------
While linking this with my previous error " Object variable with block ... "
, I was wondering if this error has anything to do with the database
connection.
Will this happen if the asp.net page is refreshed frequently ?
Thanks in advance for your help
Rgds,
Majo
"majo" wrote:
> Hi Roger,
>
> I havent solved my problem yet.
>
> I was wondering if it has something to do with database locks. I checked for
> any locks, but couldnt find any at the time of the error.
>
> I have no idea how to solve this problem.
>
> Please let me know if you come across any solutions.
>
> Thanks
> majo
>
>
> "" wrote:
>
> > > We have hosted an asp.net application in a windows 2003 server machine. The
> > > application runs well but ONCE IN A WHILE it comes up with the error, "Server
> > > Error in '/CreditApplication' Application."
> > > The error details are given below.
> >
> > Did you ever resolve this issue? I'm currently experiencing something
> > similar. An ASP.NET application was running fine on a Windows XP
> > machine. But now that we've moved it to Windows Server 2003, it
> > *sometimes* gets the error that you described:
> >
> > System.NullReferenceException: Object variable or With block variable
> > not set.
> > at Microsoft.VisualBasic.CompilerServices.LateBinding .LateGet(Object
> > o, Type objType, String name, Object[] args, String[] paramnames,
> > Boolean[] CopyBack)
> >
> > This is while accessing a COM object. Once again, it's worked
> > flawlessly on XP for quite a while now, but seems to occasionally have
> > problems on Windows Server 2003 (maybe the operating system isn't the
> > main issue, but I don't know what other differences exist).
> >
> > - Roger
> >
> >
|