I get the message Microsoft [ODBC Sql server driver]communication link failure error message in my VB 6 application with MSDE engine. This error does not happen often.
My connection string is as below.
"Provider=MSDASQL;Driver={SQL Server};Server=" & mSvrName & ";DATABASE=cnsClient;uid=uid;pwd=pwd"
Please help.
All,
I need a help from you all. I am getting this error if the users are running the application which is connecting from MSAccess97 to SQL Server 2000.
Error: [Microsoft][ODBC SQL Server Driver]Communication link failure
I would appreciate if you send me the resolution for this problem.
Thanks,
Reddy
Several of our customers are getting a message intermitantly throughout the day where the connection is closed. The message being generated is [Microsoft][ODBC SQL Server Driver]Communication Link Failure.
These messages started in the last two weeks.
Thanks for any direction that can be thrown my way.
David
Okay-- if anyone can solve this they are truly the SQL genius! We are getting this error when we run a VB program that we use to access an SQL database on a server across our network on a workstation. In fact we get this same error when we even run the program on the server where the SQL database is running or on any of our workstations. Here is the error message:
08501:[Micorsoft][odbc sql server driver] communications link failure
Now the odd thing is that many other functions in the workstation application work fine and retrieve data from SQL but certain data requests by the workstation application fail with the above error message and we get this message consistently. Even though it appears that different workstations running the identical Vb application will get this error consistently but in different locations when running the application. We were running SQL 6.5 on an old server, with the workstation application for literally years without any problems. We also decided to upgrade to a new server, installed server 2000 operating system and the latest version of SQl -- moved all the databases pointed the workstations odbc at this new server and get exactly the same error in the same location in the workstation applications. The programmer that wrote the application and designed the database in SQL can't find the problem and a number of other computer "experts" also could not find the error. We did add a new linksys DSL router/firewall but everything kept working after this installation for several weeks so I don't know if this is the problem on the network. THe programmer also noted that he had problems using terminal services on our network to connect to his office computer and decided that there must be some network issues that are causing the ODBC communicaitions to fail and also terminal services to fail-- or of course they may be unrelated. Has anyone ever seen this ODBC communication error in their travels through SQL implementations? Any help will be greatly appreciated. If we can't fix this we will have to abandon a software application that has been used for over five years and just too complex to rewrite.
Jeff Kilpatrick
Hi Guys,
I am using C++ (Ver 6) that connects to a SQL Server 7 DB using ODBC drivers. The apps connects to the database in the start and listens to the users requests and replies with the required data.
The apps is working fine, but once in a while it looses connection and gives "Communication link failure" message.
I just restart the apps and it is able to reconnect and perform as normal without any problems.
I am not able to find the reason as this behaviour as its very much unpredictable!
The error is returned by SQLExecDirect() function.
The question is, since I still have the Connection Handle, is it possible to just reconnect to the database re-using the same handle ? or do I have any other choices ?
Thanks in advance.
Faisal.
Hi Everybody,
On localhost this application works fine but when I put on remote server. I am getting following errors. For both localhost and server, I am using same remote sql 2000. I will appreciate any help.
Thanks,
Arif
Server Error in '/' Application.
--------------------------------------------------------------------------------
ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.Data.Odbc.OdbcException: ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'.
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.
Stack Trace:
[OdbcException: ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'.]
Microsoft.Data.Odbc.OdbcConnection.HandleError(IntPtr hHandle, SQL_HANDLE hType, RETCODE retcode) +27
Microsoft.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method) +838
Microsoft.Data.Odbc.OdbcCommand.ExecuteNonQuery() +80
Calgary.venues.Page_Load(Object sender, EventArgs e) in c:inetpubwwwrootCalgarySitevenuesvenues.aspx.vb:32
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +731
we have our cubes in Server A and SQL DB resides on Server B (we are on SQL 2014), from last couple of days are cube started failing due to below error:
OLE DB or ODBC error: Protocol error in TDS stream; HY000; Protocol error in TDS stream; HY000; Protocol error in TDS stream; HY000; Communication link failure; 08S01; TCP Provider: An existing connection was forcibly closed by the remote host.
; 08S01
I have been going through some blogs to understand the error but don't find any specific yet.
We are developing an ASP ad component for our web site. For the past one week
we are testing the component in real environment. All of a sudden we are getting the following error message.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Communication link failure
We are using SQL Server 7.0 with Windows NT4 SP4, IIS and ASP
We are not using any complex joins or view updation. We are using ADODB connection variable with an application scope to establish the connection. When we try to use the connection object to open a Recordset, this error occured. We colsed the connection and destroyed the ApplicationScope Connection object and re-created the object with out any success.
I get ODBC Error 823 when I try to access data from Crystal reports and I/O error, communication link failure...from query analyzer. But the weird thing is it is on and off. If I keep keep clicking 4 times in a row it happens 5 time or 7th time. It is alo only on one of the big tables. They are all stored on same primary filegroup?
Any ideas on what this might be? When I checked BOL it said disk error. The network team doesn't seem to agree. How can I make sure it is hardware or software problem?
Please help.
B.T.W we have SQL 2000 Enterprise.
Hello,We are the authors of an application written in PowerBuilder (typeClient-Server, database MSSQLServer2000).After some time (1 hour) of client inactivity happens disconnect from serverand aplication reports error 'Communication link failure ...'Please, would you help me, if exists some way how to set up an interval ofthe connectivity between Client and Server. I wasn´t able to find it out inany help or manual.Thank you very much in advance!Pavel
View 1 Replies View Related
I am running an SSIS packsge across 2 servers. There at 33 Mil rows being copied over. At 5.6 mil rows I get this
[OLE DB Source [1]] Error: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Protocol error in TDS stream". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: The specified network name is no longer available. ".
[DTS.Pipeline] Error: The PrimeOutput method on component "OLE DB Source" (1) returned error code 0xC0202009. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.
Is there any known cause of this?
Thanks
Hai,
Iam using VC++ application to connect remote database(MSSQL) through network.
Everything works fine, if the network connection is active. If the network breaks and resumes, the application throws "Communication Link Failure" and do not get connected even after the network is resumed.
Client :
* Windows 2000 Professional
* MDAC 2.5
* VC++, using framework- CRecordset to access database
* PEER to PEER network configuration
* DSN through ODBC
Server :
* Windows 2000 Professional
* MDAC 2.8
* MSSQL Server
how to resume the database connection ??
Any one help me????
Thanks in advance,
Hi Y'all,
When i alter 1 single value in my sql server 2000 sometimes i get following error:
1) [MICROSOFT][ODBC SQL SERVER DRIVER] Communication link failure
After clicking away:
2)CANNOT START MORE TRANSACTION ON THIS SESSION
Maybe someone can help me out on this?
Thanks!
We replicate from London to New York and Hong Kong. The New York replication is working fine but everytime we try the Hong Kong replication it starts doing it but when it gets to the bulk copying stage it'll still keep going but on a random table will suddenly fail with a communication link failure message ?? It used to do this and because it keeps trying it used to eventually succeed but recently it never succeeds ?? It keeps trying but we end up having to stop it as it just doesn't succeed anymore ?? Our link to Hong Kong appears fine, we can ping and PC Duo into their servers.
Any ideas would be greatly appreciated as we can't think what it may be ??
thanks
Paul
Hi,with SQL 2000 and Windows 2000, we're getting lots of this error message"Communication link failure" from our C++ application.Any idea why?Thanks,
View 2 Replies View RelatedHi,
I am using ADO in my application to connect and retrieve data from Microsoft SQL Server 2000 SP4. When I start my application, it establishes connection to the server successfully and I am able to retrieve data from the server. here is my test scenario:
1. unplug the network cable from the client machine and put the cable back in after some time. I disconnect from the database in my code when the client machine disconnects from the network
2. Once the client machine comes back on the network, I try to reconnect and retrieve data from the sql server but I get the following error message when I try to execute a sql command:
[Microsoft][ODBC SQL Server Driver]Communication Link failure
This problem occurs only with Window XP SP2. With XP SP1 it works fine. It seems to be problem on the client side as with Windows XP SP1 I do not get this error message at all.
Here are the various details:
1. The firewall is off on the client workstation.
2. the connection string is:
driver={SQL Server};server=AA;uid=BB;pwd=CC;database=DD
where AA = DNS name of server machine where sql server is running.
BB = user name
CC = password
DD= database name
3. The client is remote to the server.
4. I can ping the server machine when the client machine reconnects to the network.
5. I can still telnet the server when the client machine reconnects to the network.
6. client database provider is MDAC odbc.
7. the client and server machines are in the same domain.
8. Shared memory and TCPIP protocols are enabled and TCP is at the top of the list.
9. No alias is being used.
10. Viris scan is not installed.
11. force encriptioned is NOT checked.
Please reply.
Problem: We have intermittent failures of SQL Server jobs with the following error -
TCP Provider: The specified network name is no longer available. [SQLSTATE 08S01]
Communication link failure [SQLSTATE 08S01]
Types of job steps failing: DBCC Checkdb, LiteSpeed backups, re-indexing sql in stored procs, home-grown database update stored procs. These types of job steps are failing on 3 different servers in a 4-way active cluster although all 4 servers have the same type of job steps. No steps involved attempt cross-server processes, job only uses its own server and SAN.
Environment: 4-way active IA64bit cluster Windows 2003 datacenter running SQL2005 RTM. All 4 nodes attached to EMC Clarion SAN.
What we have already looked at: No additonal messages in event viewers. SQL Agent additional logging shows same error. Network services has monitored and sees nothing. Network services is current on firmware upgrades (just applied last batch 2 weeks ago) and still got 2 more errors after the upgrades. I've seen other postings (with no solutions) where people have same error with SQL2000 through SQL2005 SP2, so i don't believe SP2 will help this.
Hi Folks,
This is regarding the intermittent failure of communication between the application server and database server in one of our customer environment. Application error as well as SQL error log shows "General Network Error","Communication Link Failure". Please find below the server configuration
Application Server OS: Win 2003 server + Service Pack1, Standard Edition
Database Server OS: Win 2003 server + Service Pack1, MS SQL Server 2000 + SP4
We have checked the Client/Server Network utility associated with SQL Server and found TCP/IP protocol is used in communication neither than Named Pipes. DSN is used. We have also followed and implemented as per one KB article which mentioned Win 2003 server's feature of preventing Denial of Service attacks (Chance may be there to prevent the valid login packets).We made the registry changes and disabled this feature. A scheduled job which updates the database happens every morning. Also backup was done using a backup utility which needs the exclusive access to DB. So we have asked the customer to use enterprise manager for back up the DB instead of using the other utility to backup. If any one have experienced the same issue, please let me know.
Thanks,
Pranav.
Hi ALL
I am facing a strange problem using ADO to connect Sql Server that I can not resolve it.
My program connected to SqlServer when it started, the state of the connectionPtr was adoStateOpen.Then I disable the network card and enable it immeditately, the errors happened when I executed the sql query probably because of connectionPtr was invalid,but the state of connectionPtr was always adoStateOpen.
1)Msg: Unspecified error Source: Microsoft OLE DB Provider for ODBC Drivers Description: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (send()).
2)Msg: Unspecified error Source: Microsoft OLE DB Provider for ODBC Drivers Description: [Microsoft][ODBC SQL Server Driver]Communication link failure.
Should I reconnect to SqlServer?How can I catch this error when the connection is valid except other errors?
Sorry,my english is poor and thanks for your response.
Thanks a lot.
Env:
1)OS : Windows 2000 Server
2)SqlServer:Sql Server 2000
Hi,
I have an SSIS package which runs subsequent packages in a batch. When I run the main package through command line or a SQL job and connect to a data warehouse that is on the same machine, it runs without a problem. When I try and connect to a warehouse on a remote machine (ideal configuration), it fails with this error:
Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ".
This seems to happen on random subpackages and isn't always consistent.
My Master.dts.Config file has this connection info:
<Configuration ConfiguredType="Property" Path="Package.Connections[Batch].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=RemoteServerName;Initial Catalog=DataWarehouse;Provider=SQLNCLI.1;Integrated Security=SSPI;</ConfiguredValue>
</Configuration>
Both machines have 64-bit operating system and 64-bit SQL software.
Any help would be great.
Thanks.
Hello
TestMachine1 runs SQL2005 SP2 and has as linked server myRemoteServer (SQL2000) server. I run an stored procedure in TestMachine1 which inserts about 20,000 rows to a table in myRemoteServer and brings back a similar quantity of rows. This stored procedures take about 1.5min to complete, but no error appears.
When running the same stored procedure in TestMachine2 (also SQL2005SP2), the following error appears after about 1 minute of execution (not the exact text):
SQLNCli. TCP Provider: network name is no longer available - communication link failure.
Please note that this stored procedure worked before on TestMachine2 (but with less than 10,000 rows) and that connectivity is proven among TestMachine1 and myRemoteServer, since I can execute "select * from synonym_MyRemoteTable" with no problems at all in the TestMachine2's Management Studio.
TestMachine1 and TestMachine2 have Windows XP Professional SP2; myRemoteServer has Windows 2003 and SQL Server 2000 SP4.
Can you please help me to avoid this error?
Hi all,
I am wondering if you guys have any experience with failing Stored Procedures running inside a SSIS package with the following error:
=====================================================
Message
Executed as user: GAALPSVR034FSYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:51:22 AM Error: 2008-05-19 09:06:55.15 Code: 0x00000000 Source: usp_SLIM_Site_PreProcess Description: TCP Provider: The specified network name is no longer available. End Error Error: 2008-05-19 09:06:55.18 Code: 0xC002F210 Source: usp_SLIM_Site_PreProcess Execute SQL Task Description: Executing the query "Exec usp_SLIM_Site_PreProcess" failed with the following error: "Communication link failure". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 8:51:22 AM Finished: 9:06:55 AM Elapsed: 932.203 seconds. The package execution failed. The step failed.
======================================================
Sometime it fails when gets called through a job and sometimes even when a package is open in a design mode. The actual Stored Procedure NEVER fails if called in SQL Server Management Studio.
Any ideas or suggestions will be very helpful and appreciated
Thanks for your help!
Jacob
Below the Error Log Reported in SQL Agent (64 bit SQLServer 2008R2 Enterprise Edition Service pack 2 ,32Core CPU Numa Node and 64GB Ram
Â
[298] SQLServer Error: 10054, TCP Provider: An existing connection was forcibly closed by the remote host. [SQLSTATE 08S01]
[298] SQLServer Error: 10054, Communication link failure [SQLSTATE 08S01]
[165] ODBC Error: 0, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections.
For more information see SQL Server Books Online. [SQLSTATE 08001]
[382] Logon to server '(local)' failed (ConnUpdateStartExecutionDate)
When running the etl I'm getting the error: <SSIS Task>: Shared Memory Provider: Timeout error [258] ; followed by the message "Communication link failure".
What is special about this message that it happens on a SQL Execute task (random task) and the Timeout is after 2 minutes.
When executing the packages separatly it is working fine. The SQL Tasks that are failing are also quit heavy, but reasonable and takes between >2min and 10 - 15 min. Statements are stored procedures that puts an index on 3 mil. records or update statements,...
I had a look to all my (SSIS-etl)Â timeouts and they have the default value 0, the "remote query timeout" of the server is set to 10 minutes. According to me, these are the only one that exists?
There are 2instances on the server each instance has 24GB allocated, the server has 64 in total. Also when the etl runs (that results in an error) no other etl is running on the 2 instances. I'm working with the oledb sql server native client11.0 provider : SQLNCLI11.1.
I am looking for solution for "Communication link failure" Â since many months in google but no luck, am running an SSIS package to load data. job failing many times with error 'Communication link failure', searched every where but found nothing.
Below is the complete error description when job failed.
OS - Windows server 2008 R2 Enterprise Edition
RAM - 198GB
 SQL server 2008 R2 Enterprise Edition and error description is below,
Started: Â 6:22:40 AM Â Error: 2015-08-19 18:50:32.70 Â Â Code: 0xC0202009 Â Â Â
Source: Data Flow Task Lookup [193] Â Â Â
Description: SSIS Error Code DTS_E_OLEDBERROR. Â An OLE DB error has occurred.Â
Error code: 0x80004005. Â An OLE DB record is available. Â
[Code] ....
trying to install sql server2005 on a windows 2003 server box.
getting msg below at the sql server . i looked at other posts on trying to uninstall SQL Native Access Client and norton antivirus. i could never find the snac on the add - remove programs and this server does not have a virus protection program yet.
here's the history of the installs on the server:
wanted to test a 2005 upgrade so:
1) installed sql server 2000 then sp4 then restored some databases to it - all OK
2) tried to upgrade to sql 2005 but ran into problems and left it at that.
had a disk drive crash on the d drive so lost the installs but not the operating system
when the drive was replaced, left alone for a while
then wanted to test a straight 2005 install
1) removed the broken 2005 attempt
2) removed the 2000
3) installed 2005 and got the error on the subject line:
TITLE: Microsoft SQL Server 2005 Setup
------------------------------
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
i've gone through as many of the forums that i can and have tried several things - like uninstalling 2005 and installing pieces and parts but but nothing seems to work.
Thanks!
Dan <><
Hi, I am getting this message, anyone knows what could be the reason for this. My connection to the sql server is out too.
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
Thanks
Ali
Hi everyone,
I am getting the below error when I try to access the table in 2005 database through 3rd party application from the application server.
“[Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt�
This database was restored from sqlserver 2000, so the ODBC connection in the application server first was pointing to 2000 database and now its dropped and recreated to point to the 2005 database.
I dont get this error message when I do the same action from my pc.
I google'd on this error message, and I am not sure if the driver has to be upgraded or if there is anything else that I am missing here.
Thanks much.
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.
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
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?
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
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