471,073 Members | 1,452 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,073 software developers and data experts.

MSAccess problems

Hi,

I'm having my ASP.NET application hosted at a Windows 2003 server (IIS6).
This works almost all the time (I have uptimes of 100% on most days), but
then all of a sudden a few days in a row I have the following phenomenon:

..aspx still get processed, but as soon as any of them try to read/write to a
MsAccess database (using DSNLess OleDBConnection) it's timing out.

This happens for a period of about 40 minutes and then all of a sudden
everything starts working again without any user intervention.

Has anyone had the same problems ?

Thanks,

Wim
Nov 18 '05 #1
4 1383
Access is not designed for Internet use. It is designed as a desktop/LAN
database. However, ANY OLE DB-compliant database can be used in an ASP.Net
application. The upside is cost; an .mdb database is free of licensing fees.
The downside is performance. You may have too many concurrent users for
Access to handle at times. Check your web server logs to see if there is a
correspondence of heavy traffic to these errors.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Annick Van Hoof" <me@here.nospam> wrote in message
news:Oc**************@TK2MSFTNGP09.phx.gbl...
Hi,

I'm having my ASP.NET application hosted at a Windows 2003 server (IIS6).
This works almost all the time (I have uptimes of 100% on most days), but
then all of a sudden a few days in a row I have the following phenomenon:

.aspx still get processed, but as soon as any of them try to read/write to a MsAccess database (using DSNLess OleDBConnection) it's timing out.

This happens for a period of about 40 minutes and then all of a sudden
everything starts working again without any user intervention.

Has anyone had the same problems ?

Thanks,

Wim

Nov 18 '05 #2
WL
Hi Kevin,

Thanks for your reply: you are absolutely right that a (MS) SQL Server is a
lot beter.
However, the problem occurs on a server that is not really used by the
public. I have a Alertra (uptime checker) account running every 10 minutes
(and that's it).
So concurrent user would not be the problem.

Moreover, when a timeout occurs on one Access databases: all other ASP.NET
pages that are even using other MsAccess files are timing out.
It just seems as if there's a problem with the OleDbConnection.

Can OleDb do connectionpoolin on MsAccess connections ? If so: this might be
a problem ?

Thanks,

Wim

"Kevin Spencer" <ks******@takempis.com> wrote in message
news:eD**************@TK2MSFTNGP10.phx.gbl...
Access is not designed for Internet use. It is designed as a desktop/LAN
database. However, ANY OLE DB-compliant database can be used in an ASP.Net
application. The upside is cost; an .mdb database is free of licensing fees. The downside is performance. You may have too many concurrent users for
Access to handle at times. Check your web server logs to see if there is a
correspondence of heavy traffic to these errors.

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Annick Van Hoof" <me@here.nospam> wrote in message
news:Oc**************@TK2MSFTNGP09.phx.gbl...
Hi,

I'm having my ASP.NET application hosted at a Windows 2003 server (IIS6). This works almost all the time (I have uptimes of 100% on most days), but then all of a sudden a few days in a row I have the following phenomenon:
.aspx still get processed, but as soon as any of them try to read/write
to a
MsAccess database (using DSNLess OleDBConnection) it's timing out.

This happens for a period of about 40 minutes and then all of a sudden
everything starts working again without any user intervention.

Has anyone had the same problems ?

Thanks,

Wim


Nov 18 '05 #3
> Can OleDb do connectionpoolin on MsAccess connections ? If so: this might
be
a problem ?
You got me there, WL. I haven't used Access in a web app in years. Have you
tried searching the Knowledge Base?

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"WL" <me@here.nospam> wrote in message
news:e$**************@TK2MSFTNGP09.phx.gbl... Hi Kevin,

Thanks for your reply: you are absolutely right that a (MS) SQL Server is a lot beter.
However, the problem occurs on a server that is not really used by the
public. I have a Alertra (uptime checker) account running every 10 minutes
(and that's it).
So concurrent user would not be the problem.

Moreover, when a timeout occurs on one Access databases: all other ASP.NET
pages that are even using other MsAccess files are timing out.
It just seems as if there's a problem with the OleDbConnection.

Can OleDb do connectionpoolin on MsAccess connections ? If so: this might be a problem ?

Thanks,

Wim

"Kevin Spencer" <ks******@takempis.com> wrote in message
news:eD**************@TK2MSFTNGP10.phx.gbl...
Access is not designed for Internet use. It is designed as a desktop/LAN
database. However, ANY OLE DB-compliant database can be used in an ASP.Net
application. The upside is cost; an .mdb database is free of licensing fees.
The downside is performance. You may have too many concurrent users for
Access to handle at times. Check your web server logs to see if there is a correspondence of heavy traffic to these errors.

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Annick Van Hoof" <me@here.nospam> wrote in message
news:Oc**************@TK2MSFTNGP09.phx.gbl...
Hi,

I'm having my ASP.NET application hosted at a Windows 2003 server

(IIS6). This works almost all the time (I have uptimes of 100% on most days), but then all of a sudden a few days in a row I have the following phenomenon:
.aspx still get processed, but as soon as any of them try to

read/write to
a
MsAccess database (using DSNLess OleDBConnection) it's timing out.

This happens for a period of about 40 minutes and then all of a sudden
everything starts working again without any user intervention.

Has anyone had the same problems ?

Thanks,

Wim



Nov 18 '05 #4
WL
Yep, not a big success though

I'll just have to try it I guess ...

Thanks,

Wim

"Kevin Spencer" <ks******@takempis.com> wrote in message
news:en**************@tk2msftngp13.phx.gbl...
Can OleDb do connectionpoolin on MsAccess connections ? If so: this might
be
a problem ?
You got me there, WL. I haven't used Access in a web app in years. Have

you tried searching the Knowledge Base?

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"WL" <me@here.nospam> wrote in message
news:e$**************@TK2MSFTNGP09.phx.gbl...
Hi Kevin,

Thanks for your reply: you are absolutely right that a (MS) SQL Server is
a
lot beter.
However, the problem occurs on a server that is not really used by the
public. I have a Alertra (uptime checker) account running every 10
minutes (and that's it).
So concurrent user would not be the problem.

Moreover, when a timeout occurs on one Access databases: all other ASP.NET pages that are even using other MsAccess files are timing out.
It just seems as if there's a problem with the OleDbConnection.

Can OleDb do connectionpoolin on MsAccess connections ? If so: this might be
a problem ?

Thanks,

Wim

"Kevin Spencer" <ks******@takempis.com> wrote in message
news:eD**************@TK2MSFTNGP10.phx.gbl...
Access is not designed for Internet use. It is designed as a desktop/LAN database. However, ANY OLE DB-compliant database can be used in an
ASP.Net application. The upside is cost; an .mdb database is free of licensing

fees.
The downside is performance. You may have too many concurrent users for Access to handle at times. Check your web server logs to see if there is a
correspondence of heavy traffic to these errors.

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Annick Van Hoof" <me@here.nospam> wrote in message
news:Oc**************@TK2MSFTNGP09.phx.gbl...
> Hi,
>
> I'm having my ASP.NET application hosted at a Windows 2003 server

(IIS6).
> This works almost all the time (I have uptimes of 100% on most

days), but
> then all of a sudden a few days in a row I have the following

phenomenon:
>
> .aspx still get processed, but as soon as any of them try to

read/write
to
a
> MsAccess database (using DSNLess OleDBConnection) it's timing out.
>
> This happens for a period of about 40 minutes and then all of a

sudden > everything starts working again without any user intervention.
>
> Has anyone had the same problems ?
>
> Thanks,
>
> Wim
>
>



Nov 18 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Déian | last post: by
3 posts views Thread by Brad Burke | last post: by
15 posts views Thread by (Pete Cresswell) | last post: by
11 posts views Thread by Yelena Varshal via AccessMonster.com | last post: by
reply views Thread by bbrewder | last post: by
reply views Thread by leo001 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.