Linked Server to Unisys problem Help!!

Question

Linked Server to Unisys problem Help!!

Robert Vallee

Right there with Babe

Points: 786
More actions
December 9, 2002 at 10:56 am

#159304

Here we go,
I have 20+ linked servers, that work, to a Unisys Mainframe(ClearPath). I have 1 linked servers same config as all the others, that returns this error message about 8 out of 10 times I try to use it. The other 2 times the linked server works. I am pulling what hair I have left out. Can anyone help? I have found alot of info about error 7399, but none addresses a Unisys mainframe. I'm using a login account that works with all the other linked servers. I have also verified with the Unisys DBA that the login account is valid.
--Error message
Server: Msg 7399, Level 16, State 1, Line 3
OLE DB provider 'Unisys.DMSII' reported an error.
[OLE/DB provider returned message: [] [[UDP]: [2079] Internal failure: -- EXCEPTION -- in IDBInitialize::Initialize]

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

don1941 SSCarpal Tunnel Points: 4183 More actions · Answer 1

I would verify that the connection properties on your troublesome server are set the same as all the rest. In particular, i would look at the timeout parameter and make sure it's not failing because of network delays.

Robert Vallee Right there with Babe Points: 786 More actions · Answer 2

don1941,

Thanks for the quick reply. I have validated all params are the same. Timeout is set to indefinte(0) I'm on SQL2k/sp2.

Any other idea's?

I'm going to talk to our network guys to make sure we aren't having any network issues.

Rob

Antares686 SSC Guru Points: 125444 More actions · Answer 3

Is there a limit to the number of connections that can be made by a single account or from a single location with Unisys? Also, could be a limitation within the driver itself in spawning new copies. Also, check out http://support.microsoft.com/default.aspx?scid=kb;en-us;237977

Robert Vallee Right there with Babe Points: 786 More actions · Answer 4

The number of connections does not seem to be an issue. Though I have 20+ linked servers, I only have 2-3 concurrent connections at any given time to all linked servers.

Now I'm getting connection time out errors instead of the original error message stated earlier. If I reboot my SQL Server it seems to help about 40% of the time. If we restart the OLEDB on the Mainframe it works about 50% of the time. As of now I have 80% of my Linked Servers working. This is one strange problem. It just started after all linked servers where working properly for a year. We can find nothing that has changed in the year. I have talked to networking and there is no network issues and traces where done. I have tried remote/local timeouts from 0 to 6mins. If the timeout happens it’s usually after only 30 secs no matter what I have the timeouts set at.

Rob