Search results for query: *

I think we are talking about two different things here. The commandtimeout parameter you are talking about is, I believe, the ADO command timeout parameter. The parameter I am referring to is the MTS timeout parameter. The MTS parameter controls how long a transaction will be allowed to run...

It sounds like you have the same situation we have. Our users log into both a Windows NT Domain and Novell when they log onto their desktops. The passwords for Novell and the domain are kept in sync. As such, these users can utilize our three-tier application that makes use of MTS without...

Open the Management Console for MTS (mmc.exe) and expand the folder structure on the left-hand side until you see the My Computer Icon. Right-click on the My Computer Icon, choose Properties. Choose the Options Tab. You should see the Transaction Timeout parameter there. I believe that the...

One final point: The problem I was trying to solve originally was the "No Transaction Active" error that I was receiving. The cause of this error is quite simple (although Microsoft was never able to tell me this). In MTS, one can set the Transactions will timeout in xx seconds...

After much pain, we found a way to make this problem go away. Per my 4/22 post, the problem went away in our development environment when we rebuilt the server. We thought that reapplying SP6a during the rebuild was what did the trick. So we went to production with the following process: 1)...

Are you getting the 'distributed transaction waiting for lock error', the 'no transaction active error', or some other error? Also, what is the OS of you middle-tier? We've been working with MS on the 'distributed transaction waiting for lock error.' Apparently, this error was fairly common...

I get the exact same thing. Any answers on this?

Any help would be greatly appreciated with the following situation: I have a 3-tier app running on NT 4.0 sp6a with Oracle 8.1.7.1.5 client. Our Oracle database is 8.1.7.2.0 and is running on a Unix server. I am using Visual Basic 6.0 runtime modules sp5. We were using MDAC 2.5sp2 but...

For Windows NT 4.0, MTS is not installed automatically. You have to choose to install it from the Option Pack. If you see HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Transaction Server in the registry, then it has been installed. Hope this helps.