Sybase: SET CHAINED command not allowed within multi-statement transaction

Hello,
I'm getting the error message "SET CHAINED command not allowed within
multi-statement transaction" for CMP Entity beans against Sybase.
The errors appear in my jdbc.log in this order:
010SM: This database does not support the initial proposed set of
capabilities, retrying.) SQLState(010SM)
JZ0EM: End of data.
JZ0SJ: Metadata accessor information was not found on this database.
Please install the required tables
as mentioned in the jConnect documentation.
010SL: Out-of-date metadata accessor information was found on this
database. Ask your database administrat
or to load the latest scripts.) SQLState(010SL)
SQLState(ZZZZZ) vendor code(226)
com.sybase.jdbc2.jdbc.SybSQLException: SET CHAINED command not allowed
within multi-statement transaction.
I'm using JConnect 5.5, WebLogic 6.1 sp3, Solaris 8, and Sybase 11.
The weird thing is, the app works on a box running 6.1 sp2 and Win2k
Prof.
Any ideas?
Thanks!
Dan

Hi Dan,
There is a patch for this sybase problem, please contact [email protected] to
get a temp patch.
sree
"Dan Blaner" <[email protected]> wrote in message
news:[email protected]..
Hello,
I'm getting the error message "SET CHAINED command not allowed within
multi-statement transaction" for CMP Entity beans against Sybase.
The errors appear in my jdbc.log in this order:
010SM: This database does not support the initial proposed set of
capabilities, retrying.) SQLState(010SM)
JZ0EM: End of data.
JZ0SJ: Metadata accessor information was not found on this database.
Please install the required tables
as mentioned in the jConnect documentation.
010SL: Out-of-date metadata accessor information was found on this
database. Ask your database administrat
or to load the latest scripts.) SQLState(010SL)
SQLState(ZZZZZ) vendor code(226)
com.sybase.jdbc2.jdbc.SybSQLException: SET CHAINED command not allowed
within multi-statement transaction.
I'm using JConnect 5.5, WebLogic 6.1 sp3, Solaris 8, and Sybase 11.
The weird thing is, the app works on a box running 6.1 sp2 and Win2k
Prof.
Any ideas?
Thanks!
Dan

Similar Messages

SET CHAINED command not allowed within multi-statement transaction

Hi,
i need to do one transaction and i am setting autocommit(false) and
once i am don ewith my 2 inserts i am settins it to true.
i have like 20 thousand rows and when it is working fine for some inserts but after that it is throwing
"SET CHAINED command not allowed within multi-statement transaction".
can anyone please help me.

You can find some information here:
http://publib.boulder.ibm.com/infocenter/wsphelp/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rtrb_dsaccess.html
it's first problem for sybase DB

Transient Sybase SET CHAINED Tx exception.

Hi,
I've been experiencing a bit of strange behavior with WebLogic 6.1 SP3
and Sybase 11.9.2.4. We are using the Sybase driver that comes with WL
6.1. We are seeing occasional SQLExceptions concerning transactional
modes for stored procedures running in our non-Tx datasource and regular
SQL run in our Tx-datasource. I got the following for the stored
procedure call:
=========================
com.sybase.jdbc.SybSQLException: Stored procedure 'weeklyflow..getWeeklyComplexContacts' may be run only in unchained transaction mode. The 'SET CHAINED OFF' command will cause the current session to use unchained transaction mode.
at com.sybase.tds.Tds.processEed(Tds.java)
at com.sybase.tds.Tds.nextResult(Tds.java)
at com.sybase.jdbc.ResultGetter.nextResult(ResultGetter.java)
at com.sybase.jdbc.SybStatement.nextResult(SybStatement.java)
at com.sybase.jdbc.SybStatement.queryLoop(SybStatement.java)
at com.sybase.jdbc.SybCallableStatement.executeQuery(SybCallableStatement.java)
at weblogic.jdbc.pool.PreparedStatement.executeQuery(PreparedStatement.java:51)
at weblogic.jdbc.rmi.internal.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:56)
at weblogic.jdbc.rmi.SerialPreparedStatement.executeQuery(SerialPreparedStatement.java:42)
at org.ici.weeklyflow.dao.SyBaseWeeklyDataDAOImpl.getWeeklyComplexContacts(SyBaseWeeklyDataDAOImpl.java:3233)
at org.ici.weeklyflow.ejb.WeeklyFlowSBean.getComplexContacts(WeeklyFlowSBean.java:137)
at org.ici.weeklyflow.ejb.WeeklyFlowSBean_1tv6ke_EOImpl.getComplexContacts(WeeklyFlowSBean_1tv6ke_EOImpl.java:785)
at org.ici.weeklyflow.ejb.WeeklyFlowSBean_1tv6ke_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
=======================
All of our stored procedures used for retrieving data have been created
with the 'anymode' transaction mode. They will run correctly for a while
and then occasionally the error will occur.
The regular SQL in the Tx-datasource resulted in the following:
=======================
com.sybase.jdbc.SybSQLException: SET CHAINED command not allowed within multi-statement transaction.
at com.sybase.tds.Tds.processEed(Tds.java)
at com.sybase.tds.Tds.nextResult(Tds.java)
at com.sybase.jdbc.ResultGetter.nextResult(ResultGetter.java)
at com.sybase.jdbc.SybStatement.nextResult(SybStatement.java)
at com.sybase.jdbc.SybStatement.updateLoop(SybStatement.java)
at com.sybase.jdbc.SybStatement.executeUpdate(SybStatement.java)
at com.sybase.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java)
at com.sybase.tds.Tds.setOption(Tds.java)
at com.sybase.jdbc.SybConnection.setAutoCommit(SybConnection.java)
at weblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:594)
at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:115)
at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:78)
at org.ici.weeklyflow.dao.SyBaseWeeklyApplicationDAOImpl.removePrivilegedUser(SyBaseWeeklyApplicationDAOImpl.java:312)
at org.ici.weeklyflow.ejb.WeeklyFlowSBean.removePrivilegedUser(WeeklyFlowSBean.java:322)
at org.ici.weeklyflow.ejb.WeeklyFlowSBean_1tv6ke_EOImpl.removePrivilegedUser(WeeklyFlowSBean_1tv6ke_EOImpl.java:1049)
at org.ici.weeklyflow.ejb.WeeklyFlowSBean_1tv6ke_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
=====================================
I saw other postings concerning this message but those seemed to be in
regards to errors that occurred all the time, does anyone have any ideas?
Thanks,
-Ben DeVore
Tallan, Inc.

You need a patch for SP3. Send an email to Joe Weinstein.
Benjamin DeVore <[email protected]> wrote in message
news:[email protected]...
Hi,
I've been experiencing a bit of strange behavior with WebLogic 6.1 SP3
and Sybase 11.9.2.4. We are using the Sybase driver that comes with WL
6.1. We are seeing occasional SQLExceptions concerning transactional
modes for stored procedures running in our non-Tx datasource and regular
SQL run in our Tx-datasource. I got the following for the stored
procedure call:
=========================
com.sybase.jdbc.SybSQLException: Stored procedure'weeklyflow..getWeeklyComplexContacts' may be run only in unchained
transaction mode. The 'SET CHAINED OFF' command will cause the current
session to use unchained transaction mode.
at com.sybase.tds.Tds.processEed(Tds.java)
at com.sybase.tds.Tds.nextResult(Tds.java)
at com.sybase.jdbc.ResultGetter.nextResult(ResultGetter.java)
at com.sybase.jdbc.SybStatement.nextResult(SybStatement.java)
at com.sybase.jdbc.SybStatement.queryLoop(SybStatement.java)
atcom.sybase.jdbc.SybCallableStatement.executeQuery(SybCallableStatement.java)
atweblogic.jdbc.pool.PreparedStatement.executeQuery(PreparedStatement.java:51)
atweblogic.jdbc.rmi.internal.PreparedStatementImpl.executeQuery(PreparedStatem
entImpl.java:56)
atweblogic.jdbc.rmi.SerialPreparedStatement.executeQuery(SerialPreparedStateme
nt.java:42)
atorg.ici.weeklyflow.dao.SyBaseWeeklyDataDAOImpl.getWeeklyComplexContacts(SyBa
seWeeklyDataDAOImpl.java:3233)
atorg.ici.weeklyflow.ejb.WeeklyFlowSBean.getComplexContacts(WeeklyFlowSBean.ja
va:137)
atorg.ici.weeklyflow.ejb.WeeklyFlowSBean_1tv6ke_EOImpl.getComplexContacts(Week
lyFlowSBean_1tv6ke_EOImpl.java:785)
atorg.ici.weeklyflow.ejb.WeeklyFlowSBean_1tv6ke_EOImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
atweblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
:93)
atweblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
=======================
All of our stored procedures used for retrieving data have been created
with the 'anymode' transaction mode. They will run correctly for a while
and then occasionally the error will occur.
The regular SQL in the Tx-datasource resulted in the following:
=======================
com.sybase.jdbc.SybSQLException: SET CHAINED command not allowed withinmulti-statement transaction.
at com.sybase.tds.Tds.processEed(Tds.java)
at com.sybase.tds.Tds.nextResult(Tds.java)
at com.sybase.jdbc.ResultGetter.nextResult(ResultGetter.java)
at com.sybase.jdbc.SybStatement.nextResult(SybStatement.java)
at com.sybase.jdbc.SybStatement.updateLoop(SybStatement.java)
at com.sybase.jdbc.SybStatement.executeUpdate(SybStatement.java)
atcom.sybase.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java
at com.sybase.tds.Tds.setOption(Tds.java)
at com.sybase.jdbc.SybConnection.setAutoCommit(SybConnection.java)
at weblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:594)
at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:115)
atweblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.ja
va:135)
atweblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:78
atorg.ici.weeklyflow.dao.SyBaseWeeklyApplicationDAOImpl.removePrivilegedUser(S
yBaseWeeklyApplicationDAOImpl.java:312)
atorg.ici.weeklyflow.ejb.WeeklyFlowSBean.removePrivilegedUser(WeeklyFlowSBean.
java:322)
atorg.ici.weeklyflow.ejb.WeeklyFlowSBean_1tv6ke_EOImpl.removePrivilegedUser(We
eklyFlowSBean_1tv6ke_EOImpl.java:1049)
atorg.ici.weeklyflow.ejb.WeeklyFlowSBean_1tv6ke_EOImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
atweblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
:93)
atweblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
=====================================
I saw other postings concerning this message but those seemed to be in
regards to errors that occurred all the time, does anyone have any ideas?
Thanks,
-Ben DeVore
Tallan, Inc.

Unusual 550 5.7.1 Command Not Allowed being sent from Exchange 2010

Greetings,
I have an Exchange 2010 server that seems to be rejecting some emails from external domains with 550 5.7.1 Command Not Allowed. I've taken a look at the SMTP Receive logs (below) and can't seem to find any reason why the emails are getting rejected. The sequence
immediately prior to the 550 being sent is highlighted in bold.
#Fields: date-time sequence-number local-endpoint remote-endpoint event data context
2014-11-05T08:42:27.545Z 0 192.168.3.5:25 212.82.97.117:53913 +
2014-11-05T08:42:27.545Z 1 192.168.3.5:25 212.82.97.117:53913 * SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders Set Session Permissions
2014-11-05T08:42:27.545Z 2 192.168.3.5:25 212.82.97.117:53913 > 220 SERVER.domain.com Microsoft ESMTP MAIL Service ready at Wed, 5 Nov 2014 03:42:27 -0500
2014-11-05T08:42:27.657Z 3 192.168.3.5:25 212.82.97.117:53913 < EHLO nm34-vm3.bullet.mail.ir2.yahoo.com
2014-11-05T08:42:27.658Z 4 192.168.3.5:25 212.82.97.117:53913 > 250-SERVER.domain.com Hello [212.82.97.117]
2014-11-05T08:42:27.658Z 5 192.168.3.5:25 212.82.97.117:53913 > 250-SIZE
2014-11-05T08:42:27.658Z 6 192.168.3.5:25 212.82.97.117:53913 > 250-PIPELINING
2014-11-05T08:42:27.658Z 7 192.168.3.5:25 212.82.97.117:53913 > 250-DSN
2014-11-05T08:42:27.658Z 8 192.168.3.5:25 212.82.97.117:53913 > 250-ENHANCEDSTATUSCODES
2014-11-05T08:42:27.658Z 9 192.168.3.5:25 212.82.97.117:53913 > 250-STARTTLS
2014-11-05T08:42:27.658Z 10 192.168.3.5:25 212.82.97.117:53913 > 250-X-ANONYMOUSTLS
2014-11-05T08:42:27.658Z 11 192.168.3.5:25 212.82.97.117:53913 > 250-AUTH NTLM
2014-11-05T08:42:27.658Z 12 192.168.3.5:25 212.82.97.117:53913 > 250-X-EXPS GSSAPI NTLM
2014-11-05T08:42:27.658Z 13 192.168.3.5:25 212.82.97.117:53913 > 250-8BITMIME
2014-11-05T08:42:27.658Z 14 192.168.3.5:25 212.82.97.117:53913 > 250-BINARYMIME
2014-11-05T08:42:27.658Z 15 192.168.3.5:25 212.82.97.117:53913 > 250-CHUNKING
2014-11-05T08:42:27.658Z 16 192.168.3.5:25 212.82.97.117:53913 > 250-XEXCH50
2014-11-05T08:42:27.658Z 17 192.168.3.5:25 212.82.97.117:53913 > 250-XRDST
2014-11-05T08:42:27.658Z 18 192.168.3.5:25 212.82.97.117:53913 > 250 XSHADOW
2014-11-05T08:42:27.756Z 19 192.168.3.5:25 212.82.97.117:53913 < STARTTLS
2014-11-05T08:42:27.756Z 20 192.168.3.5:25 212.82.97.117:53913 > 220 2.0.0 SMTP server ready
2014-11-05T08:42:27.756Z 21 192.168.3.5:25 212.82.97.117:53913 * Sending certificate
2014-11-05T08:42:27.756Z 22 192.168.3.5:25 212.82.97.117:53913 * CN=SERVER Certificate subject
2014-11-05T08:42:27.756Z 23 192.168.3.5:25 212.82.97.117:53913 * CN=SERVER Certificate issuer name
2014-11-05T08:42:27.756Z 24 192.168.3.5:25 212.82.97.117:53913 * 3BF7DF215EB42FB14FAE1BF7E4369E06 Certificate serial number
2014-11-05T08:42:27.756Z 25 192.168.3.5:25 212.82.97.117:53913 * 01494AD746353CCE0F198CE83AD4D6A8592C29F5 Certificate thumbprint
2014-11-05T08:42:27.756Z 26 192.168.3.5:25 212.82.97.117:53913 * SERVER;SERVER.domain.com Certificate alternate names
2014-11-05T08:42:28.059Z 27 192.168.3.5:25 212.82.97.117:53913 < EHLO nm34-vm3.bullet.mail.ir2.yahoo.com
2014-11-05T08:42:28.059Z 28 192.168.3.5:25 212.82.97.117:53913 * TlsDomainCapabilities='None'; Status='NoRemoteCertificate'
2014-11-05T08:42:28.060Z 29 192.168.3.5:25 212.82.97.117:53913 > 250-SERVER.domain.com Hello [212.82.97.117]
2014-11-05T08:42:28.060Z 30 192.168.3.5:25 212.82.97.117:53913 > 250-SIZE
2014-11-05T08:42:28.060Z 31 192.168.3.5:25 212.82.97.117:53913 > 250-PIPELINING
2014-11-05T08:42:28.060Z 32 192.168.3.5:25 212.82.97.117:53913 > 250-DSN
2014-11-05T08:42:28.060Z 33 192.168.3.5:25 212.82.97.117:53913 > 250-ENHANCEDSTATUSCODES
2014-11-05T08:42:28.060Z 34 192.168.3.5:25 212.82.97.117:53913 > 250-AUTH NTLM LOGIN
2014-11-05T08:42:28.060Z 35 192.168.3.5:25 212.82.97.117:53913 > 250-X-EXPS GSSAPI NTLM
2014-11-05T08:42:28.060Z 36 192.168.3.5:25 212.82.97.117:53913 > 250-8BITMIME
2014-11-05T08:42:28.060Z 37 192.168.3.5:25 212.82.97.117:53913 > 250-BINARYMIME
2014-11-05T08:42:28.060Z 38 192.168.3.5:25 212.82.97.117:53913 > 250-CHUNKING
2014-11-05T08:42:28.060Z 39 192.168.3.5:25 212.82.97.117:53913 > 250-XEXCH50
2014-11-05T08:42:28.060Z 40 192.168.3.5:25 212.82.97.117:53913 > 250-XRDST
2014-11-05T08:42:28.060Z 41 192.168.3.5:25 212.82.97.117:53913 > 250 XSHADOW
2014-11-05T08:42:28.158Z 42 192.168.3.5:25 212.82.97.117:53913 < MAIL FROM:<[email protected]>
2014-11-05T08:42:28.158Z 43 192.168.3.5:25 212.82.97.117:53913 * 08D11121D08C9A95;2014-11-05T08:42:27.545Z;1 receiving message
2014-11-05T08:42:28.159Z 44 192.168.3.5:25 212.82.97.117:53913 > 250 2.1.0 Sender OK
2014-11-05T08:42:28.364Z 45 192.168.3.5:25 212.82.97.117:53913 < RCPT TO:<[email protected]>
2014-11-05T08:42:28.364Z 46 192.168.3.5:25 212.82.97.117:53913 > 250 2.1.5 Recipient OK
2014-11-05T08:42:28.462Z 47 192.168.3.5:25 212.82.97.117:53913 < DATA
2014-11-05T08:42:29.275Z 48 192.168.3.5:25 212.82.97.117:53913 * Tarpit for '0.00:00:05'
2014-11-05T08:42:34.278Z 49 192.168.3.5:25 212.82.97.117:53913 > 550 5.7.1 Command not allowed
2014-11-05T08:42:34.521Z 50 192.168.3.5:25 212.82.97.117:53913 < RSET
2014-11-05T08:42:34.521Z 51 192.168.3.5:25 212.82.97.117:53913 * Tarpit for '0.00:00:05'
2014-11-05T08:42:39.523Z 52 192.168.3.5:25 212.82.97.117:53913 > 250 2.0.0 Resetting
2014-11-05T08:42:39.621Z 53 192.168.3.5:25 212.82.97.117:53913 < MAIL FROM:<[email protected]>
2014-11-05T08:42:39.621Z 54 192.168.3.5:25 212.82.97.117:53913 * 08D11121D08C9A95;2014-11-05T08:42:27.545Z;2 receiving message
2014-11-05T08:42:39.621Z 55 192.168.3.5:25 212.82.97.117:53913 > 250 2.1.0 Sender OK
2014-11-05T08:42:39.719Z 56 192.168.3.5:25 212.82.97.117:53913 < RCPT TO:<[email protected]>
2014-11-05T08:42:39.719Z 57 192.168.3.5:25 212.82.97.117:53913 > 250 2.1.5 Recipient OK
2014-11-05T08:42:39.817Z 58 192.168.3.5:25 212.82.97.117:53913 < DATA
2014-11-05T08:42:39.838Z 59 192.168.3.5:25 212.82.97.117:53913 * Tarpit for '0.00:00:05'
2014-11-05T08:42:44.837Z 60 192.168.3.5:25 212.82.97.117:53913 > 550 5.7.1 Command not allowed
2014-11-05T08:42:45.078Z 61 192.168.3.5:25 212.82.97.117:53913 < RSET
2014-11-05T08:42:45.078Z 62 192.168.3.5:25 212.82.97.117:53913 * Tarpit for '0.00:00:05'
2014-11-05T08:42:50.079Z 63 192.168.3.5:25 212.82.97.117:53913 > 250 2.0.0 Resetting
2014-11-05T08:42:50.177Z 64 192.168.3.5:25 212.82.97.117:53913 < QUIT
2014-11-05T08:42:50.177Z 65 192.168.3.5:25 212.82.97.117:53913 > 221 2.0.0 Service closing transmission channel
2014-11-05T08:42:50.177Z 66 192.168.3.5:25 212.82.97.117:53913 - Local
I have another entry in my logs fro the same sender coming from the same IP which yields the same results. Strangely enough, there are other entries from the same sender coming from different IPs which are delivered just fine.
The sender has stated that they only get the rejects when replying to emails from my domain, not when he sends fresh emails.
Why would Exchange send the 550 5.7.1 in response to a DATA command when it responds with 354 Start mail input; end with <CRLF>.<CRLF> to other DATA commands from a different server?
Bit of an odd problem, any help would be greatly appreciated.
Thanks,
B. Colt

Thanks for the input Mr. Crowley. I've dumped the Receive Connector configurations, everything seems to be at default values except for logging (I set it to verbose).
RunspaceId : 17f0dc01-c2a9-45ce-812d-5d47688b6650
AuthMechanism : Tls, BasicAuth, BasicAuthRequireTLS
Banner :
BinaryMimeEnabled : True
Bindings : {12.34.56.78:25}
ChunkingEnabled : True
DefaultDomain :
DeliveryStatusNotificationEnabled : True
EightBitMimeEnabled : True
BareLinefeedRejectionEnabled : False
DomainSecureEnabled : False
EnhancedStatusCodesEnabled : True
LongAddressesEnabled : False
OrarEnabled : False
SuppressXAnonymousTls : False
AdvertiseClientSettings : False
Fqdn : mail.MYDOMAIN.com
Comment :
Enabled : True
ConnectionTimeout : 00:10:00
ConnectionInactivityTimeout : 00:05:00
MessageRateLimit : unlimited
MessageRateSource : IPAddress
MaxInboundConnection : 5000
MaxInboundConnectionPerSource : 20
MaxInboundConnectionPercentagePerSource : 2
MaxHeaderSize : 64 KB (65,536 bytes)
MaxHopCount : 60
MaxLocalHopCount : 12
MaxLogonFailures : 3
MaxMessageSize : 100 MB (104,857,600 bytes)
MaxProtocolErrors : 5
MaxRecipientsPerMessage : 200
PermissionGroups : ExchangeUsers, ExchangeServers
PipeliningEnabled : True
ProtocolLoggingLevel : Verbose
RemoteIPRanges : {0.0.0.0-255.255.255.255}
RequireEHLODomain : False
RequireTLS : False
EnableAuthGSSAPI : False
ExtendedProtectionPolicy : None
LiveCredentialEnabled : False
TlsDomainCapabilities : {}
Server : MYSERVER
SizeEnabled : Enabled
TarpitInterval : 00:00:05
MaxAcknowledgementDelay : 00:00:30
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : default MYDOMAIN.com
DistinguishedName : CN=default MYDOMAIN.COM,CN=SMTP Receive Connectors,CN=Protocols,CN=MYSERVER,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=My
Company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN
,DC=local
Identity : SERVER\default MYDOMAIN.COM
Guid : 04d418d8-06f6-4e13-8f3b-439f9c6509b0
ObjectCategory : MYDOMAIN.COM/Configuration/Schema/ms-Exch-Smtp-Receive-Connector
ObjectClass : {top, msExchSmtpReceiveConnector}
WhenChanged : 10/1/2014 3:53:53 PM
WhenCreated : 3/1/2012 2:33:10 PM
WhenChangedUTC : 10/1/2014 7:53:53 PM
WhenCreatedUTC : 3/1/2012 7:33:10 PM
OrganizationId :
OriginatingServer : SERVER.MYDOMAIN.COM
IsValid : True
RunspaceId : 17f0dc01-c2a9-45ce-812d-5d47688b6650
AuthMechanism : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
Banner :
BinaryMimeEnabled : True
Bindings : {:::25, 0.0.0.0:25}
ChunkingEnabled : True
DefaultDomain :
DeliveryStatusNotificationEnabled : True
EightBitMimeEnabled : True
BareLinefeedRejectionEnabled : False
DomainSecureEnabled : False
EnhancedStatusCodesEnabled : True
LongAddressesEnabled : False
OrarEnabled : False
SuppressXAnonymousTls : False
AdvertiseClientSettings : False
Fqdn : SERVER.MYDOMAIN.COM
Comment :
Enabled : True
ConnectionTimeout : 00:10:00
ConnectionInactivityTimeout : 00:05:00
MessageRateLimit : unlimited
MessageRateSource : IPAddress
MaxInboundConnection : 5000
MaxInboundConnectionPerSource : unlimited
MaxInboundConnectionPercentagePerSource : 100
MaxHeaderSize : 64 KB (65,536 bytes)
MaxHopCount : 60
MaxLocalHopCount : 12
MaxLogonFailures : 3
MaxMessageSize : 100 MB (104,857,600 bytes)
MaxProtocolErrors : 5
MaxRecipientsPerMessage : 5000
PermissionGroups : AnonymousUsers, ExchangeUsers, ExchangeServers, ExchangeLegacyServers
PipeliningEnabled : True
ProtocolLoggingLevel : Verbose
RemoteIPRanges : {192.168.1.0(255.255.255.0), ::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
RequireEHLODomain : False
RequireTLS : False
EnableAuthGSSAPI : False
ExtendedProtectionPolicy : None
LiveCredentialEnabled : False
TlsDomainCapabilities : {}
Server : MYSERVER
SizeEnabled : EnabledWithoutValue
TarpitInterval : 00:00:05
MaxAcknowledgementDelay : 00:00:30
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Default SERVER
DistinguishedName : CN=Default SERVER,CN=SMTP Receive Connectors,CN=Protocols,CN=SERVER,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=MY
COMPANY,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MYDOMAIN,DC=l
ocal
Identity : SERVER\Default SERVER
Guid : fc6ab381-1cf9-4edb-bec4-3a2c092cd4e3
ObjectCategory : mydomain/Configuration/Schema/ms-Exch-Smtp-Receive-Connector
ObjectClass : {top, msExchSmtpReceiveConnector}
WhenChanged : 10/1/2014 3:56:23 PM
WhenCreated : 2/6/2012 11:51:58 AM
WhenChangedUTC : 10/1/2014 7:56:23 PM
WhenCreatedUTC : 2/6/2012 4:51:58 PM
OrganizationId :
OriginatingServer : SERVER.mydomain.com
IsValid : True
I really don't want to turn off the tarpitting and expose myself to tons of spam, although I do have anti-spam filters running.
Any thoughts?
Thanks again,
B. Colt
Brian Colt

Remote Server returned '550 5.7.1 Command not allowed'

I have a user that modified a meeting request that was initially sent by her boss. She has rights to her boss' calendar. After modifying the meeting request, she received the following undeliverable. Any idea where to start troubleshooting?
Thanks
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction
may be preventing delivery.<o:p></o:p>
"domain name" gave this error:
Command not allowed <o:p></o:p>

Hi redman71,
Thank you for your question.
We could refer to the following steps to make sure we have grant correct permission for user:
1.Open Outlook 2013.
2.Select Calendar.
3.On the Home tab, select Calendar Permissions.
4.Select the Permissions tab if it is not already selected.
5.Select Add.
6.Type the name of the person you wish to add (e.g, doe, jane). Highlight the name that you want to add.
7.Click the Add button and the user's name will display underlined in the text box to the right.
8.Click Ok.
9.Under Permissions you can set the appropriate permissions for the user (e.g., Reviewer, Author, etc.)
10.Click OK when you are finished selecting the permissions.
Permission Settings:
Owner: Create, read, modify, and delete all items, and create subfolders. Can change the permission levels that other people have for the folder.
Publishing Editor :Create, read, modify, and delete all items and create subfolders.
Editor: Create, read, modify, and delete all items.
Publishing Author: Create and read items, create subfolders, and modify and delete items and files that you create. (Does not apply to delegates.)
Author: Create and read items, and modify and delete items and files that you create.
We could refer to the following link:
https://technet.microsoft.com/en-us/library/dd298062(v=exchg.150).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

550 5.7.1 Command not allowed

We are having issues with several things at the moment in Exchange 2013.
One particular outside email address is returning the following code when replying to an email from within the organization:
<<< 550 5.7.1 Command not allowed 554 5.0.0 Service unavailable
The second issue is related as it pulls a similar code. When one particular user sends an email from her account, or an attached account to a third specific account, she gets the following message:
Diagnostic code = SubmissionProhibited; Reason code = TransferFailed; Status code = 571
< #5.7.1 smtp;550 5.7.1 Command not allowed>
No other user has issues sending to that account.
The third message happened once today, and is sporadic. When another user emails a specific group, she gets returned with: Your message can't be delivered because delivery to this address
is restricted.
We've had some SMTP issues in the past where it would intermittently not send a message, but I don't know if its related, or how to fix it. Any suggestions?

Hello,
If all these users are trying to send to a specific smtp, you need to contact their administrator to whitelist your domain/users. Some times, they need to add permission to receive external emails to their mailbox, distribution list etc.
Regards from ExchangeOnline.in|Windows Administrator Area | Skype:[email protected]

"Set Associations" will not allow Office 2013 Programs / executables to be Associated to a file type

Have Office 2010 and 2013 installed (installing 2010 first, then 2013) and after Windows Update applied Office 2010 SP2 later on, all of my Office file associations (except for Outlook, it points to 2013 as
expected) open up Office 2010 programs. And I'm happy that some programs (Access for example) continue to default to Access 2010.
Ok, so the problem is that for those Office programs that I want to associate to 2013 versions (Excel, PowerPoint & Word as the biggest examples), when I go into "Control Panel\All Control Panel Items\Default
Programs\Set Associations" and pick .doc as an example (I've also tried .xls, .xlsx, .docx) and click on "Change Program", then "More Options", "Look for another app on this PC", and finally navigate to "C:\Program Files\Microsoft
Office 15\root\office15" to double click on excel.exe or winword.exe as appropriate, the selection is ignored (i.e. the icon doesn't change to the Office 2013 style and double clicking on .doc file opens it up in Word 2010).
I do understand there is a "Fix" by either repairing the Office 2013 install or I believe to have seen a Microsoft downloadable fix program, though I do not want to run these as I'm told they will reset
all file associations to Office 2013, and there are still a couple of programs I want to open up in Office 2010, till I get a comfort level with Office 2013. Also realize that once Office 2013 SP1 comes out, it will do the same thing that Office 2010
SP2 did and change the file associations to 2013, whether I want it to or not, hopefully by then I won't have much need for Office 2010.
Also, I find it troubling that the "Set Associations" will not allow me to select specific programs, and I wonder which other File Associations has Microsoft felt appropriate to restrict access.
Look forward to the feedback as it pertains to the above (which I realize is unique to my IT Testing needs).
Thank you,

Hi,
We can try to change the file associate in Registry key:
For all users on this computer, please change associate program of the .doc or file type you would like to under
HKEY_LOCAL_MACHINE\Software\Classes.
For current user account, please change associate program of the .doc or file type you would like to under HKEY_CURRENT_USER\Software\Classes. If there is no such extension, please create new keys for it.
Hope these could be helpful.
Kate Li
TechNet Community Support

Subquery is not allowed within FILTER arguments

In a report I need to show two columns of same type but with values obtained with different criterias.
The criterias are difined in 2 different reports
Report
Month, ColumnA , ColumnB, Number_of_Nights
ColumnA refers to the actual column Member_id= criteria are defined with REPORT1 (where joined date between X and Y and market code=Z)
ColumnB refers to the actual column Member_id=criteria are defined with REPORT2 (where joined date between A and B and market code=C)
I can not use on ColumnA the normal filter and than filter based on results from another request, because it would apply to columnB as well.
I need therefore to use the filter from the "Edit Formula" screen and than filter on a column and select REPORT1 for ColumnA and REPORT2 for ColumnB.
This approach doesn't seem to work because I return :
[nQSError: 10058] A general error has occurred. [nQSError: 22033] Subquery is not allowed within FILTER arguments. (HY000)
How do you manage such reports?
Thanks!!
Edited by: user6185307 on 14.05.2012 06:00
Edited by: user6185307 on 14.05.2012 06:01
Edited by: user6185307 on 14.05.2012 06:02

Try creating the report in one go...
Instead of creating a subquery, and then a subquery using that subquery, and finally a "master" query, create the "master" query first, and within the conditions, create your subquery as you go along.
I'm not sure whether this would work, as I don't currently have access to Discoverer!
Alternatively, subqueries are rarely the most efficient way of processing information, so consider writing a PL/SQL function to do some of the work for you.

Yielding is not allowed within a C or metamethod call

The way I'm developing my plug in is that I'm creating individual modules, testing those modules and then integrating the modules into my plugin. The individual modules work. However, I have a problem when I try to integrate.
I'm using an anonymous function to call a function when a user presses a button. That function calls another lua file (is that a module?) If I place the require statement at the top of the file I receive the Yielding is not allowed within a C or metamethod call error.
However, if I place the require statement within the function that specifically requires accessing the lua file then I don't receive the error. Clearly, I don't understand what's going on. Can anyone explain what is happening here?
Thanks!

Hey Rob,
Thanks for helping me with this. Since this is so new to me, I'm all over the place and I'm having trouble even understanding what my problems are :-)
Anyway, here's where I'm at:
I have a button in sectionsForTopOfDialog. I have changed the action to be action = function() .... end
When I press the button the function is called. The problem is when I call the LrHttp.post function. That's when the yield error is being thrown.

How to set MM02 should not allow to change account and costing view

Hi all guru's
How to set MM02 should not allow to change account and costing view details for orher users expect me,plz help me
thanks
ramesh

Hi Ramesh,
                   Use the Authorization Object: M_MATE_STA     Material Master: Maintenance Statuses
Below are the Views for the MM02, Field STATM
Whichever not wanted to be changed, please dont provide them.
A     Work scheduling
B     Accounting
C     Classification
D     MRP
E     Purchasing
F     Production resources/tools
G     Costing
K     Basic data
L     Storage
P     Forecasting
Q     Quality management
S     Warehouse management
V     Sales
X     Plant stocks
Z     Storage location stocks
Regards,
Yawar Khan
Edited by: 1234_abcd on Jan 10, 2012 8:14 AM

Set Content Copying: Not allowed in Adobe forms

We have developed an adobe form, non interactive form, which has scanned signatures, incorporated as images, of authorized personnel.
But we found that these signatures (images) can be copied by standard copy (Ctr+c).
After a brief study we could find out that we need to set the Content Copying as Not allowed, in document properties, as one of the possible solution, but we are unable to do so.
Could you please suggest a way out as to how do we set Content Copying: Not allowed, in the document properties, of the PDF document.

Thank you for your view.
The XML equivalent of the Adobe form, designed, has a tag <PDF security> which has "copy content" set as 1. The possible solution to my problem is to set the copy content to zero or a value which deactivates the copy content. But even though we set the value to zero, the moment we activate the form it reset itself to 1. Could you please elaborate on this one?

Pdp.p.la command not allowed

Hi!
I get the message: "command not allowed "pdp.p.la". (024021)" when I run this command on the command line:
cr_cli -cmd pdp.p.la -u username -p passwordWhy is that command not allowed? What could I do to run this command?
My Configuration:
Windows Server 2000
Sun N1 SPS 5.2.1
Thanks in advance
Daniel

Hi,
Perhaps you are looking for
pdb.p.laThis command will list all the plans.
For more details, visit the N1 SPS CLI Reference Manual at
http://docs.sun.com/app/docs/doc/819-4444/6n6jjaepv?a=view
To list all of the available commands, type the following:
cr_cli -cmd -lTo list all of the commands that have the same command prefix, use the wildcard character * after the prefix. You might need to escape the * with a backslash (\) or by enclosing it in double quotes. For example, the following command lists all of the hdb commands:
cr_cli -cmd -l "hdb.*"The CLI commands are grouped in the following categories:
cat � Categories
cdb � Component database
cfg � Configuration generator
cmp � Comparison engine
fdb � Folder repository
hdb � Host repository
net � Network operations
pdb � Plan repository
pe � Plan execution
plg � Plug-in repository
rule � Rules for notifications
udb � User repository
util � Miscellaneous utilities

SQL operations are not allowed with no global transaction by default for X

Hi All,
I am getting the above mentioned error.
java.sql.SQLException: SQL operations are not allowed with no global transaction by default for XA drivers. If the XA driver supports performing SQL operations with no global transaction, explicitly allow it by setting "SupportsLocalTransaction" JDBC connection pool property to true. In this case, a
lso remember to complete the local transaction before using the connection again for global transaction, else a XAER_OUTSIDE XAException may result. To complete a local transaction, you can either set auto commit to true or call Connection.commit() or Connection.rollback().
I am developing a web application. I have jsp, servlets, JDBC classes.
I am using DataSource and Connection pools.
I am on WLS 8.1 sp3 and Oracle 10.1.
Part of My Config file looks as follows:
<JDBCConnectionPool DriverName="weblogic.jdbcx.oracle.OracleDataSource" KeepLogicalConnOpenOnRelease="true" KeepXAConnTillTxComplete="false" Name="AUMDataSource" NeedTxCtxOnClose="false" NewXAConnForCommit="false" Password="{3DES}AKRkWgdzXN8WrXSRtSvJ6g==" Properties="user=pibsrmgr;portNumber=1521;SID=pibsrdod;serverName=pibsrdod.dtu.mlam.ml.com" RollbackLocalTxUponConnClose="true" SupportsLocalTransaction="false" Targets="myserver" TestTableName="SQL SELECT 1 FROM DUAL" URL="jdbc:bea:oracle://pibsrdod.dtu.mlam.ml.com:1521" XAEndOnlyOnce="false" />
<JDBCTxDataSource EnableTwoPhaseCommit="true" JNDIName="jdbc/AUMDataSource" Name="AUMDataSource" PoolName="AUMDataSource" Targets="myserver" />
Any help will be appreciated.
Thanks
---Radhe

Hi,
Regarding Transactions , the following link can helpful to you .
Regards,
Prasanna Yalam

Operation Connection.rollback is not allowed during a global transaction.

Hi
I am getting the following exception when i try to deploy my application in the server. Is any body got the same error. please help me to solve this problem.
com.ibm.mm.beans.CMBException: DSRA9350E: Operation Connection.rollback is not allowed during a global transaction.
java.sql.SQLException: DSRA9350E: Operation Connection.rollback is not allowed during a global transaction.
     at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.rollback(WSJdbcConnection.java:2270)
     at com.ibm.mm.sdk.internal.sql.PConnectionICM.rollback(PConnectionICM.java:230)
     at com.ibm.mm.sdk.server.DKDatastoreICM.connect(DKDatastoreICM.java:3273)
     at com.ibm.mm.beans.CMBConnection.connect(CMBConnection.java:1685)
Thanks.

Are you using an XA driver for two-phase commit?
%

Error-local collection types not allowed in SQL statements

TYPE WEEK_NUM_T IS VARRAY(10) OF VARCHAR2(10);
vc_weeknum WEEK_NUM_T;
SELECT DISTINCT to_char(y.week_number_in_year) BULK COLLECT INTO vc_weeknum
    FROM DD_TMP x, TIME y
    WHERE x.DATE_TM = y.ORACLE_DATE;
INSERT INTO TMP_HOLD
    (SELECT *
         FROM TMP
         WHERE DATE_TM IN (SELECT * FROM TABLE(vc_weeknum));It seems like the TABLE() function don't work. What is the workaround?

You haven't provided enough of your code to tell, but you are probably trying to use a pl/sql type instead of a sql type. Please see the reproduction of error, then correction below.
-- reprouction of error:
scott@ORA92> CREATE TABLE tmp_hold AS SELECT * FROM dept WHERE 1 = 2
2 /
Table created.
scott@ORA92> DECLARE
2    TYPE WEEK_NUM_T     IS VARRAY(10) OF VARCHAR2(10);
3    vc_weeknum WEEK_NUM_T;
4 BEGIN
5    SELECT DISTINCT deptno
6    BULK   COLLECT INTO vc_weeknum
7    FROM   emp;
8
9    INSERT INTO TMP_HOLD
10    SELECT *
11    FROM   dept
12    WHERE deptno IN
13            (SELECT * FROM TABLE(vc_weeknum));
14 END;
15 /
         (SELECT * FROM TABLE(vc_weeknum));
ERROR at line 13:
ORA-06550: line 13, column 31:
PLS-00642: local collection types not allowed in SQL statements
ORA-06550: line 13, column 25:
PL/SQL: ORA-22905: cannot access rows from a non-nested table item
ORA-06550: line 9, column 3:
PL/SQL: SQL Statement ignored
-- correction:
scott@ORA92> CREATE OR REPLACE TYPE WEEK_NUM_T AS TABLE OF VARCHAR2(10);
2 /
Type created.
scott@ORA92> DECLARE
2    vc_weeknum WEEK_NUM_T;
3 BEGIN
4    SELECT DISTINCT deptno
5    BULK   COLLECT INTO vc_weeknum
6    FROM   emp;
7
8    INSERT INTO TMP_HOLD
9    SELECT *
10    FROM   dept
11    WHERE deptno IN
12            (SELECT * FROM TABLE (CAST (vc_weeknum AS week_num_t)));
13 END;
14 /
PL/SQL procedure successfully completed.
scott@ORA92> SELECT * FROM tmp_hold
2 /
    DEPTNO DNAME          LOC
        10 ACCOUNTING     NEW YORK
        20 RESEARCH       DALLAS
        30 SALES          CHICAGO
scott@ORA92>

Sybase: SET CHAINED command not allowed within multi-statement transaction

Similar Messages

Maybe you are looking for