Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working ?
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaun
Strange. It looks that both strings are correct (although I would put the
network part toward the end as a personal preference).
I often refer to http://www.connectionstrings.com/ for examples and usage of
connection strings.
Keith
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.c om...
> Hi
> Odd one here, I have a local version of SQL running on my laptop for
> demos, been working fine for years yet yesterday I suddenly get an
> error "Invalid Conection Parameter" running a sproc using the
> following connection string (Its an Access 2002 App to SQL 2000)
> strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> Works fine if I use the server based SQL resource
> So I change it to be the following and it starts working ?
> strConnect = "Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> So it started not liking the 'Network=DBMSSOCN' part but both the
> datbases have TCP/IP and Named Pipes setup as network protocols and
> bot have not chnaged config for years
> I did install SP2 for XP a few weeks ago but I'm sure I have run it
> since (mind you I wish I'd never done SP2 with all the unasked for
> 'extras' MS dump on your PC but thats another thread)
> Thanks all
> shaun
|||Thanks for the link Keith
Yep it is odd as I thought both were fine as well and the one now is
not working worked fine for months!!!
Ah well the odditiess of Microsoft
Cheers
Shaun
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message news:<uQts2dgCFHA.3908@.TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
> Strange. It looks that both strings are correct (although I would put the
> network part toward the end as a personal preference).
> I often refer to http://www.connectionstrings.com/ for examples and usage of
> connection strings.
> --
> Keith
>
> "Shaun" <shaunsizen@.msn.com> wrote in message
> news:4a2f9143.0502030133.5892ee76@.posting.google.c om...
|||Win XP SP2 also probably updated your MDAC or exposed an MDAC vunerability
that was updated recently through Windows Updates.
Nevertheless, you are using the OLEDB for ODBC, MSADSQL? Why not just use
the SQLOLEDB directly seeing as you are not using the functionality that an
ODBC DSN would give you? If I am wrong, then it is the DRIVER=SQLSERVER
that is throwing you. That's an ODBC Only OLEDB parameter.
Sincerely,
Anthony Thomas
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.c om...
Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working ?
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaun
Showing posts with label stops. Show all posts
Showing posts with label stops. Show all posts
Friday, February 24, 2012
Connection String suddenly Stops working
Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working '
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaunStrange. It looks that both strings are correct (although I would put the
network part toward the end as a personal preference).
I often refer to http://www.connectionstrings.com/ for examples and usage of
connection strings.
--
Keith
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.com...
> Hi
> Odd one here, I have a local version of SQL running on my laptop for
> demos, been working fine for years yet yesterday I suddenly get an
> error "Invalid Conection Parameter" running a sproc using the
> following connection string (Its an Access 2002 App to SQL 2000)
> strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> Works fine if I use the server based SQL resource
> So I change it to be the following and it starts working '
> strConnect = "Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> So it started not liking the 'Network=DBMSSOCN' part but both the
> datbases have TCP/IP and Named Pipes setup as network protocols and
> bot have not chnaged config for years
> I did install SP2 for XP a few weeks ago but I'm sure I have run it
> since (mind you I wish I'd never done SP2 with all the unasked for
> 'extras' MS dump on your PC but thats another thread)
> Thanks all
> shaun|||Thanks for the link Keith
Yep it is odd as I thought both were fine as well and the one now is
not working worked fine for months!!!
Ah well the odditiess of Microsoft
Cheers
Shaun
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message news:<uQts2dgCFHA.3908@.TK2MSFTNGP12.phx.gbl>...
> Strange. It looks that both strings are correct (although I would put the
> network part toward the end as a personal preference).
> I often refer to http://www.connectionstrings.com/ for examples and usage of
> connection strings.
> --
> Keith
>
> "Shaun" <shaunsizen@.msn.com> wrote in message
> news:4a2f9143.0502030133.5892ee76@.posting.google.com...
> > Hi
> >
> > Odd one here, I have a local version of SQL running on my laptop for
> > demos, been working fine for years yet yesterday I suddenly get an
> > error "Invalid Conection Parameter" running a sproc using the
> > following connection string (Its an Access 2002 App to SQL 2000)
> >
> > strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
> > Server;UID=abc;PWD=def"
> >
> > Works fine if I use the server based SQL resource
> >
> > So I change it to be the following and it starts working '
> >
> > strConnect = "Server=" & DB_Server & ";DRIVER=SQL
> > Server;UID=abc;PWD=def"
> >
> > So it started not liking the 'Network=DBMSSOCN' part but both the
> > datbases have TCP/IP and Named Pipes setup as network protocols and
> > bot have not chnaged config for years
> >
> > I did install SP2 for XP a few weeks ago but I'm sure I have run it
> > since (mind you I wish I'd never done SP2 with all the unasked for
> > 'extras' MS dump on your PC but thats another thread)
> >
> > Thanks all
> > shaun|||Win XP SP2 also probably updated your MDAC or exposed an MDAC vunerability
that was updated recently through Windows Updates.
Nevertheless, you are using the OLEDB for ODBC, MSADSQL? Why not just use
the SQLOLEDB directly seeing as you are not using the functionality that an
ODBC DSN would give you? If I am wrong, then it is the DRIVER=SQLSERVER
that is throwing you. That's an ODBC Only OLEDB parameter.
Sincerely,
Anthony Thomas
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.com...
Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working '
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaun
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working '
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaunStrange. It looks that both strings are correct (although I would put the
network part toward the end as a personal preference).
I often refer to http://www.connectionstrings.com/ for examples and usage of
connection strings.
--
Keith
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.com...
> Hi
> Odd one here, I have a local version of SQL running on my laptop for
> demos, been working fine for years yet yesterday I suddenly get an
> error "Invalid Conection Parameter" running a sproc using the
> following connection string (Its an Access 2002 App to SQL 2000)
> strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> Works fine if I use the server based SQL resource
> So I change it to be the following and it starts working '
> strConnect = "Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> So it started not liking the 'Network=DBMSSOCN' part but both the
> datbases have TCP/IP and Named Pipes setup as network protocols and
> bot have not chnaged config for years
> I did install SP2 for XP a few weeks ago but I'm sure I have run it
> since (mind you I wish I'd never done SP2 with all the unasked for
> 'extras' MS dump on your PC but thats another thread)
> Thanks all
> shaun|||Thanks for the link Keith
Yep it is odd as I thought both were fine as well and the one now is
not working worked fine for months!!!
Ah well the odditiess of Microsoft
Cheers
Shaun
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message news:<uQts2dgCFHA.3908@.TK2MSFTNGP12.phx.gbl>...
> Strange. It looks that both strings are correct (although I would put the
> network part toward the end as a personal preference).
> I often refer to http://www.connectionstrings.com/ for examples and usage of
> connection strings.
> --
> Keith
>
> "Shaun" <shaunsizen@.msn.com> wrote in message
> news:4a2f9143.0502030133.5892ee76@.posting.google.com...
> > Hi
> >
> > Odd one here, I have a local version of SQL running on my laptop for
> > demos, been working fine for years yet yesterday I suddenly get an
> > error "Invalid Conection Parameter" running a sproc using the
> > following connection string (Its an Access 2002 App to SQL 2000)
> >
> > strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
> > Server;UID=abc;PWD=def"
> >
> > Works fine if I use the server based SQL resource
> >
> > So I change it to be the following and it starts working '
> >
> > strConnect = "Server=" & DB_Server & ";DRIVER=SQL
> > Server;UID=abc;PWD=def"
> >
> > So it started not liking the 'Network=DBMSSOCN' part but both the
> > datbases have TCP/IP and Named Pipes setup as network protocols and
> > bot have not chnaged config for years
> >
> > I did install SP2 for XP a few weeks ago but I'm sure I have run it
> > since (mind you I wish I'd never done SP2 with all the unasked for
> > 'extras' MS dump on your PC but thats another thread)
> >
> > Thanks all
> > shaun|||Win XP SP2 also probably updated your MDAC or exposed an MDAC vunerability
that was updated recently through Windows Updates.
Nevertheless, you are using the OLEDB for ODBC, MSADSQL? Why not just use
the SQLOLEDB directly seeing as you are not using the functionality that an
ODBC DSN would give you? If I am wrong, then it is the DRIVER=SQLSERVER
that is throwing you. That's an ODBC Only OLEDB parameter.
Sincerely,
Anthony Thomas
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.com...
Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working '
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaun
Connection String suddenly Stops working
Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working '
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaunStrange. It looks that both strings are correct (although I would put the
network part toward the end as a personal preference).
I often refer to http://www.connectionstrings.com/ for examples and usage of
connection strings.
Keith
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.com...
> Hi
> Odd one here, I have a local version of SQL running on my laptop for
> demos, been working fine for years yet yesterday I suddenly get an
> error "Invalid Conection Parameter" running a sproc using the
> following connection string (Its an Access 2002 App to SQL 2000)
> strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> Works fine if I use the server based SQL resource
> So I change it to be the following and it starts working '
> strConnect = "Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> So it started not liking the 'Network=DBMSSOCN' part but both the
> datbases have TCP/IP and Named Pipes setup as network protocols and
> bot have not chnaged config for years
> I did install SP2 for XP a few weeks ago but I'm sure I have run it
> since (mind you I wish I'd never done SP2 with all the unasked for
> 'extras' MS dump on your PC but thats another thread)
> Thanks all
> shaun|||Thanks for the link Keith
Yep it is odd as I thought both were fine as well and the one now is
not working worked fine for months!!!
Ah well the odditiess of Microsoft
Cheers
Shaun
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message news:<uQts2dgCFHA.3908@.TK2MS
FTNGP12.phx.gbl>...[vbcol=seagreen]
> Strange. It looks that both strings are correct (although I would put the
> network part toward the end as a personal preference).
> I often refer to http://www.connectionstrings.com/ for examples and usage
of
> connection strings.
> --
> Keith
>
> "Shaun" <shaunsizen@.msn.com> wrote in message
> news:4a2f9143.0502030133.5892ee76@.posting.google.com...|||Win XP SP2 also probably updated your MDAC or exposed an MDAC vunerability
that was updated recently through Windows Updates.
Nevertheless, you are using the OLEDB for ODBC, MSADSQL? Why not just use
the SQLOLEDB directly seeing as you are not using the functionality that an
ODBC DSN would give you? If I am wrong, then it is the DRIVER=SQLSERVER
that is throwing you. That's an ODBC Only OLEDB parameter.
Sincerely,
Anthony Thomas
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.com...
Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working '
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaun
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working '
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaunStrange. It looks that both strings are correct (although I would put the
network part toward the end as a personal preference).
I often refer to http://www.connectionstrings.com/ for examples and usage of
connection strings.
Keith
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.com...
> Hi
> Odd one here, I have a local version of SQL running on my laptop for
> demos, been working fine for years yet yesterday I suddenly get an
> error "Invalid Conection Parameter" running a sproc using the
> following connection string (Its an Access 2002 App to SQL 2000)
> strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> Works fine if I use the server based SQL resource
> So I change it to be the following and it starts working '
> strConnect = "Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> So it started not liking the 'Network=DBMSSOCN' part but both the
> datbases have TCP/IP and Named Pipes setup as network protocols and
> bot have not chnaged config for years
> I did install SP2 for XP a few weeks ago but I'm sure I have run it
> since (mind you I wish I'd never done SP2 with all the unasked for
> 'extras' MS dump on your PC but thats another thread)
> Thanks all
> shaun|||Thanks for the link Keith
Yep it is odd as I thought both were fine as well and the one now is
not working worked fine for months!!!
Ah well the odditiess of Microsoft
Cheers
Shaun
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message news:<uQts2dgCFHA.3908@.TK2MS
FTNGP12.phx.gbl>...[vbcol=seagreen]
> Strange. It looks that both strings are correct (although I would put the
> network part toward the end as a personal preference).
> I often refer to http://www.connectionstrings.com/ for examples and usage
of
> connection strings.
> --
> Keith
>
> "Shaun" <shaunsizen@.msn.com> wrote in message
> news:4a2f9143.0502030133.5892ee76@.posting.google.com...|||Win XP SP2 also probably updated your MDAC or exposed an MDAC vunerability
that was updated recently through Windows Updates.
Nevertheless, you are using the OLEDB for ODBC, MSADSQL? Why not just use
the SQLOLEDB directly seeing as you are not using the functionality that an
ODBC DSN would give you? If I am wrong, then it is the DRIVER=SQLSERVER
that is throwing you. That's an ODBC Only OLEDB parameter.
Sincerely,
Anthony Thomas
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.com...
Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working '
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaun
Tuesday, February 14, 2012
Connection Reset
Hi all
I have build an application on top of SQL Server 2005 and i am using microsoft driver. My application stops periodically becoz of Database Connection Loss and I get the following exception
com.microsoft.sqlserver.jdbc.SQLServerException: An exception occurred during the DBComms.transmit operation. Exception:Socket closed. Context:(5) [Thread[Thread-55,5,main], IO:7e2dc, Dbc:null].
10:06:14:703 AM at com.microsoft.sqlserver.jdbc.SQLServerException.ma keFromDriverError(Unknown Source)
10:06:14:703 AM at com.microsoft.sqlserver.jdbc.DBComms.transmit(Unkn own Source)
10:06:14:703 AM at com.microsoft.sqlserver.jdbc.IOBuffer.sendCommand( Unknown Source)
10:06:14:703 AM at com.microsoft.sqlserver.jdbc.SQLServerStatement.se ndExecute(Unknown Source)
10:06:14:703 AM at com.microsoft.sqlserver.jdbc.SQLServerStatement.do ExecuteQuery(Unknown Source)
10:06:14:703 AM at com.microsoft.sqlserver.jdbc.SQLServerPreparedStat ement.executeQuery(Unknown Source)
Unable to find the exact reason for the above problem. Pl advice
Thanks & Rgds
RoshiniIt apppears to me that you get some kind of timeout, and the connection is closed, but I might be proven wrong. Nevertheless, you should handle such cases, as this may happen even in the most critical high availability solutions, for instance if a SQL Server Cluster is failing over. Applications should be able to reconnect automagically.
I have build an application on top of SQL Server 2005 and i am using microsoft driver. My application stops periodically becoz of Database Connection Loss and I get the following exception
com.microsoft.sqlserver.jdbc.SQLServerException: An exception occurred during the DBComms.transmit operation. Exception:Socket closed. Context:(5) [Thread[Thread-55,5,main], IO:7e2dc, Dbc:null].
10:06:14:703 AM at com.microsoft.sqlserver.jdbc.SQLServerException.ma keFromDriverError(Unknown Source)
10:06:14:703 AM at com.microsoft.sqlserver.jdbc.DBComms.transmit(Unkn own Source)
10:06:14:703 AM at com.microsoft.sqlserver.jdbc.IOBuffer.sendCommand( Unknown Source)
10:06:14:703 AM at com.microsoft.sqlserver.jdbc.SQLServerStatement.se ndExecute(Unknown Source)
10:06:14:703 AM at com.microsoft.sqlserver.jdbc.SQLServerStatement.do ExecuteQuery(Unknown Source)
10:06:14:703 AM at com.microsoft.sqlserver.jdbc.SQLServerPreparedStat ement.executeQuery(Unknown Source)
Unable to find the exact reason for the above problem. Pl advice
Thanks & Rgds
RoshiniIt apppears to me that you get some kind of timeout, and the connection is closed, but I might be proven wrong. Nevertheless, you should handle such cases, as this may happen even in the most critical high availability solutions, for instance if a SQL Server Cluster is failing over. Applications should be able to reconnect automagically.
Subscribe to:
Posts (Atom)