Receive ".NET: Unknonw error 1"

Receive ".NET: Unknonw error 1"

Postby xcbroker » Thu 24 Sep 2009 13:53

I have installed CoreLab OraDirect for .NET 2.0 and the sample projects worked just fine with my sample Oracle database on a separate machine. I followed the sample and developed our custom SharePoint web parts to connect to Oracle. Everything worked fine until yesterday, I started to receive error message like: NET: Unknown error 1

Running the sample projects, I got the same error. I checked event viewer and there is no error.

What could be the problem? What should I check for?

Thanks in advance.

Sean
xcbroker
 
Posts: 21
Joined: Tue 07 Apr 2009 21:25

Postby Shalex » Mon 28 Sep 2009 06:16

Could you please post here your call stack? If there is no call stack when you are running your Visual Studio in the debug mode, please obtain the call stack by attaching to your Visual Studio with launched sample project from another instance of Visual Studio. To obtain the call stack, connect from one Visual Studio (Debug | Attach to Proccess) to the process of another Visual Studio. Before attaching don't forget to make these settings in VS that you are using to debug the other one: a) in the (Debug | Exceptions) window select Common Language Runtime Exceptions; b) in the (Tools | Options) window, Debugging | General - clear Enable Just My Code (Managed Only).

Does this problem persist only with applications, which use OraDirect .NET?
Shalex
Devart Team
 
Posts: 7539
Joined: Thu 14 Aug 2008 12:44

Postby xcbroker » Tue 29 Sep 2009 00:10

The same problem occurred to both the sample windows form application and the application in SharePoint environment. Here is the call stack from the sample DataSet application demo.

ystem.Exception was unhandled
Message="NET: Unknown error 1"
Source="CoreLab.Oracle"
StackTrace:
at CoreLab.Oracle.bl.b(Int32 A_0)
at CoreLab.Oracle.o.b()
at CoreLab.Oracle.d.a(Int32 A_0, bx A_1)
at CoreLab.Oracle.OracleCommand.a(CommandBehavior A_0, IDisposable A_1, Int32 A_2, Int32 A_3)
at CoreLab.Common.DbCommandBase.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at CoreLab.Oracle.OracleDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable)
at Samples.DataSetDemoControl.btFill_Click(Object sender, EventArgs e) in C:\Program Files\CoreLab\OraDirect.NET2\Samples\WinForms\CS\DataSet\DataSetDemoControl.cs:line 194
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.SendMessage(HandleRef hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at System.Windows.Forms.Control.SendMessage(Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.Control.ReflectMessageInternal(IntPtr hWnd, Message& m)
at System.Windows.Forms.Control.WmCommand(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
at System.Windows.Forms.Control.DefWndProc(Message& m)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at Samples.MainForm.Main() in C:\Program Files\CoreLab\OraDirect.NET2\Samples\WinForms\CS\MainForm.cs:line 27
at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
xcbroker
 
Posts: 21
Joined: Tue 07 Apr 2009 21:25

Postby Shalex » Wed 30 Sep 2009 07:24

Please give us the following information:
1) the version and edition of your dotConnect for Oracle. You can see it in the Tools | Oracle | About menu of Visual Studio.
Have you tried to run your project with the latest 5.25.44 build of dotConnect for Oracle?
2) the version of your Oracle server and client you are using;
3) the version and edition of your operating system;
4) please send us (http://www.devart.com/company/contact.html) a small test project and the DDL/DML script
to reproduce the problem.
We will investigate the issue and notify you about the results as soon as possible.
Shalex
Devart Team
 
Posts: 7539
Joined: Thu 14 Aug 2008 12:44

Postby xcbroker » Wed 30 Sep 2009 15:52

1. The version for dotConnect for Oracle is: 4.60.33.0.
2. Oracle server is Oracle 11g Release 1 (11.1), database connection is using Direct mode.
3. Oracle server is on Windows 2003 R2 SP2 on a virtual machine and application runs on a separate virtual machine on Windows 2003 R2 SP2.
4. The problem can be reproduced with the sample projects from the install of CoreLab OraDirect for .NET 2.
xcbroker
 
Posts: 21
Joined: Tue 07 Apr 2009 21:25

Postby Shalex » Mon 05 Oct 2009 08:34

This error arises when server tries to process a command that is not supported by protocol. The problem can be in the request command, data type. Try using the latest 5.25.44 version of dotConnect for Oracle.
Shalex
Devart Team
 
Posts: 7539
Joined: Thu 14 Aug 2008 12:44

Postby xcbroker » Sun 01 Nov 2009 18:38

dotConnect for Oracle is embedded as part of our product shipped to the customer as custom web part for SharePoint. There is not an easy way to update the version for all the customers. So we cannot just update to the latest dotConnect for Oracle, besides, the same code worked couple months ago and just recently stopped working without any code change. So there is not a unsupported protocol involved.
xcbroker
 
Posts: 21
Joined: Tue 07 Apr 2009 21:25

Postby Shalex » Mon 02 Nov 2009 11:39

The possible reason of the problem also can be usage of the same connection object in several threads (please create a separate connection object per thread). Do our samples from the installation folder work fine in your environment?
Shalex
Devart Team
 
Posts: 7539
Joined: Thu 14 Aug 2008 12:44

Postby xcbroker » Tue 10 Nov 2009 03:40

Problem was gone after I reset the password for the connection string on the Oracle side. Thanks.
xcbroker
 
Posts: 21
Joined: Tue 07 Apr 2009 21:25


Return to dotConnect for Oracle