New transaction cannot enlist in the specified transaction coordinator

I was faced with this error when I was trying to configure a web application and trying enter a transaction through the virtual website. Thanks to the internet, I found a lot of information on the internet.

Here are the steps I followed to correct this:

Start the Component Services administrative tool. To do this, click Start, click Run, type dcomcnfg.exe, and then click OK.
In the console tree of the Component Services administrative tool, expand Component Services, expand Computers, right-click My Computer, and then click Properties.
Click the MSDTC tab, and then click Security Configuration.

Turn on the Network DTC Access
Allow Inbound
Allow Outbound
Enable XA Transactions
Choose No Authentication required

Save these settings and reboot your system.

The error is fixed.

In Windows Server 2003 SP1 and in Windows XP SP2, the Distributed Transaction Coordinator service gives you more control over the network communication between computers. By default, all network communication is disabled. The Distributed Transaction Coordinator Security Configuration dialog box has been enhanced so that you can manage these communication settings.

Library of free database models

The library includes hundreds of sample database schemas for tons of topics â?? ranging from â??Airline Reservationsâ?? to â??Organizations and Peopleâ?? to â??Car Servicingâ?? to â??Pizza Deliveryâ??.

read more

How to Normalise Your Database

Normalisation is part of successful database design.Without normalisation, database systems can be inaccurate, slow, and inefficient and they might not produce the data you expect.

read more

Library of free database models

The library includes hundreds of sample database schemas for tons of topics â?? ranging from â??Airline Reservationsâ?? to â??Organizations and Peopleâ?? to â??Car Servicingâ?? to â??Pizza Deliveryâ??.

read more

Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.

I worked a long time on this error with the application I am developing in ASP. My research today has shown that this is often a datatype problem. If the value that is filled in the form is not the same as that has been defined in the database, you get this error. For example, if you are passing a null value to a field that doesn't accept them (DATETIME field) or passing an value to a Boolean field etc.

For more information on this error, click here

"[Microsoft][ODBC Microsoft Access Driver]General error Unable to openregistry key 'Temporary (volatile) Jet DSN for process"

This error occured for the first time to me today when I set up my connection in the asp code. I spent about 15 mins. thinking why this error is occuring. I thought this could be something related to permissions either for the database or for the directory where the database is residing.

These are the things I tried:

• the webserver environment needs "write" permission to the directory where the Access database resides. So, set permissions first. Go to Windows Explorer, Tools, Folder Options, View and turn off the very last entry in the list ("Use simple file sharing") if you haven't already done so.
• When you right-click on the database folder there is a "Security" tab . Make sure you give write permission to the folder with the Access database to the "IUSR_****" account (with *** being your computer's name). This account is used by IIS, as default, to evaluate permissions for the default access to your local website and scripts.
• Give the same user IUSR_ (or whatever is the default account) access to the TEMP directory of Windows. MS Access might need to write some stuff there.
  Give the same account write permission in MS Access itself. These permissions can be reset by Access if you compact and repair the database so keep in mind to refresh this permission if necessary.
• If you still get the error "[Microsoft][ODBC Microsoft Access Driver]General error Unable to openregistry key 'Temporary (volatile) Jet DSN for process", check that the database is really in the directory referenced by the DSN or the connection string in your ASP file! Also, check for misspellings in the file name and whether the path is correct. This was the reason for my error today.