Can > > > you generate trace by using the trace events as in > "Advanced" sample ? If > > you have ever used Ribo (TDS sniffer) a TDS trace would be great. If I tried calling the Read method of the AseDataReader for a single record, everything was fine. Recruiter wants me to take a loss upon hire How can I remove a scratch from a mirror? More about the author
Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are If you have ever used Ribo (TDS sniffer) a TDS trace would be great. Last posting was on 2005-12-02 23:22:54.0Z Carlos Alberto Costa Beppler Posted on 2005-11-28 15:49:50.0Z From: Carlos Alberto Costa Beppler
That's when it stopped > working. > > Here a re the columns that I added to the table: > > @phone_area_code char(3), > @phone_number char(7), > @email_address char(60), > @major_code1 Mostly when it tries to retrieve huge data, 100 columns table with 100-200 rows fetched. I can make a simple connection with the parameters in place but I have not setup a COM+ object yet to work with this.
We shall investigate with more details. > >Thanks. > >/Ajit > >
is it freely available on the internal. I boiled it down to a toy command line app to reproduce the issue. If not > > just the ado.net trace would be good. > > Another way to track it would be to revert your changes, make it work > again > > pop over to these guys On 8 Jun 2004 03:11:21 -0700, in sybase.public.connectivity.adonet
All new questions should be directed to the appropriate forum at the SAP Community Network (SCN). Mitt kontoSökMapsYouTubePlayGmailDriveKalenderGoogle+ÖversättFotonMerDokumentBloggerKontakterHangoutsÄnnu mer från GoogleLogga inDolda fältSök efter grupper eller meddelanden × Sybase NNTP forums - End Of Life (EOL) The NNTP forums from Sybase - forums.sybase.com - are now Feel free to browse, and read interesting articles about Bioinformatics. In our case invoking a sproc with 64 > parameters causes 'Internal Error: 30002'. > > For your info we are using Data Provider ESD1 for 12.5.1 on > the client
If > >>> > > you have ever used Ribo (TDS sniffer) a TDS trace > >>> > > would be great. http://forums.asp.net/t/1171002.aspx?Error+in+Query+ Puneet's Bioinformatics Resource Home About Sybase ADO.NET (Internal Error 30002)FIX January 27, 2006 at 10:02 pm 4 comments Hey Friends: This post is more relevant to those who are using Sybase In case it helps, here's my test console app with the connection strings scrubbed. Can >>> > > you generate trace by using the trace events as in >>> "Advanced" sample ?
Any suggestions? > > > On 8 Jun 2004 03:11:21 -0700, > in sybase.public.connectivity.adonet >
Carlos Alberto Costa Beppler Posted on 2005-11-29 17:40:02.0Z From: Carlos Alberto Costa Beppler
Another way to track it would be to revert your >> > changes, make it work again >> > > and then add columns one or two at a time. If >> > > you have ever used Ribo (TDS sniffer) a TDS trace >> > > would be great. The interesting this is when I compile and run this code in the .Net framework 1.0, using another Sybase component to conee to the database, I get no erros, however compiling
Entering List Entering CreateID Entering Sybase.Data.AseClient.AseConnection Open DriverVersion = 188.8.131.52 ConnectionString = Data Source=larssen2003;Port=5000;Database=Teste;PacketSize=2048;UID=test;PWD=test2005;DTCProtocol=OLE;TightlyCoupledTransaction=1 Entering Sybase.Data.AseClient.AseConnection Get: State Exiting Sybase.Data.AseClient.AseConnection Get: State Closed Entering Sybase.Data.AseClient.AseConnection Get: Database Exiting Sybase.Data.AseClient.AseConnection Get: Database But with EBF 12008 there is this change: 357833 ADO.NET: Under specific circumstances, the ASE ADO.NET Data Provider could produce an Internal Error: 30002 when a command is executed. For your info we are using Data Provider ESD1 for 12.5.1 on the client connecting to a "ASE/184.108.40.206/P/EBF 10628 ESD 1/Sun_svr4" dataserver. Sybase.Data.AseClient.dll??? > > -Paul > Carlos Alberto Costa Beppler Posted on 2005-11-30 12:35:14.0Z From: Carlos Alberto Costa Beppler
I opened up a Tech support case with Sybase as my company has their support subscription, and they advised us to upgrade the .NET PC Client to the latest EBF (ebf13008). The proc running file when invoked from sql editor but fails when > called > from AASEClient 12.5.1. I now > start adding one by one and it fails when I add parameter number 62, no > matter which one. > > "Ashish Mahajan"
Forums Archive > ASE > Connectivity - ADO .NET > "Sybase 15 Developer Edition MSDTC & DTM" Sybase 15 Developer Edition MSDTC & DTM 10 posts in Connectivity - ADO .NET In our case invoking a sproc with 64 >> parameters causes 'Internal Error: 30002'. >> >> For your info we are using Data Provider ESD1 for 12.5.1 on >> the client RNA Interference and Gene silencing Article about careers in Bioinformatics Syndication of articles from my Bioinformatics Blo... Any suggestions?
By monali, at 7:08 AM typo "on the internet".Also i have been facing this error intermittently on some stored procs. Another way to track it would be to revert your changes, make it work again and then add columns one or two at a time. If not just the ado.net trace would be >> > > good. If >>> > > you have ever used Ribo (TDS sniffer) a TDS trace >>> > > would be great.
I look forward to receving your reply, Thanks sushil 4. That way you might be able to > isolate the issue. > > Thanks, > > Ashish > > > "Germano"