Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SqlSimon
Starting Member
4 Posts |
 Posted - 2009-03-10 : 07:33:19
|
| Hi folks,I hope someone can help me.I am trying to get several developer workstations working with the follow setup... * Windows XP (32-bit) SP2* SQL 2005 Developer - SP3* MS OLE DB for DB2 v2.0I need to get the DB2 to connect to transfer tables in a SSIS package. I am able to get the connections working and tested OK, and to 'build the Packages' in the Data Source dialog boxes.But when I try and to access the list of tables or preview the results of simple SELECT statements in an OLE DB Datasource, I get an error "Internal NetLib Error". I have the same software, albeit 64-bit, and connection strings and SSIS packages working fine, if I develop directly on the SQL server with remote desktop, but this is not good practice. * Windows 2003 Enterprise Server 64-bit (x64)* SQL 2005 Enterprise (x64) - SP3 * MS OLE DB for DB2 v2.0 (x64) I have Google'd like crazy to try and sort this, but with no success for about a week so far.Any clues what I could be missing, or where interrogate the generic Internal Netlib error in more detail ?Any help greatly appreciated.Simon P. |
|
|
SqlSimon
Starting Member
4 Posts |
Posted - 2009-03-13 : 11:34:24
|
| Hi All,After a many days of head-scratching, and even using a phone-a-friend lifeline to Microsoft, I managed to resolve this issue myself.It appears the problems is with Windows XP missing key NLS (Language support) files which are used by the Microsoft OLE DB provider for DB2. I compared the files and related registry keys between Windows 2003 server and XP and saw that there were many more files and entries in the server.I copied the NLS files from the system32 (on a 32-bit server) folder and the “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls” registry key to my XP workstations. Rebooted. And all now works perfectly as it did on Windows 2003.The support contact at MS did some tests to prove my solution, and it does indeed appear that the OLE DB Provider installer is looking for these missing registry entries that do not exist on Windows client operating systems (XP, Vista and 7.0). |
 |
|
|
|
|
|
|
|
Internal Netlib Error with MS OLE DB for DB2