# Run-time Errors

### TPETRAN

Problem: TPETRAN error is typically caused by problems in propagating the transaction from WebLogic to Tuxedo. The most common causes of this are:

- The application has not performed a tpopen()
- No TMS is running in the Tuxedo domain
- The TLOG file for the domain gateway hasn't been created.

Cause/Resolution: If the Tuxedo application does not need to participate in the same transaction as WebLogic started, then simply set the transaction attribute on the @jc:tuxedo tag to NotSupported. See How Do I: Create a Web Service with Transactional Support in the Tuxedo Service, for more information on enabling transaction support in your Tuxedo application.

### TPENOENT

Problem: The TPENOENT error is typically caused when the service listed in the service attribute (or in the send-queue-space attribute) of the @jc:tuxedo tag has not been imported.

Resolution: Verify with the WebLogic Console that the service has been imported and that the WTC server has been deployed.

### TPESYSTEM from a Service that Returns a VIEW Buffer

Problem: TPESYSTEM indicates a generic system error and can be caused by many different types of problems. In a service that returns a VIEW buffer, TPESYSTEM often indicates that WTC has not been given the class for the type of buffer that is being returned. Therefore, the reply cannot be constructed.

Resolution: Verify that WTC knows about the VIEW buffer class. The class should either be named in the method's view-class attribute, or should be configured as a resource in the WTC configuration.