Well, I broke down and opened a ticket with support yesterday on this. This morning I had gotten back and guess what they wanted, log files... So I got them some log files (which said the same thing I had been saying).
I tried a workaround: Create a view on my local AR System database that pointed to the remote database. I opened up Query Analyzer, queried the new view, and it worked (of course), however remedy still failed to work. I have seen a few other ppl post after DTS change that they were having problems with linked DBs in either MS SQL <> MS SQL or in MS SQL <> Oracle. I fail to see what DTS would have to do with this, but it does seem to be a strange coincidence. I also set up my dev server to a dev database, both running MS SQL Server 2k, and they are experiencing the same error as well. The exact error in the arerror.log is: Wed Mar 14 07:31:48 2007 Dispatch : Timeout during data retrieval due to busy server -- retry the operation (Remedy-Dev) ARERR - 93 This is the only error being listed in the log. In my arsql.log, I can see the query: <SQL > <TID: 002796> <RPC ID: 0000001668> <Queue: Admin > <Client-RPC: 390620 > <USER: <user> > /* Wed Mar 14 2007 07:26:55.5430 */SELECT * FROM <server>.<db>.dbo.<view> WHERE <column>='014562354' So, I know that remedy is passing the correct query. Just it seems like the remote server isn't receiving it, as in the network and sql traces, they can only see my incoming connection and never see a query come across. I'm suspect to leaning towards a change that was performed on the server the night before this issue began occurring (the same night as DST Change) that affected RPC port traffic and temporarily disabled FTP traffic. The FTP logs were generating the error: Rename Temp File calloc:File exists Microsoft says that the temp file that is created during the download process is deleted. The KB article is located at http://support.microsoft.com/kb/899679. There is a workaround for this issue. WORKAROUND To work around this problem, use the FTP LCD command in the FTP session to change the working directory to the destination directory before you run the GET command. For example, to successfully download the file by using FTP, follow these steps: 1. At a command prompt, type ftp URL, and then press ENTER. URL is the URL of your FTP site. 2. Type lcd d:\, and then press ENTER. D:\ is the destination directory where you want to copy the file. 3. Type get FileName, and then press ENTER. FileName is the name of the file that you want to download from the FTP site. So, I'm leaning towards whatever caused this FTP issue after the changes on the box have caused my DB Link errors, but I'm having a hard time getting anything concrete to prove that. Does anyone have any ideas or has anyone experienced this before? Thanks, Gary ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza Sent: Tuesday, March 13, 2007 8:38 AM To: [email protected] Subject: Re: MS SQL Linked Server error Gary, On your remote database, are there sufficient number of user connections available to connect to? If not this 'might' be the reason it is timing out? Joe ----- Original Message ---- From: "Opela, Gary L Contr OC-ALC/ITMA" <[EMAIL PROTECTED]> To: [email protected] Sent: Monday, March 12, 2007 4:10:50 PM Subject: Re: MS SQL Linked Server error ** **Bump** Additional Information: My MS SQL DBA says he can see my connection, but is not seeing any query being passed. In addition to this, if I log into SQL Query Analyzer (as the same user that remedy uses) to run the query , he can see the query being sent, and of course, it does work. ________________________________ From: Opela, Gary L Contr OC-ALC/ITMA Sent: Monday, March 12, 2007 10:25 AM To: ' [email protected] ' Subject: MS SQL Linked Server error MS SQL 2k Windows Server 2k Remedy 6.3 unpatched Microsoft XP Workstation Here is the scenario. I've set up a link between my database and another database using. In remedy, whenever I hit <enter> on a field, then remedy sends a query to that linked database based on the values in that field. This morning remedy began just hanging for several minutes after hitting <enter> and then it returns a server busy error. I have rebooted the server and this does not seem to help. I've re-entered the userid and password values from the Security -> Linked Servers -> <servername> -> Properties -> Security tab and still no luck. I can use that same userid, however, to log directly into the linked server and execute a query. I can also log directly into my primary database and execute a query that is referencing the linked server. I've checked with my DBA and he can see my database connection coming in successfully. It's just like for some reason the data cannot be returned. Any ideas why everything BUT remedy works? Thanks, Gary ________________________________ TV dinner still cooling? Check out "Tonight's Picks" <http://us.rd.yahoo.com/evt=49979/*http:/tv.yahoo.com/> on Yahoo! TV. __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
