[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1596
  • Last Modified:

Why connection fails via Sybase ASE OLE DB using Sybase Configuration Manager for test connects

The original sybase client version is 12.5.0.3.  Connection was working fine until  there was a request to install client version 12.5.2.  To try to correct, deinstalled 12.5.2, still not working...reinstalled 12.5.0.3, still not working.  Connection via  isql is working fine despite the reinstallation.  Trace although enabled, was not generating a trace file during the connection process.  Event Viewer Logs do not register any clues as well.  What could be done to trace what's going on? Thanks.
0
villavej
Asked:
villavej
  • 4
  • 3
1 Solution
 
grant300Commented:
ISQL works because it does not use any of the Windows stack-o-stuff required to make OLE DB work.  The actual Sybase client software is fine.

Troubleshooting the 12.5.2 connection problem probably would have been easier than this.  By doing the multiphasic install/uninstall/reinstall dance, you probably have a hodge-podge of mismatched DLLs and Registry entries.  Also, the Sybase client stuff generally only wants one version installed on Windows or it gets confused.

First, find a virgin machine that does/has not have any version of the Sybase client installed.  The install the 12.5.2 client and see if you still have a connection issue.  You may have to modify the connection arguments at the OLE level to get it to work.  Look for the release notes for clues as I know there were significant new features in Sybase ASE 12.5.1+ that were not present in 12.5.03.  (BTW, I had a client trying to run 12.5.0.3 on Linux and they did not have good lock; I got them to move to 12.5.1 at least.)  If 12.5.2 does not work right away and you CANNOT fix your application code, you are stuck with 12.5.0.3

Whichever way you to, uninstall everything Sybase Client.  Then go in and remove all references to Sybase from the Registry.  Make sure any DLLs that were copies to the Windows System area have been removed as well.  Depending on which way you go, now do a clean install of that version of the Sybase client.

Best of luck,
Bill
0
 
villavejAuthor Commented:
Thanks, Bill.   The solution was partly correct.  We cleaned up all sybase installations including registries/dlls related to sybase...rebooted the machine...reinstalled 12.5.2 client...then restarted the web services (ISS).   We also refreshed the OLEDB path with the back-up copy of ids files. However,
all the ids files are still experiencing "connection failed due to timeout"  so we recreated or created new ids files and they are connecting until the third connection.  The ids files' configurations are the same.  What could be the problem this time?
0
 
grant300Commented:
I know there were changes between the CLSIDs in 12.0 and 12.5 and at least 1 EBF for 12.5.1

There was also a change in the way IDS files were pulled out of the list but I want to say that all that got fixed prior to 12.5.2

I think what you should try is recreating the IDS files from scratch for 12.5.2 as I am pretty sure the 12.5.0.x ones are different.

The other thing you can do is use a UDL instead which will utilize entries from the interfaces (sql.ini) file if you set it up in with Extended Properties.

I hope this works for you cause I am quickly motoring way out of my area of expertise 8-)

Regards,
Bill
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
villavejAuthor Commented:
Hi Bill,

I can access the server now.  Maybe you can walk me through.  The first data source created was successful and connection was successful too.  After creating another one,  the connection is no longer successful even the first one created.    I noticed that teh CLSid is the same for all the data sources.  Should this be the case?  By the way, when do you usually online so you walk me though the server like searching the installs, registries and so on?
0
 
grant300Commented:
villavei,

I will do what I can but, to be perfectly honest, I got you this far mostly by instinct and sense of smell 8-)  At this point, I am really out of my depth.

Can you cross post this to a Microsoft group?  There are a lot more people there doing OLE DB than there are on in the Sybase group and it seems that the remaining problems are more on that side than the Sybase side.

Anybody else have any suggestions?

Bill
0
 
villavejAuthor Commented:
Bill,  Than you very much.  You helped us resolve the core problem.  I was able to register around 7 data sources without issues.   It's a procedural issue on how to enter and launch web services.  I'll accept you solution for 500 pts.
0
 
grant300Commented:
That is very generous of you.

I am glad I was able to help.

Regards,
Bill
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now