Odbc-timeout Error On A Linked Table From Access2k
Dec 12, 2006
Hi.
I have the problem that some records in a ms sqlserver table is unable
to update from Access.
I get the error message odbc-time out error in linked table......
I tried to copy this table to another database, where none but me was
aktive.
And then it worked quit ok when I try to save the record.
I am thinking about if there is some trigger och restraint that I
don't know about, but I don't know how to se all of this in the
database.
I have changed the odbc-timeout settings in Access but that doesn't
seed to make any difference
So what's the problem?
Does anyone have an idea?
/regards BigOlle
View 1 Replies
ADVERTISEMENT
Sep 27, 2006
I have access97 front end , with linked tables to sql server 2005. when i change a table ID column (type int) to primary key so it is updatable, then try open the table i get odbc error with no msg, if i alter table again to remove primary key option table opens fine but is not updateable. any ideas would be a great help
View 5 Replies
View Related
Apr 5, 2004
I recently started with a company that uses access for a front end and sql2000 for the back. They have set up an ODBC connection though access2k to reach sql2k. This works fine but fouls up in regards to the record locking. You can set record locking in access but it has no effect. In the office help it says 'data in a form, report, or query from an Open Database Connectivity (ODBC) database is treated as if the No Locks setting were chosen, regardless of the RecordLocks property setting.'
Also, the access lock option info says it 'could' lock the few records around the record you wish to lock.
So my question is this: How can i (without destroying this ODBC link from access2k to sql2k) get locks for individual records to work successfully?
any info would be great, thanks
View 1 Replies
View Related
Feb 18, 2005
Very common error but wired scenario. Every client machine get this error in morning. VB application works fine until evening but when everyone goes home after shut down the machine and they come back again in morning and try to run the application they get this error. Application runs fine, It can access data, pull data, view data but It can not write any data. (Other words can not enter any data).
Application again starts working fine after I copy database on different SQL server. For temporary solution I swap database from one SQL Server to other one day and back to original SQL server next day. Every morning it takes about 2 hours to copy database. I’m doing this from last few days as working solution. FYI, I have 2 different VB application, each has their own database. One working fine and other started giving me problem, the one I described above.
Few thing I want to let you know:
Recently I changed the SQL server. After I changed I started having this problem. But other application working fine. So I don’t think that could be a problem. (Both application basically same in terms of development and tools they use. VB and SQL Server, ODBC connection, Crystal Reports).
In old SQL server both database had daily backup on third party backup built on different server using Client Network Backup. After I changed the SQL server I never modify backup setting. So after I moved SQL server , every night backup was trying to connect to old SQL server and but It couldn’t take the backup cause I changed the machine. Again if that’s the problem both application should not work but one working fine other is giving me problem.
One more thing I want to mention here is I started having this problem when I left the SQL server copying database overnight. Means, I started copying database and I left the machine ON when I came in the morning copying database was done and I just click on the OK and close the window. Basically It has finished copying database in around 2 hours after I started and I close the window when I came back next morning.
That’s the few things I’m thinking about but I don’t know what kind of database setting this might have changed and how to reset again. Any help will appreciated.
Dose any one know how to combine .mdf (Primary data file) and .ndf (secondary data file) ???
View 2 Replies
View Related
Jan 8, 2004
Greetings!
I recently rewrote an old ACCESS 97 application to work with MSSQL 7.
The program works fine until I use a form whiche opens several linked tables at the same time. When closing the Form I get (At unpredictable moments) an ODBC SQL SERVER DRIVER update failure error message.
All rights are set on the tables for Public and even then i keep getting this error at very odd moments. I also had a look in Access at the ODBC refresh rate which is set at 10sec , OLEDB refreshrate 10 sec, and refresh is set at 5sec.
I tried different combinations of timeout settings and even renewing the MDAC to version 2.7.
Nothing helps.
Can anyone give me a tip as to look for the possible source of the error and how to fix it?
Thanks!
Vincent JS
View 2 Replies
View Related
Sep 12, 2001
Receiving error "Microsoft ODBC Server Driver Timeout Expired".
This is happening when running queries or stored procedures through VB6 and also in Enterprise Manager.
Have set query timeout to 0 and command timeout to 0 but no joy.
Enterprise manager cannot even perform a count of records (16Million) without timeing out.
Can anyone help...at end of tether!
Cheers,
Brookesy
View 1 Replies
View Related
Sep 28, 2005
Hi everyone
I have installed SQL server on my server machine. using localsystem and mixmode option.
It is working fine.
I installed sql server with connectivity tools only option on my client computer.
now, When i try to connect to server using data source from control panel --> Administrative tools --> Data source(ODBC).
but I cant connect.It gives me error as below.
Connection Failed:
SQLState:'HYT00'
Sql Server Error:0
[Microsoft][ODBC SQL Server Driver] Timeout Expired.
I uninstalled sql server from my client and server computer. and installed again.
I tried to ping from client computer to server computer it is working.
even i tried telnet sqlservername 1433
this one is also ok.
But same error facing
Please help me out.
Regards,
ASIF
View 1 Replies
View Related
Jul 20, 2005
sql server 2000 8.00.194Microsoft Windows 2000 Service Pack 2I looked into my sqlserver agent log and found the followingODBC Error 0 Timeout expired[SQLSTATE HYT00]logon to server local '( failed)' (Job manager)I have no idea what that means but it did keep out users for a minute or more.The threads found on this forum almost all point to reccuring situationsmine is a sporadic one time issue.Is it Ok to conclude it is a network error as I did?TIAVince
View 1 Replies
View Related
Apr 23, 2002
Hello,
I am researching alternatives to a stored procedure that uses a linked server query that my ASP page uses to retrieve records to the page.
Should I:
Use replication (Data is constantly updated, so a snapshot won't do. Merge replication?)
Break up the stored procedure into subqueries?
Use a view on the remote server instead of the actual tables?
I am trying to reduce the amount of table scans, what is the best way to do this?
Here is the stored procedure I am trying to tune:
(@startDate and @endDate are parameters passed from the web page):
CREATE PROCEDURE dbo.spELRMCcardXtionByDate @dcid nvarchar(255), @startDate datetime, @endDate datetime
AS
SELECT Store.[Str#], Store.[Dcid#], E.card_number, E.program_number
, E.start_date, E.end_date, E.card_number, E.event_number
, E.status, E.budget, E.scheduled_date, P.tx_time, P.purchase_amount
, L.merchant_name
FROM (Store INNER JOIN Event E ON Store.[DemoID#] = E.event_number)
LEFT JOIN (Location L RIGHT JOIN POS_TX P ON L.location_number = P.location_number)
ON E.event_number = P.event_number
WHERE (((Store.[Dcid#])= @dcid)) AND E.scheduled_date BETWEEN @startDate AND @endDate
ORDER BY Store.[Str#]
GO
Any suggestions on my sp or anything else that can implement would be greatly appreciated.
TIA,
Bruce Johnston
Programmer/Analyst
View 1 Replies
View Related
Aug 3, 2007
Hello All,
My application is dependent on two databases one is on sql 2005 machine and other is on sql 2000 machine. A linked server is establish between these two using sql account which has appropriate rights on both server's databases.
application works fine but after some time it crashes and if i see error from sql profiler i get the error
OLE DB provider "SQLNCLI" for linked server "sql2000machine" returned message "Login timeout expired".
Few days back applciation was working absolutly fine, but i was trying to make linked sever through windows account, i dnt know wat has i changed during achiveing that setup that now application (linked server) is not working even with sql account.
please help its urgent.
View 1 Replies
View Related
Feb 7, 2001
Hi!
I'm using SQL Server 7. My views do not return result sets because I get the following message:
ODBC SQL Server Driver Timeout Expired.
How do I write script to change the time out property?
Thanks,
Denise
View 1 Replies
View Related
Jan 12, 2000
Hi Everyone,
I have set up a link from ACCESS to a SQL 7.0 database using ODBC (File DSN saved on a shared DRIVE). The link works well only from the workstation where the link was created. But How can I create a link so a group of users can view the linked table in ACCESS without type a password? Any suggestion is appreciated.
Lunjun
View 2 Replies
View Related
Oct 11, 2006
Hello,
I have a table that is fairly large, and I need to make a change to one of the columns in the table. Namely I need to change the datatype and rename that column. When I try to save the updated table, I keep getting a timeout error that says.
'eligibility (dbo)' table
- Unable to create index 'PK_eligibility'.
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Any ideas on how to make the table change more efficient or change the timeout period. I need to keep the existing data in the table. I am using sql server managment studio(2005) connected to a sql server 2000 database.
Thanks!
View 7 Replies
View Related
Jul 20, 2006
Access 2002SQL Server 2000ODBC Linked TablesI have a user who gets an ODBC timeout message when trying to save a newrecord in a form. I looked at the locks on the server and that user waslocking himself out. On the same server I can enter records fine withthat form, except when he's in there, he's using the same application(copy of).The form he's using is a simple one bound to a query thus:select * from table where 1=2or something very similar so that it's always at a new record anddoesn't look at any others.Any settings I should look at?
View 1 Replies
View Related
Jul 3, 2007
Hi,
I am running a stored procedure that collects some records from two tables do some calculations with those records and insert those calculation result in a temp. table. I am calling this stored procedure in my aspx page and then later select all the records from temp table and show it in a table.
When I run this application on browser it give me Timeout expired error but whn I execute the stored procedure it runs properly but takes around 3:10 mins to execute in query analyzer. I did some google work and based on that I specified CommandTimeout = 300 for SP and Connection timeout=400 in web.config. But still it didnt worked. Sometimes it runs properly but sometimes its not.
Where I am doing mistake? and Wht should i do to resolve this? Plz. help.
Thanks in adv.
Regards,
Yogita
View 1 Replies
View Related
Dec 26, 2007
Guys,
I am trying to attach a database object to the App_Data directory I got thie error
Error: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
This is what I did. I right click the App_Data folder and click Add New Item. Then I click the SQL Database. This is where I got the error.
What should I do? Please help
View 2 Replies
View Related
Aug 16, 2007
One of our clients has reported a problem. Everything was workingfine on Monday, but since Tuesday all is going wrong. The sysadminassures me that there have been no changes to the network, or theservers.Three applications, one back-end database server (SQL Server 2000 withall service packs etc.).APP 1: Access 2000 databaseAPP 2: ASP.NET (VS 2003)APP 3: ASP.NET (VS 2003)All connect to the same database server - different databases, natch.1 & 2 have reported ODBC timeout issues. 3 had other problems. Thisis how they present themselves. I ran SQL Profiler to capture thetraceAPP 1 - ACCESS APPLICATION1. Login works fine. You have to supply credentials which arevalidated by SQL Server. Open a Search form and the default recordsetis displayed correctly.NOTE: This SQL captured on trace.2. Enter a criterion into one of the controls on the search form andpress "Filter". Wait a minute and watch the hourglass. EventuallyODBC Timeout error displayed.NOTE: This SQL captured on trace.3. Right-click on the appropriate column on the sub-form and enterthe same criterion as for step 2 above. NO ODBC TIMEOUT - CORRECTRECORDSET RETURNED WITHIN TWO SECONDSNOTE: This SQL captured on trace.NOTE: If I open the (linked) tables in the Microsoft Access databasepane I can manipulate the data at will. However, if I try to open anystored queries in Access they time out.APP 2 - ASP.NET APPLICATION1. Login works fine. You have to supply credentials which arevalidated by SQL Server. As it happens, the default display for thelogged-on user contains no records.2. Change the parameters to allow some records to be displayed.Watch the progress bar do nothing and then the system displays the"Object reference not set to an instance of an object" exception.NOTE: This SQL captured on trace.APP 3 - ASP.NET APPLICATION1. Login works fine. You have to supply credentials which arevalidated by SQL Server. As it happens, the default display containsno records.2. Attempt to add a new record. System pretty slow.3. New record form displayed. All drop-downs contain incorrect data- for example, in the Supply Priority list, there should be 14 items -there are, in fact, 56 - each item duplicated four times. This hashappened in all the tables that I can see. I've taken a dump of thelive data and compared it with our archived version - for lookuptables, there is no duplication in our copy, but in their copy everyitem appears four times.If the above wasn't weird enough for you, get this.If I cut and paste the SQL that's being captured by the Profiler ateach point and paste it into Query Analyser, it totally barfs. Iwaited 11 minutes for one query but it just kept running, neverreturning. EVEN THE QUERY AT APP 1 POINT 3.Needless to say, if I run these queries back at the office it all goesaccording to plan.I think they've got a problem.....Edward
View 2 Replies
View Related
Oct 25, 2006
Hello !
I get in my SSIS Package a Query Timeout in the Datareader!
I Use the ADO.Net OBC Connection with the Connection String:
Dsn=xxx;uid=xxx;connection timeout=0;command timeout=0;query timeout=0
Is there any Option to set the Query Timeout ?
Thanks !
Pseudo
View 5 Replies
View Related
Nov 10, 2006
Hi,I
get this error from our web application every once in a while. " Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding". I email
myself when an error occurs, and once every 2-3 days I get this timeout
error emails, like 5-10 emails in a span of few minutes. Then it goes
away. I have set the command timeout for 60 secs.
It
doesn't happen from the same stored procedure, actually I have seen it
timeout from really simple 1 or 2 line stored procedures, which shouldn't normally take 1 sec. Its like
sql server just shuts down for few minutes. We have some
backups and maintenance jobs scheduled, but they run only after
midnight. I have checked the
application event viewer, there are no warnings or
error messages for MSSQLSERVER. Can
any one tell me how to check whats going on during that short timespan
when timeout error occurs, and what causes it? I don't want to run sql
profiler continuously for 2-3 days, I am afraid it will slow down the
server more. Thanks.
View 3 Replies
View Related
May 17, 2001
Hi,
I am using SQL Server 7.0 Desktop Edition on Windows NT 4.0 workstation with service pack 6. I'm connecting to my production servers using the Enterprise Manager.A couple of months back, I have installed SQL Server 2000 Evaluation Edition on my desktop and using it to access the production servers.A couple of days back, I was not able to connect to the Query Analyzer either through Enterprise Manager or directly. I am getting the following error:
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver] Timeout expired.
All our production servers are in a data center. I'm able to connect to the production servers in one particular cage but it is giving the above error if I try to connect to other servers which are in different cages. My colleague is able to connect to all the servers through Query Analyzer from his machine which has only SQL Server 7.0.I uninstalled SQL Server 2000 on his suggestion but it is giving the same error. I uninstalled and installed SQL Server 7.0 but I'm still getting the same problem.
Could you please throw some light on why this is happening ?
Thanks in advance,
MN Rao
View 1 Replies
View Related
May 23, 2002
I am trying to populate a View. I can run the sql code successfully by using SQL Query Analyzer. However, When I try to open the View in SQL Enterprise Manager and request that all rows be returned, I receive the following error:
ODBC SQL Server Driver Timeout Expired
I cannot determine the cause, Can anyone help me determine why the message is occurring? Thank you.
View 2 Replies
View Related
Oct 30, 2007
Hi
I'm running a machine with windows xp pro sp2. I have a MS Access 2000 database on that machine. The database contains 1 odbc linked table
and 1 Access query.
The odbc linked table is connected to a MS SQL Server 2000 database with a ODBC SQL Server System DSN.
The table on SQL Server to which the table in Access is linked has about
3 million + rows.
When I open the ODBC linked table in Access, it opens without a problem.
However, if I use even so much as one criterion such as "where company = ABC" for example, then it "thinks" for a while and returns the dreaded:
[Microsoft][ODBC SQL Driver] Timeout Expired (#0).
I have to use MS Access 2000 as the front end for this SQL Database table.
How do I get around the timeout issue. Is there a setting in SQL?
Please keep in mind that
I can't write the queries as Store procs because the requirement of the client is that there be one Linked Access table that the users can use
to write various access queries. No user are not techies.
please help
View 1 Replies
View Related
Jul 20, 2005
Hi,Has anyone ever had trouble using the query analyzer tool through a vpnclient? I'm able to connect outside of work to a sqlserver db on mycompany lan with enterprise mgr, but the query analyzer times out everytime I try to connect from outside of work. Both utilities work fine atwork (no vpn tunnel).The exact error is:Unable to connect to server blahblahblah:ODBC: Msg 0, Level 16, State 1[Microsoft][ODBC SQL Server Driver] Timeout expiredI've tried increasing the sqlserver odbc driver's CPTimeout without success.Appreciate any advice.Eric
View 2 Replies
View Related
Feb 5, 2008
Hi ,
Well i have one question regarding the Timeout . I have an SQL SERVER 2005 database and have an VB6.0 application. I have a stored procedure which inserts more than 90,000 rows from one table to another . Some times i get an exception as [Microsoft] [ODBC SQL Driver] Timeout Expired in the Visual Basic application and some times it works fine. The exception i receive within 30 seconds , but when i try the same stored procedure in query analyser , it works fine. also i have increased the timeout in visual basic , but still i get the same error.
Can anyone suggest.....
View 6 Replies
View Related
Jun 29, 2002
Hello,
When I connecting thru T-SQL, the following error was thrown.
Unable to connect to server 'SERVERNAME'
ODBC: Msg 0,Level 16, State 1
[Microsoft][ODBC SQL Server Driver] Timeout expired.
How to fix this?
regrads,
vnk.
View 2 Replies
View Related
Aug 19, 1999
I am running a query which pulls back about 200,000 records.
When I run this in ISQL (SQL Server 6.5), it runs in almost 2 minutes.
When I put it in a store procedure and run it off my ASP application, I
get this error
[Microsoft][ODBC SQL Server Driver]Timeout Expired
We've tried many things including:
1) Increased connection and command time outs in Global ASA
2) Have the ODBC driver log long Quires to a file
3) Changed Query Time out in Enterprise Manager(360 seconds) Go to
tools --> Preferences/configure -->Connection Tab
4) Changed Maximum allowed open database from 20 to 200
5) Changed resource timeout to 360 seconds from 5 seconds
6) Changed remote query timeout to 0, allowing infinite wait.
What else can we try???
Thanks for taking the time to read this
Joyce
View 2 Replies
View Related
Feb 1, 1999
Hi all,
I inherited some really twisted asp pages from another developer that crank for a long time. They used to work, albeit slowly. Now when I try to run one I get the error:
Microsoft OLE DB Provider for ODBC Drivers error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
Short queries run fine.
IIS4 & SQL Server are on the same box. I didn't the ASP pages or the IIS or SQL server config. I did install VStudio 6.0 a while back.
Anybody got any clues?
View 1 Replies
View Related
May 29, 2002
Thank you to all who reply to this perplexing question.
Mike
Database VMFGSRVRVMFG is SQL 2000 Std.
Database NT002P_GL is SQL 7.0.
All SQL versions are at the current SP levels.
I receive the timeout message when I am in EM,
database,VMFG(database), Views, Open View, Return All
Rows. I can successfully run the code in QA. I believe I
am running up against a time parameter in SQL Server. I
have reviewed all time parameters that I can find.
However, I still receive the error. What parameters should
I be looking at? I am attempting to create a view with the
following code:
--------------
CREATE view uv_olap_adj_co_profit as
select customer.id as customer_number,
customer.name as customer_name,
customer_order.salesrep_id as salesperson,
isnull(customer.country, 'USA') as country,
'7' as business_unit,
customer_order.order_type as order_type,
uv_olap_co_profit.customer_order,
uv_olap_co_profit.work_order,
uv_olap_co_profit.close_date,
uv_olap_co_profit.period_year,
uv_olap_co_profit.gl_period,
isnull((uv_olap_co_profit.billing + ut_man_adj.billing)
*ut_fin_adj.billing,
uv_olap_co_profit.billing*ut_fin_adj.billing) as billing,
isnull((uv_olap_co_profit.material_cost +
ut_man_adj.material)*ut_fin_adj.material,
uv_olap_co_profit.material_cost*ut_fin_adj.materia l) as
material,
isnull((uv_olap_co_profit.labor_cost + ut_man_adj.labor)
*ut_fin_adj.labor,
uv_olap_co_profit.labor_cost*ut_fin_adj.labor) as labor,
isnull((uv_olap_co_profit.burden_cost + ut_man_adj.burden)
*ut_fin_adj.burden,
uv_olap_co_profit.burden_cost*ut_fin_adj.burden) as
burden,
uv_olap_co_profit.service_cost as service
from uv_olap_co_profit,
ut_man_adj,
ut_fin_adj,
customer_order,
customer
where uv_olap_co_profit.customer_order *=
ut_man_adj.cust_order_id and
uv_olap_co_profit.work_order *= ut_man_adj.work_order and
uv_olap_co_profit.period_year = ut_fin_adj.year and
uv_olap_co_profit.customer_order = customer_order.id and
customer_order.customer_id = customer.id and
(customer_order.salesrep_id = 'LABELAIREP' or
customer_order.salesrep_id = 'OMOHUNDR' or
customer_order.salesrep_id = 'EGGERSR')
union all
select customer.id as customer_number,
customer.name as customer_name,
customer_order.salesrep_id as salesperson,
isnull(customer.country, 'USA') as country,
customer.user_2 as business_unit,
customer_order.order_type as order_type,
uv_olap_co_profit.customer_order,
uv_olap_co_profit.work_order,
uv_olap_co_profit.close_date,
uv_olap_co_profit.period_year,
uv_olap_co_profit.gl_period,
isnull((uv_olap_co_profit.billing + ut_man_adj.billing)
*ut_fin_adj.billing,
uv_olap_co_profit.billing*ut_fin_adj.billing) as billing,
isnull((uv_olap_co_profit.material_cost +
ut_man_adj.material)*ut_fin_adj.material,
uv_olap_co_profit.material_cost*ut_fin_adj.materia l) as
material,
isnull((uv_olap_co_profit.labor_cost + ut_man_adj.labor)
*ut_fin_adj.labor,
uv_olap_co_profit.labor_cost*ut_fin_adj.labor) as labor,
isnull((uv_olap_co_profit.burden_cost + ut_man_adj.burden)
*ut_fin_adj.burden,
uv_olap_co_profit.burden_cost*ut_fin_adj.burden) as
burden,
uv_olap_co_profit.service_cost as service
from uv_olap_co_profit,
ut_man_adj,
ut_fin_adj,
customer_order,
where uv_olap_co_profit.customer_order *=
ut_man_adj.cust_order_id and
uv_olap_co_profit.work_order *= ut_man_adj.work_order and
uv_olap_co_profit.period_year = ut_fin_adj.year and
uv_olap_co_profit.customer_order = customer_order.id and
customer_order.customer_id
View 1 Replies
View Related
Apr 9, 2001
Hi!,
I am running sqlserver 2000 enterprise edition on windows 2000.
When I try to run a select statement. I am encountering
[microsoft][odbc sql server driver] timeout expired
How do fix this problem?
Thanks,
Ranjan
View 1 Replies
View Related
Oct 30, 2007
I've tried every websearch possible to try and get a solution for this problem but can't.
Development Software:
SQL Server 2000
Enterprise Manager 8.0
Query Analyzer 8.00.194
Error:
When I run a mildly complex view in Enterprise Manager I get the error:[Microsoft][ODBC SQL Server Driver]Timeout Expired
after about 30 seconds.
When I copy and paste and run the exact same code in Query Analyzer the Query runs for longer than 30 seconds and runs until completion. Now my question is since this apparently seems to be an Enterpise Manager problem and not on the server end, where do I go in Enterprise Manager to change that setting? I've looked everywhere in Enterpise manager and can't find a "command timeout" setting.
Thanks!
View 4 Replies
View Related
May 18, 2004
Hello,
I installed MS SQL Server 2000 Evaluation Edition on
Windows XP Pro. I have database on the same PC. When I
am running a query(view) from Query Analyser I
get "[Microsoft][ODBC SQL Server Driver] Timeout Expired"
error message . When I am running the same view on
smaller amount of data it works.
:confused:
Could you please help me with that?
Thanks
DJ
View 3 Replies
View Related
Mar 6, 2008
Hi,
I have tried updating the DSN configure option i.e. 30000 milliseconds.
But I am still facing the problem of Timeout Expired.
I am using sql server 2005 for daily importing data from Excel Dump Files into sql server table.
Everyday the database gets updated.
The Error mentioned in Subject normally gets once a month, due to daily updation of database whether each table structure gets changed like index, trigger, etc.
Kindly let me know how to resolve this error.
Regards,
Srinivas Alwala
View 1 Replies
View Related
Oct 18, 2006
Hi, on a web application that I develop, I just upgraded to a new database server running SQL Server 2005 and Windows Server 2003 Enterprise Edition. The previous database server ran SQL Server 2000 and Windows Server 2003 Standard Edition. Since this upgrade, the application has been causing "timeout" errors all over the application. I've been stumped. Here's the error mssage:
Microsoft OLE DB Provider for ODBC Drivers error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
I'm hoping there is some sort of a setting that can be modified to increase the maximum number of connections between the web server and database server. This is a fresh version of Windows Server 2003 and SQL Server 2005. Any support that can be provided will be greatly appreciated.
View 3 Replies
View Related
