Error while running the application using Enterprise Services Transactions.

[srinivasan.shanmugapillai]

Hi,

I'm running a VB.NET windows applicatrion that is using the enterprise
services transactions.

While running this application without enterprise services support, a
connection is established and data is retrieved sucessfully.

when the class is configured to run inside enterprise services, it
fails without proper error description.

Error :

An unhandled exception of type 'System.Data.OleDb.OleDbException'
occurred in mscorlib.dll
additional information :No Error information available : E_NOINTERFACE

Thanks,
Srini.

 

[Mr. Arnold]

Hi,

I'm running a VB.NET windows applicatrion that is using the enterprise
services transactions.

While running this application without enterprise services support, a
connection is established and data is retrieved sucessfully.

when the class is configured to run inside enterprise services, it
fails without proper error description.

Why do you have the solution on a read of data in a Enterprise Services
transaction?

You're reading the data in this case. There should be no need for a
transactional mode on a read of data from a table or tables. What are you
going to Commit or Rollback too on the reading of data. You're just reading
the data.

From a transactional standpoint, a transactional solution should only be
applied to inserting or updating of records where a Commit or Rollback can
be applied.

Error :

An unhandled exception of type 'System.Data.OleDb.OleDbException'
occurred in mscorlib.dll
additional information :No Error information available : E_NOINTERFACE

Maybe, you should look into using ADO.NET's transactional features/abilities
insead of
using Enterprise Services, unless you are forced to use a Com+ Server in
this situation. ADO.NET transactions don't carry the processing overhead,
like using Enterprise Services.

I am curious. Are you the infamous Reno, NV Srini?

 

[srinivasan.shanmugapillai]

Why do you have the solution on a read of data in aEnterpriseServices
transaction?

You're reading the data in this case. There should be no need for a
transactional mode on a read of data from a table or tables. What are you
going to Commit or Rollback too on the reading of data. You're just reading
the data.

From a transactional standpoint, a transactional solution should only be
applied to inserting or updating of records where a Commit or Rollback can
be applied.





Maybe, you should look intousingADO.NET's transactional features/abilities
insead ofusingEnterpriseServices, unless you are forced to use a Com+ Server in
this situation. ADO.NET transactions don't carry the processing overhead,
likeusingEnterpriseServices.

I am curious. Are you the infamous Reno, NV Srini?

Hi Arnold,

Thanks for your reply.

Actually I just want to test a sample application on how to use the
enterprise services with .NET.

And I am not sure whether we will get all features of MTS(like object
pooling, automatic transaction management, queued components,loosely
coupled events etc), if we are not using a serviced component.

Thanks,
Srini.