This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: Install Anywhere Issue with plugins on Windows 2008
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 28, 2009
02:01 PM
Install Anywhere Issue with plugins on Windows 2008
Hopefully someone here can help me figure this issue out.
I am using the JTDS-1.2.2 JDBC driver in an IA plugin to connect to SQL Server. The plugin works fine on XP, Vista and Windows 2003 and is something I've used in my installers for a good 9 months now. However when the plugin is run from an installer on Windows 2008 64 bit (R2) I get a very odd error.
Network error IOException: Protocol wrong type for socket: create
at com.infor.scm.installer.db.DBUtilDBType.access1.run(DashoA10*..)
Caused by: java.sql.SQLException: Network error IOException: Protocol wrong type for socket: create
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.(ConnectionJDBC2.java:385)
at net.sourceforge.jtds.jdbc.ConnectionJDBC3.(ConnectionJDBC3.java:50)
This error only occurs when the installer is run on Windows 2008 R2 64 bit. If I take the same code in the plugin and just run it as a java app it runs fine and does the DB access as it should.
I pulled the JTDS JDBC driver apart and tracked down the error to a simple opening of a socket. I tested a plugin that just opens a socket and it fails inside of install anywhere but runs fine outside of install anywhere.
This is the final test code I narrowed the issue down to. The error line is in bold.
Socket socket = new Socket();
InetSocketAddress address = new InetSocketAddress("localhost",1433);
socket.connect(address, 2000);
socket.close();
I am using the JTDS-1.2.2 JDBC driver in an IA plugin to connect to SQL Server. The plugin works fine on XP, Vista and Windows 2003 and is something I've used in my installers for a good 9 months now. However when the plugin is run from an installer on Windows 2008 64 bit (R2) I get a very odd error.
Network error IOException: Protocol wrong type for socket: create
at com.infor.scm.installer.db.DBUtilDBType.access1.run(DashoA10*..)
Caused by: java.sql.SQLException: Network error IOException: Protocol wrong type for socket: create
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.
at net.sourceforge.jtds.jdbc.ConnectionJDBC3.
This error only occurs when the installer is run on Windows 2008 R2 64 bit. If I take the same code in the plugin and just run it as a java app it runs fine and does the DB access as it should.
I pulled the JTDS JDBC driver apart and tracked down the error to a simple opening of a socket. I tested a plugin that just opens a socket and it fails inside of install anywhere but runs fine outside of install anywhere.
This is the final test code I narrowed the issue down to. The error line is in bold.
Socket socket = new Socket();
InetSocketAddress address = new InetSocketAddress("localhost",1433);
socket.connect(address, 2000);
socket.close();
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 15, 2010
11:03 AM
Hi, I was wondering if you got this issue resolved? I am having the same issue. It works on a 32-bit machine, but not for a 64 bit machine with 64-bit SQL server.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 16, 2010
12:31 AM
Hi,
Is this plugin/custom code running in the install/ uninstall phases ?
Thanks,
Is this plugin/custom code running in the install/ uninstall phases ?
Thanks,
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 16, 2010
07:56 AM
Hi, yes, it is running during the install phase
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 11, 2010
12:27 AM
We found the similar problem on 2008 64bit when using httpconnection.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)