CSRF Violation is detected

Hi
I am facing the issue in management console when I have run the Job: "The request is coming from un-authorized source!(BODI-3016849)"
Versions:
DS: 4.1 SP2
Any one knows Please give your inputs

Hi Suresh,
Please refer the below KBA regarding your issue.
1960488 - Error: You receive "CSRF Violation is detected. The request is coming from un-authorized source!(BODI-3016849)" when you click Users and Groups in SAP Data Services
https://service.sap.com/sap/support/notes/1960488
Thanks,
Daya

Similar Messages

A Cross-site request forgery (CSRF) has been detected. Task=com.bea.consol

On the BEA admin console and tryiing to install an ear from a remote location that is fairly large, we're seeing the following error:
<A Cross-site request forgery (CSRF) has been detected. Task=com.bea.console.actions.app.install.Flow.uploadApp address=*.**.***.*** user=weblogic>
The address contains an actual IP address.
If we copy the same ear over to the server box and install, it works fine. If we remove some jars from the ear to decrease its size, it works fine.
We are running a Weblogic 10.3.5 server. The ear that fails is 276MB. We can successfully install a 246MB ear. So the problem must arise somewhere between 250MB and 275MB.
Has anyone seen this? Is this a known limitation for installing remote ear's?
Any information is appreciated.

A phase listener comes to mind. Check out this useful article:
http://balusc.blogspot.com/2006/09/debug-jsf-lifecycle.html

802.1X Port Based Authentication - IP Phone- MDA - Port Security Violation

I have configured 802.1X authentication on selected ports of a Cisco Catalyst 2960S with Micorsoft NPS Radius authentication on a test LAN. I have tested the authentication with a windows XP laptop, a windows 7 laptop with 802.1X, eap-tls authentication and a Mitel 5330 IP Phone using EAP-MD5 aithentication. All the above devices work with with the MS NPS server. However in MDA mode when the 802.1x compliant windows 7 laptop is connected to the already authenticated Mitel IP Phone, the port experiences a security violation and the goes into error sdisable mode.
Feb 4 19:16:16.571: %AUTHMGR-5-START: Starting 'dot1x' for client (24b6.fdfa.749b) on Interface Gi1/0/1 AuditSessionID AC10A0FE0000002F000D3CED
Feb 4 19:16:16.645: %DOT1X-5-SUCCESS: Authentication successful for client (24b6.fdfa.749b) on Interface Gi1/0/1 AuditSessionID AC10A0FE0000002F000D3CED
Feb 4 19:16:16.645: %PM-4-ERR_DISABLE: security-violation error detected on Gi1/0/1, putting Gi1/0/1 in err-disable state
Feb 4 19:16:17.651: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to down
Feb 4 19:16:18.658: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down
If the port config is changed to "authentication host-mode multi-auth", and the laptop is connected to the phone the port does not experience the security violation but the 802.1x authentication for the laptop fails.
The ports GI1/0./1 & Gi1/02 are configured thus:
interface GigabitEthernet1/0/1
switchport mode access
switchport voice vlan 20
authentication event fail action authorize vlan 4
authentication event no-response action authorize vlan 4
authentication event server alive action reinitialize
authentication host-mode multi-domain
authentication order dot1x mab
authentication priority dot1x mab
authentication port-control auto
mab
mls qos trust cos
dot1x pae authenticator
spanning-tree portfast
sh ver
Switch Ports Model SW Version SW Image
* 1 52 WS-C2960S-48FPS-L 15.2(1)E1 C2960S-UNIVERSALK9-M
Full config attached. Assistance will be grately appreciated.
Donfrico

I am currently trying to get 802.1x port authentication working on a Cat3550 against Win2003 IAS but the IAS log shows a invalid message-authenticator error. The 3550 just shows failed. When I authenticate against Cisco ACS (by simply changing the radius-server) it works perfectly.
However, I am successfully using IAS to authenticate WPA users on AP1210s so RADIUS appears to be OK working OK.
Are there special attributes that need to be configured on the switch or IAS?

802.1X Port Based Authentication Security Violation

I have configured 802.1X authentication on selected ports of a Cisco Catalyst 2960S with Micorsoft NPS Radius authentication on a test LAN. I have tested the authentication with a windows XP laptop, a windows 7 laptop with 802.1X, eap-tls authentication and a Mitel 5330 IP Phone using EAP-MD5 aithentication. All the above devices work with with the MS NPS server. However in MDA mode when the 802.1x compliant windows 7 laptop is connected to the already authenticated Mitel IP Phone, the port experiences a security violation and the goes into error sdisable mode.
Feb 4 19:16:16.571: %AUTHMGR-5-START: Starting 'dot1x' for client (24b6.fdfa.749b) on Interface Gi1/0/1 AuditSessionID AC10A0FE0000002F000D3CED
Feb 4 19:16:16.645: %DOT1X-5-SUCCESS: Authentication successful for client (24b6.fdfa.749b) on Interface Gi1/0/1 AuditSessionID AC10A0FE0000002F000D3CED
Feb 4 19:16:16.645: %PM-4-ERR_DISABLE: security-violation error detected on Gi1/0/1, putting Gi1/0/1 in err-disable state
Feb 4 19:16:17.651: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to down
Feb 4 19:16:18.658: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down
If the port config is changed to "authentication host-mode multi-auth", and the laptop is connected to the phone the port does not experience the security violation but the 802.1x authentication for the laptop fails.
The ports GI1/0./1 & Gi1/02 are configured thus:
interface GigabitEthernet1/0/1
switchport mode access
switchport voice vlan 20
authentication event fail action authorize vlan 4
authentication event no-response action authorize vlan 4
authentication event server alive action reinitialize
authentication host-mode multi-domain
authentication order dot1x mab
authentication priority dot1x mab
authentication port-control auto
mab
mls qos trust cos
dot1x pae authenticator
spanning-tree portfast
sh ver
Switch Ports Model SW Version SW Image
* 1 52 WS-C2960S-48FPS-L 15.2(1)E1 C2960S-UNIVERSALK9-M
Full config attached. Assistance will be grately appreciated.
Donfrico

I believe , you need to configure re-authentication on this switch port:
! Enable re-authentication
authentication periodic
! Enable re-authentication via RADIUS Session-Timeout
authentication timer reauthenticate server

Problem since upgrade to 2.0 "Error: Session state protection violation"

I've upgraded to 2.0. Everything fine except one particular page when I submit it I get "Error: Session state protection violation". I have read up about session state protection, and it is turned off in my application. There are no items, pages or URLs that have any session state protection. There is nothing particularly different about this screen when compared to other screens that work. What can be causing this?
Steve

Steve - Thanks for putting that test case out there. This is an odd bug. It happens when you apply the read-only attribute to a "Display as Text (does not save state)" item. Normally, these items are not HTML input items on the page (you see only the value rendered). However, because of a bug, applying the read-only attribute causes an INPUT item to be created. This leads to the problem that you saw -- when an item that should never be POSTed because it is: a) an application item, b) a page item that has the Session State Protection attribute "Restricted - May not be set from browser", or c) a page item of display type "Display as Text (does not save state)", is POSTed, the Session State Protection violation is detected and reported. These checks are performed whether the Session State Protection feature is enabled for the application or not. The reason for that is that checking for cases(a) and (c) is always legitimate and checking for case (b) is always necessary because the Restricted attribute for page items of qualifying display types is always in effect.
So the workaround in your case is not to use the read-only attribute for the display-only items. They are read-only anyway.
Thanks again for pointing this out.
Scott

Security-violation error in 3750

We Have a strange behavior with the computer of a user who connects with his laptop to the network through port replicator or docking station,Where we have a acs.When he goes to another place of the company in another City, Where we have other acs, he connects without port replicator directly to network,It works well. But when the laptop returns does not have
network and the following message of error in switch appears:
May 16 07:51:23: %DOT1X-5-SECURITY_VIOLATION: Security violation on interface FastEthernet1/0/27, New MAC address 00c0.f200.53f0 is seen on the interface in Single Host mode
May 16 07:51:23: %PM-4-ERR_DISABLE: security-violation error detected on Fa1/0/27, putting Fa1/0/27 in err-disable state
May 16 07:51:24: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/27, changed state to down
May 16 07:51:25: %LINK-3-UPDOWN: Interface FastEthernet1/0/27, changed state to down
I execute the commando "shutdown" and "not shutdown" in the interface of switch, and soon the commando: "dot1x port-control auto" and soon "not dot1x port-control auto". laptop make authentication and begins to work well.
What think you about What this occurring?

Hi,
Is there any port security being set on the switch?
are you able to paste your config file here?
thanks,
rgds,
ken L

OptimisticVerificationException

I am getting the following error:
kodo.util.OptimisticVerificationException: An optimistic lock violation
was detected when flushing object
"com.xyz.packagemerge.model.Package@6bfc1ff8" with id
"com.xyz.packagemerge.model.Package-57368" to the data store. This
indicates that the object was concurrently modified in another transaction.
FailedObject:com.xyz.packagemerge.model.Package@6bfc1ff8
     at
kodo.jdbc.runtime.PreparedStatementManager.checkUpdate(PreparedStatementManager.java(Compiled
Code))
     at
kodo.jdbc.runtime.PreparedStatementManager.flushInternal(PreparedStatementManager.java(Compiled
Code))
     at
kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java(Inlined
Compiled Code))
     at
kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java(Compiled
Code))
I have tried every thing I can find, and the only solution that has worked
was to remove the jdbc-version-ind from the mapping files. This solution
is undesirable in addition to being unacceptable due to the performance
degradation it causes (10 - 50 times increase in processing time).
The application is single threaded, there is only 1 persistence manager,
and there are no other transactions (or even connnections) to the database.
Relevant configuration info:
[Thread-20] kodo.jdbc.JDBC - Using dictionary class
"kodo.jdbc.sql.OracleDictionary" (Oracle Oracle9i Enterprise Edition
Release 9.2.0.5.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production ,Oracle JDBC driver 9.0.1.0.0).
javax.jdo.option.ConnectionDriverName=oracle.jdbc.driver.OracleDriver
javax.jdo.PersistenceManagerFactoryClass=kodo.jdbc.runtime.JDBCPersistenceManagerFactory
javax.jdo.option.Multithreaded=false
javax.jdo.option.NontransactionalWrite=false
javax.jdo.option.NontransactionalRead=false
javax.jdo.option.RetainValues=false
javax.jdo.option.RestoreValues=false
kodo.ConnectionFactoryProperties=(MaxActive\=5)
kodo.jdbc.DBDictionary=oracle(StoreCharsAsNumbers\=false, BatchLimit\=0)
kodo.DataCache=true(CacheSize\=5000)
kodo.RemoteCommitProvider=sjvm
kodo.QueryCache=true(CacheSize\=1000)
It appears that it could be a problem with the state-image not recognizing
the difference between null and empty string, or an inconsistency in the
data cache.

Clint-
Can you disable batch updates and see if it works? There are known
problems with some versions of the Oracle JDBC driver (including the one
you are using) that prevents incorrect update counts from being returned
from batch updates; the most common symptom of this problem is an
incorrect OptimisticVerificationException being thrown.
You should also try using version 9.0.1.0.0 of the Oracle driver,
which is known to work much better for batch updating.
Finally, what version of Kodo are you using? Recent versions (3.1.4)
should have detected this problem and issued a warning.
In article <[email protected]>, Clint LeGros wrote:
I am getting the following error:
kodo.util.OptimisticVerificationException: An optimistic lock violation
was detected when flushing object
"com.xyz.packagemerge.model.Package@6bfc1ff8" with id
"com.xyz.packagemerge.model.Package-57368" to the data store. This
indicates that the object was concurrently modified in another transaction.
FailedObject:com.xyz.packagemerge.model.Package@6bfc1ff8
     at
kodo.jdbc.runtime.PreparedStatementManager.checkUpdate(PreparedStatementManager.java(Compiled
Code))
     at
kodo.jdbc.runtime.PreparedStatementManager.flushInternal(PreparedStatementManager.java(Compiled
Code))
     at
kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java(Inlined
Compiled Code))
     at
kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java(Compiled
Code))
I have tried every thing I can find, and the only solution that has worked
was to remove the jdbc-version-ind from the mapping files. This solution
is undesirable in addition to being unacceptable due to the performance
degradation it causes (10 - 50 times increase in processing time).
The application is single threaded, there is only 1 persistence manager,
and there are no other transactions (or even connnections) to the database.
Relevant configuration info:
[Thread-20] kodo.jdbc.JDBC - Using dictionary class
"kodo.jdbc.sql.OracleDictionary" (Oracle Oracle9i Enterprise Edition
Release 9.2.0.5.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production ,Oracle JDBC driver 9.0.1.0.0).
javax.jdo.option.ConnectionDriverName=oracle.jdbc.driver.OracleDriver
javax.jdo.PersistenceManagerFactoryClass=kodo.jdbc.runtime.JDBCPersistenceManagerFactory
javax.jdo.option.Multithreaded=false
javax.jdo.option.NontransactionalWrite=false
javax.jdo.option.NontransactionalRead=false
javax.jdo.option.RetainValues=false
javax.jdo.option.RestoreValues=false
kodo.ConnectionFactoryProperties=(MaxActive\=5)
kodo.jdbc.DBDictionary=oracle(StoreCharsAsNumbers\=false, BatchLimit\=0)
kodo.DataCache=true(CacheSize\=5000)
kodo.RemoteCommitProvider=sjvm
kodo.QueryCache=true(CacheSize\=1000)
It appears that it could be a problem with the state-image not recognizing
the difference between null and empty string, or an inconsistency in the
data cache.--
Marc Prud'hommeaux
SolarMetric Inc.

Error 1097 after calling dll function which allocates memory inside

Hello!
When a call one my functions in my dll from LabView, i get an error 1097. My function takes a few arguments and then allocates some memory for measurement.
It's not returning any pointers to that memory area, it is just allocates that memory for itself. I don't know what could be the problem, probably i am missing something.
Could you help please?
Best regards,
Tamas
Solved!
Go to Solution.

Are you sure that the allocate function is the problem?
Error 1097 simply means something inside the external code wrote into memory locations that it was not meant to write. That is usually because of output buffer parameters that are not allocated (large enough) in LabVIEW when passed to the external code fucntion, so the function assuming it received a buffer of a certain size happily writes into that buffer but overwriting other information it should not have.
But that is by far not the only possibility to cause this error. A simple bug in the external code can cause the same problem when a pointer goes astray or such. The fact that you used that library elsewhere already without seeing any problem is unfortunately no guarantee that the function is not buggy. The LabVIEW exeception handling around the Call Library Node has gotten rather picky and can detect violations that do not have to cause visible problems at all. But the violations it detects are real violations so just silencing them is not a good idea, as they could cause all kinds of problems including overwriting vital data structures in your program that either cause a crash later on or simply wrong results in other parts of your program. Especially the last one is a total bummer to debug.
Without seeing much more of your code it is basically impossible to point out where the problem could lie. The particular Allocate function doesn't look like there is much that could be done wrong, but I would assume that you call several other functions too somewhere, which could cause the problem. If you can absolutely positively say that you never ever call any library function with a to short (or unallocated) buffer parameter, then you will have to take it up with the manufacturer of your lib, as it would seem very likely that there is some problem in there.
Also you pass a handle to the library function but your Allocate function does not have this as a parameter! Where does this handle come from? Are you sure you have allocated and prepared it properly before calling this function? A handle is quite often a pointer, although usually a so called opaque pointer meaning the user of the library does not and should not know anything about the structure this pointer points to. It is only known internal to the library.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Pessimistic lock exception in a clustered environment

Hello,
i am using distributed Cache(DataCache) in a Cluster environment
(Weblogic 7.0 cluster).
I got one AdminServer and two ManagedServer running on the same machine.
The problem occurs when i am using optimistic locking. It seems to be that
the cache is not beeing synchronized, when i am successivly persisting
objects and therfore get optimistic lock exceptions.
When i am using pessimistic locking there is no problem.
Waht could be the reason for this, maybe the case the all instances
running on the same machine?
My properties for the cache are the following:
com.solarmetric.kodo.DataCacheClass=de.d2vodafone.webe.common.security.
authorization.jdo.Cache (Cache is a subclass of UDPCache)
com.solarmetric.kodo.DataCacheProperties=UseMulticast=true
MulticastGroup=224.0.0.123 (is unique in my environment)
In the log of my server i got the following messages:
ignoring update from localhost
####<12.02.2003 13:25:11 CET> <Error> <EJB> <pc120514> <ManagedServer2>
<ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'> <kernel
identity> <> <010026> <Exception during commit of transaction
4:b57355e6636065c2: javax.jdo.JDOUserException: Errors were detected when
flushing to the data store. If using optimistic transactions, this could
indicate that lock violations were detected. The "getNestedExceptions"
method of this Exception will return the specific errors.
NestedThrowables:
javax.jdo.JDOUserException:
An instance was concurrently modified in another transaction (optimistic
lock #: 3).
FailedObject:de.webe.common.security.authorization.DomainImpl-5
     at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:551)
     at
com.solarmetric.kodo.ee.EEPersistenceManager.beforeCompletion(EEPersistenceManager.java:192)
     at
weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:540)
     at
weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:92)
     at
weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1044)
     at
weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1581)
     at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:237)
     at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:208)
     at
weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:278)
     at
de.webe.common.security.authorization.jdo.AuthorizationServiceBean_8zrrq4_EOImpl.createUser(AuthorizationServiceBean_8zrrq4_EOImpl.java:170)
     at
de.webe.common.security.authorization.jdo.AuthorizationServiceBean_8zrrq4_EOImpl_WLSkel.invoke(Unknown
Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
     at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:114)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
     at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:785)
     at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
     at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
NestedThrowablesStackTrace:
javax.jdo.JDOUserException: An instance was concurrently modified in
another transaction (optimistic lock #: 3).
FailedObject:de.d2vodafone.webe.common.security.authorization.DomainImpl-5
     at
com.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping$1.afterUpdate(ClassMapping.java:611)
     at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executePreparedStatementNonBatch(SQLExecutionManagerImpl.java:563)
     at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executePreparedStatement(SQLExecutionManagerImpl.java:512)
     at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeInternal(SQLExecutionManagerImpl.java:406)
     at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.flush(SQLExecutionManagerImpl.java:273)
     at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:421)
     at
com.solarmetric.kodo.runtime.datacache.DataCacheStoreManager.flush(DataCacheStoreManager.java:296)
     at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:549)
     at
com.solarmetric.kodo.ee.EEPersistenceManager.beforeCompletion(EEPersistenceManager.java:192)
     at
weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:540)
     at
weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:92)
     at
weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1044)
     at
weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1581)
     at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:237)
     at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:208)
     at
weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:278)
     at
de.d2vodafone.webe.common.security.authorization.jdo.AuthorizationServiceBean_8zrrq4_EOImpl.createUser(AuthorizationServiceBean_8zrrq4_EOImpl.java:170)
     at
de.d2vodafone.webe.common.security.authorization.jdo.AuthorizationServiceBean_8zrrq4_EOImpl_WLSkel.invoke(Unknown
Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
     at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:114)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
     at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:785)
     at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
     at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Unexpected exception in
beforeCompletion: sync=com.solarmetric.kodo.ee.EEPersistenceManager@472ddf
Errors were detected when flushing to the data store. If using optimistic
transactions, this could indicate that lock violations were detected. The
"getNestedExceptions" method of this Exception will return the specific
errors. - with nested exception:
[javax.jdo.JDOUserException: Errors were detected when flushing to the
data store. If using optimistic transactions, this could indicate that
lock violations were detected. The "getNestedExceptions" method of this
Exception will return the specific errors.
NestedThrowables:
javax.jdo.JDOUserException: An instance was concurrently modified in
another transaction (optimistic lock #: 3).
FailedObject:de.d2vodafone.webe.common.security.authorization.DomainImpl-5]
     at
weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1561)
     at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:284)
     at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:208)
     at
weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:278)
     at
de.webe.common.security.authorization.jdo.AuthorizationServiceBean_8zrrq4_EOImpl.createUser(AuthorizationServiceBean_8zrrq4_EOImpl.java:170)
     at
de.webe.common.security.authorization.jdo.AuthorizationServiceBean_8zrrq4_EOImpl_WLSkel.invoke(Unknown
Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
     at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:114)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
     at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:785)
     at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
     at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
Thanks for your help
Best Regards
Orhan Keskin

Orhan-
Is this consistently reproducable, or a rare or one-time occurance? If
the former, it may be a configuration issue, and we will investigatge
along that path.
If it is a rare or one-time occurance, keep in mind that data cache
synchronization does not guarantee that you will be able to avoid
optimistic locking exceptions. Whenever using optimistic locking, you
always need to assume that someday, someone is going to violate that
lock, unless you place some sort of synchronization atop all the
database access (e.g., an EJB). It makes any application much more error
prone (especially since an OL exception is a RuntimeException, and
frequently people forget that it always needs to be checked for).
Anyway, if you provide us with some more details, we will be able to
investigate further.
In article <[email protected]>, Orhan Keskin wrote:
Hello,
i am using distributed Cache(DataCache) in a Cluster environment
(Weblogic 7.0 cluster).
I got one AdminServer and two ManagedServer running on the same machine.
The problem occurs when i am using optimistic locking. It seems to be that
the cache is not beeing synchronized, when i am successivly persisting
objects and therfore get optimistic lock exceptions.
When i am using pessimistic locking there is no problem.
Waht could be the reason for this, maybe the case the all instances
running on the same machine?
My properties for the cache are the following:
com.solarmetric.kodo.DataCacheClass=de.d2vodafone.webe.common.security.
authorization.jdo.Cache (Cache is a subclass of UDPCache)
com.solarmetric.kodo.DataCacheProperties=UseMulticast=true
MulticastGroup=224.0.0.123 (is unique in my environment)
In the log of my server i got the following messages:
ignoring update from localhost
####<12.02.2003 13:25:11 CET> <Error> <EJB> <pc120514> <ManagedServer2>
<ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'> <kernel
identity> <> <010026> <Exception during commit of transaction
4:b57355e6636065c2: javax.jdo.JDOUserException: Errors were detected when
flushing to the data store. If using optimistic transactions, this could
indicate that lock violations were detected. The "getNestedExceptions"
method of this Exception will return the specific errors.
NestedThrowables:
javax.jdo.JDOUserException:
An instance was concurrently modified in another transaction (optimistic
lock #: 3).
FailedObject:de.webe.common.security.authorization.DomainImpl-5
     at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:551)
     at
com.solarmetric.kodo.ee.EEPersistenceManager.beforeCompletion(EEPersistenceManager.java:192)
     at
weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:540)
     at
weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:92)
     at
weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1044)
     at
weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1581)
     at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:237)
     at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:208)
     at
weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:278)
     at
de.webe.common.security.authorization.jdo.AuthorizationServiceBean_8zrrq4_EOImpl.createUser(AuthorizationServiceBean_8zrrq4_EOImpl.java:170)
     at
de.webe.common.security.authorization.jdo.AuthorizationServiceBean_8zrrq4_EOImpl_WLSkel.invoke(Unknown
Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
     at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:114)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
     at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:785)
     at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
     at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
NestedThrowablesStackTrace:
javax.jdo.JDOUserException: An instance was concurrently modified in
another transaction (optimistic lock #: 3).
FailedObject:de.d2vodafone.webe.common.security.authorization.DomainImpl-5
     at
com.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping$1.afterUpdate(ClassMapping.java:611)
     at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executePreparedStatementNonBatch(SQLExecutionManagerImpl.java:563)
     at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executePreparedStatement(SQLExecutionManagerImpl.java:512)
     at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeInternal(SQLExecutionManagerImpl.java:406)
     at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.flush(SQLExecutionManagerImpl.java:273)
     at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:421)
     at
com.solarmetric.kodo.runtime.datacache.DataCacheStoreManager.flush(DataCacheStoreManager.java:296)
     at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:549)
     at
com.solarmetric.kodo.ee.EEPersistenceManager.beforeCompletion(EEPersistenceManager.java:192)
     at
weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:540)
     at
weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:92)
     at
weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1044)
     at
weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1581)
     at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:237)
     at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:208)
     at
weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:278)
     at
de.d2vodafone.webe.common.security.authorization.jdo.AuthorizationServiceBean_8zrrq4_EOImpl.createUser(AuthorizationServiceBean_8zrrq4_EOImpl.java:170)
     at
de.d2vodafone.webe.common.security.authorization.jdo.AuthorizationServiceBean_8zrrq4_EOImpl_WLSkel.invoke(Unknown
Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
     at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:114)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
     at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:785)
     at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
     at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Unexpected exception in
beforeCompletion: sync=com.solarmetric.kodo.ee.EEPersistenceManager@472ddf
Errors were detected when flushing to the data store. If using optimistic
transactions, this could indicate that lock violations were detected. The
"getNestedExceptions" method of this Exception will return the specific
errors. - with nested exception:
[javax.jdo.JDOUserException: Errors were detected when flushing to the
data store. If using optimistic transactions, this could indicate that
lock violations were detected. The "getNestedExceptions" method of this
Exception will return the specific errors.
NestedThrowables:
javax.jdo.JDOUserException: An instance was concurrently modified in
another transaction (optimistic lock #: 3).
FailedObject:de.d2vodafone.webe.common.security.authorization.DomainImpl-5]
     at
weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1561)
     at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:284)
     at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:208)
     at
weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:278)
     at
de.webe.common.security.authorization.jdo.AuthorizationServiceBean_8zrrq4_EOImpl.createUser(AuthorizationServiceBean_8zrrq4_EOImpl.java:170)
     at
de.webe.common.security.authorization.jdo.AuthorizationServiceBean_8zrrq4_EOImpl_WLSkel.invoke(Unknown
Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
     at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:114)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
     at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:785)
     at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
     at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
Thanks for your help
Best Regards
Orhan Keskin
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

How to prevent SQLException with MS SQL Server?

Hi,
I have the following problem (just an example): I have a stored procedure in my MS SQL database that does an INSERT into a table. If the record is already in the table, a unique key violation is detected and my procedure does some other things, generates an error code and returns it to the calling Java method.
Problem is now, that even if I catch the error in the procedure and do some processing, after returning to the calling Java method, I receive an SQLExcetion with the original error (duplicate key...).
How can I prevent this? I want the stored procedure to do the complete error processing and return a self-made error code to Java. So, there must be some way to "reset" the error either in the stored procedure or in the JDBC connection.
Any ideas? With Oracle everything works like expected.
Regards,
Juergen

Juergen,
The SQL Server stored procedure implementation is somewhat different from the Oracle one. As you might have noted in Oracle all results (including ResultSets) can only be returned as output parameters from the stored procedure. With SQL Server you can just do a SELECT inside the procedure and you will see a ResultSet in Java (somewhat of an asynchronous call). There are advantages and disadvantages to both approaches.
One of the SQL Server "disadvantages" is the problem you are experiencing: error messages are also generated as they occur and sent to the client (JDBC driver), which transforms them into SQLExceptions. Another SQL Server disadvantage is the fact that output parameters are only available after the driver has parsed and cached or discarded all results.
With Oracle, on the other hand, you can only obtain ResultSets from stored procedures through cursors. This has two disadvantages: first there's an overhead on the server side to maintain the cursor snd seconf you need non-standard JDBC code to obtain the ResultSet.
So the short answer to your question would be that there isn't (as far as I know) any way to avoid the SQLException. However, you can skip it and either get the linked SQLExceptions or call getMoreResults() until you get your custom error message.
Alin.

Port security and 802.1x (ISE)

Hi everyone,
I'm implemmenting ISE in a network with Port Security enabled.
According the book Cisco ISE for BYOD and Secure Unified Access Port-security is not compatible with 802.1x.
I want to know what is the affectation of to have Port-security and 802.1x enabled on the same SW Port.
Someone?
Thanks!

Hi Neno,
Thanks for the reply.. As we checked the port is going in error-disable with by phone mac address wherein phone is connected 24/7 and machine connects from phone.
Please find below logs from switch -
Oct 1 09:21:11: %AUTHMGR-5-START: Starting 'dot1x' for client (e804.62eb.b435) on Interface Gi5/30 AuditSessionID AC1232470000E906E5392F07 ======Phone MAC
Oct 1 09:21:12: %AUTHMGR-5-START: Starting 'dot1x' for client (0026.b9eb.28ec) on Interface Gi5/30 AuditSessionID AC1232470000E907E53931BF ======Laptop MAC
Oct 1 09:21:12: %AUTHMGR-5-START: Starting 'dot1x' for client (0026.b9eb.28ec) on Interface Gi5/30 AuditSessionID AC1232470000E908E539329B
Oct 1 09:21:12: %DOT1X-5-SUCCESS: Authentication successful for client (0026.b9eb.28ec) on Interface Gi5/30 AuditSessionID AC1232470000E908E539329B
Oct 1 09:21:12: %AUTHMGR-7-RESULT: Authentication result 'success' from 'dot1x' for client (0026.b9eb.28ec) on Interface Gi5/30 AuditSessionID AC1232470000E908E539329B
Oct 1 09:21:12: %EPM-6-POLICY_REQ: IP 0.0.0.0| MAC 0026.b9eb.28ec| AuditSessionID AC1232470000E908E539329B| AUTHTYPEDOT1X| EVENT APPLY
Oct 1 09:21:12: %EPM-6-IPEVENT: IP 0.0.0.0| MAC 0026.b9eb.28ec| AuditSessionID AC1232470000E908E539329B| AUTHTYPE DOT1X| EVENT IP-WAIT
Oct 1 09:21:13: %AUTHMGR-5-SECURITY_VIOLATION: Security violation on the interface GigabitEthernet5/30, new MAC address (e804.62eb.b435) is seen.AuditSessionID Unassigned
Oct 1 09:21:13: %PM-4-ERR_DISABLE: security-violation error detected on Gi5/30, putting Gi5/30 in err-disable state
Oct 1 09:21:13: %AUTHMGR-5-START: Starting 'dot1x' for client (e804.62eb.b435) on Interface Gi5/30 AuditSessionID AC1232470000E909E53935F3
Oct 1 09:21:13: %EPM-6-POLICY_REQ: IP 0.0.0.0| MAC 0026.b9eb.28ec| AuditSessionID AC1232470000E908E539329B| AUTHTYPEDOT1X| EVENT REMOVE
Oct 1 09:21:13: %PM-4-ERR_DISABLE: STANDBY:security-violation error detected on Gi5/30, putting Gi5/30 in err-disable state
Can you guide us how to fix this one
Regards
Pranav

Risk Analysis not highlighting SODs for critical transactions

Hi,
I am currently experiencing a problem when running risk analysis for critical transactions.
SOD conflicts are not always being detected for critical transactions. This is happening both in role expert while creating a role and during role simulation in CC. For example risk BSSC, SU01 does not produce a violation when added to a role, but SOY1 does.
It seems to be happening consistently. If a transaction in risk BSSC has a permission object associated with it in the ruleset, a violation(at tcode or object level) is not detected by the risk analysis even when this authorisation object is maintained with the same value as in the rule set. If the transaction has no permission objects specified in the ruleset, then a violation is detected at tcode level analysis.
These transactions are standard transactions in the ruleset and have not been changed in any way. I have checked the rules and there are critical action rules for both transactions.
Has anybody experienced similiar problems?

Hi..
Check the note # SAP Note 1121978
SAP Note 1121978 - Recommended settings to improve peformance risk analysis.
Check for the following...
CONFIGTOOL>SERVER>MANAGERS>THREADMANAGER
ChangeThreadCountStep =50
InitialThreadCount= 100
MaxThreadCount =200
MinThreadCount =50
Regards
Gangadhar

Kodo.util.UnsupportedException: null

Hello,
Now I'm getting further. I was able to persist my objects!
However, I have an error regarding NamedQuery.
Here is the error:
Exception in thread "main" <3|true|4.0.0EA3>
kodo.util.UnsupportedException: null
     at
kodo.query.ExpressionStoreQuery.executeUpdate(ExpressionStoreQuery.java:232)
     at
kodo.query.ExpressionStoreQuery$DataStoreExecutor.executeUpdate(ExpressionStoreQuery.java:588)
     at
kodo.query.ExpressionStoreQuery$DataStoreExecutor.executeUpdate(ExpressionStoreQuery.java:598)
     at kodo.query.QueryImpl.update(QueryImpl.java:1223)
     at kodo.query.QueryImpl.execute(QueryImpl.java:950)
     at kodo.query.QueryImpl.updateAll(QueryImpl.java:1005)
     at kodo.query.DelegatingQuery.updateAll(DelegatingQuery.java:812)
     at kodo.persistence.QueryImpl.executeUpdate(QueryImpl.java:300)
     at com.dalitest.ClientsDAO.updateClient(ClientsDAO.java:35)
The error is cryptic as well.
It happens for this code:
public int updateClient(EntityManager em, Client c)
Query q = em.createNamedQuery("UpdateClient");
//q.setParameter("newName", c.getName());
q.setParameter("cId", c.getId());
return q.executeUpdate();
And for my Client class I have (snipped):
@NamedQueries( {
@NamedQuery(name = "UpdateClient", queryString = "UPDATE Client c SET
c.name=:newName WHERE c.id=:cId"),
@NamedQuery(name = "DeleteClient", queryString = "DELETE from Client c
WHERE c.id=:cId") })
@Entity(access = AccessType.PROPERTY)
@Table(name = "DALI_CLIENTS")
public class Client {...}
In case I do uncomment q.setParameter("newName", c.getName());
The following exception is thrown:
Exception in thread "main" <4|false|4.0.0EA3>
kodo.persistence.ArgumentException: More parameters were passed to
execute() than were declared: {1} parameters were specific for query
execution, but only {0} parameters were declared in the query.
     at kodo.query.QueryImpl.assertParameters(QueryImpl.java:1871)
     at kodo.query.QueryImpl.execute(QueryImpl.java:941)
     at kodo.query.QueryImpl.updateAll(QueryImpl.java:1005)
     at kodo.query.DelegatingQuery.updateAll(DelegatingQuery.java:812)
     at kodo.persistence.QueryImpl.executeUpdate(QueryImpl.java:300)
     at com.dalitest.ClientsDAO.updateClient(ClientsDAO.java:35)
Can anyone point me what is wrong with my update query?

Abe White wrote:
Thanks Abe for the information.
How do I have to proceed then with my updates at the moment? Do you have
any suggestions (besides waiting for the next release)?
Update the objects individually, or use SQL. Kodo allows you to access
the JDBC connection:>
http://solarmetric.com/Software/Documentation/4.0.0EA/docs/full/html/ref_guide_dbsetup_sqlconn.html
Thanks for the suggestions. SQL is not an option, since it will defeat the
purpose of the EJB3-persistence.
But can you elaborate more on the "Update the objects individually"
approach.
Let's say I have persistent Java bean Client and I changed some of its
properties (e.g. myClient.setName("New Name");)
How do I persiste it "individually"?
This approach does not work:
EntityTransaction t = em.getTransaction();
t.begin();
List<Client> pClients = new ClientsDAO().getAllClients(em);
for (Client pClient : pClients)
pClient.setName("New Name");
em.persist(pClient);
t.commit();
It throws error on t.commit();
<2|false|4.0.0EA3> kodo.util.OptimisticException: An optimistic lock violation
was detected when flushing object instance
"kodo.synthetic.com.dalitest.ClientKodoSyntheticSubclass-id-3" to the data
store. This indicates that the object was concurrently modified in another
transaction.
FailedObject: kodo.synthetic.com.dalitest.ClientKodoSyntheticSubclass-id-3
     at
kodo.jdbc.kernel.PreparedStatementManager.checkUpdate(PreparedStatementManager.java:358)
     at
kodo.jdbc.kernel.PreparedStatementManager.executeBatch(PreparedStatementManager.java:291)
     at
kodo.jdbc.kernel.PreparedStatementManager.flushInternal(PreparedStatementManager.java:243)
     at
kodo.jdbc.kernel.PreparedStatementManager.flush(PreparedStatementManager.java:206)
     at kodo.jdbc.kernel.UpdateManagerImpl.flush(UpdateManagerImpl.java:217)
     at kodo.jdbc.kernel.UpdateManagerImpl.flush(UpdateManagerImpl.java:94)
     at kodo.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:557)
     at
kodo.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:151)
     at kodo.kernel.BrokerImpl.flush(BrokerImpl.java:2034)
     at kodo.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1893)
     at kodo.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1819)
     at kodo.kernel.LocalManagedRuntime.commit(LocalManagedRuntime.java:67)
     at kodo.kernel.BrokerImpl.commit(BrokerImpl.java:1426)
     at kodo.kernel.DelegatingBroker.commit(DelegatingBroker.java:1145)
     at kodo.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:420)
     at com.dalitest.Test.main(Test.java:55)

Installation Icon Disappears w/out installing w/out error msg

64 bit Windows 7 Home Premium SP1 on an ASUS laptop. First noticed a problem with itunes - saying 'itunes has detected a problem with your audio configuration.'
I checked youtube on IE9, and the video and audio were fine. On Chrome however, youtube gave me a msg about needing to install flash player. Firefox gave me a msg about the plug-in for Shockwave being vulnerable and in need of updating. I never bothered to check any version numbers and simply uninstalled Flash entirely using the Flash Uninstaller I downloaded from Adobe.
Now I have no flash player and, although I can run the Flash Installer, nothing ever happens. If I download the installation executable, and dbl click ite, I get the UAC warning. Clicking OK makes the icon disappear from my desktop without giving me any error message.
I have attempted to install by downloading and installing using safe mode with networking and gotten the same result. I even tried first downloading in normal mode, restarting in safe mode, and installing. The icon still disappears.
I'm not sure what I should be looking for in Event Viewer.
I have run sfc /scannow and no integrity violations were detected
I have run a Quick scan with MS Security Essential, and it was clean. I am currently 7 minutes into a full scan.
UPDATE
I saw that a fellow named Mike M replied to another poster just a few hours ago, and his suggetsion was to provide 2 direct install links - 1 for IE and 1 for the other browsers. The IE install went perfectly, and I can now, once again play youtube videos in IE. I had less success with the other install. Firefox 26 gives me an error box about Shockwave not responding, and I can cancel or continue to see if it responds. Continuing gives me 'An error occurred. Please try again later' It is the same video I successfully watched in IE. Chrome gives me ''The Adobr Flash Player is required for videp playback and provides a link to get the latest Flash Player. Of course, I thought I had just done that.

Having Flash Player up to date is one part of the battle. The other is Shockwave. If you do interactive stuff like Facebook games, or Pogo, you need to have Shockwave up to date too.
I recommend a "full clean install":
Download the following by right clicking and selecting wither "save target as" (IE) or "Save Link As" (Firefox):
Flash Player Uninstaller
Shockwave Player Uninstaller
Flash Player for ActiveX (Internet Explorer)
Flash Player Plug-in (All other browsers)
Shockwave Player 12 FULL Installer (other browsers)
Note: The following isn't a download, It's a link you'll NEED TO visit with IE to get to the Shockwave Player 12 FULL Intsaller (ActiveX for IE)
Save five above files to your Downloads folder. DON'T run anything yet.
Reboot your system completely.
BEFORE opening anything else, go to your Downloads folder and run the Uninstallers.
Go to: C/Windows/System32 and delete the Macromed folder.
Go to: C/Windows/SysWOW64 and delete the Macromed folder.
Open your Registry Editor (Start>Run or press the Windows key + R and type "regedit" [minus the quotes] then click OK).
In the Registry Editor, go to: HKEY_LOCAL_MACHINE/SOFTWARE and delete the Macromedia folder.
Goto: HKEY_CURRENT_USER/Software and delete the other Macromedia folder.
Close the Registry Editor and empty your Recycle BIn.
Run the Flash Player ActiveX installer, the Flash Player (other browsers) installer, and the Shockwave FULL installer downloaded previously.
Then open IE and visit the above link to install the ActiveX FULL shockwave plugin. (Note: it says "11" but it's 12)
You've no doubt noticed I mentioned NOTHING about Chrome in all of this.
That's because Chrome uses its own "proprietary" build of Flash Player, and you CAN'T update or reinstall it here.

Srss-4.2 (EA2): troubles with new firmware

we see some issues with the srss-4.2 EA2 (4.2_49_2009.08.27.18.08) firmware. during operation, we sometimes get this on our switches:
===
Sep 21 09:08:28.686 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet9/21, changed state to down
Sep 21 09:08:28.686 CEST: %PM-SP-4-ERR_DISABLE: psecure-violation error detected on Fa9/21, putting Fa9/21 in err-disable state
Sep 21 09:08:28.686 CEST: %PORT_SECURITY-SP-2-PSECURE_VIOLATION: Security violation occurred, caused by MAC address 0000.0000.0015 on port FastEthernet9/21.
.Sep 21 09:08:28.698 CEST: %LINK-3-UPDOWN: Interface FastEthernet9/21, changed state to down
Sep 21 09:08:28.694 CEST: %LINEPROTO-SP-5-UPDOWN: Line protocol on Interface FastEthernet9/21, changed state to down
Sep 21 09:08:28.698 CEST: %LINK-SP-3-UPDOWN: Interface FastEthernet9/21, changed state to down
===
it does not happen often, but it happens (only with the latest FW).
the switch recognizes some other mac addr (0000.0000.0015, in this case) -- as port security is enabled, the port shuts down.
this happens with (receive) flowcontrol enabled and disabled.
niki

I had the same problem, but it has only hapend one time.
(Running OpenSolaris 2009.06 snv_111b X86, with the EA2 release. )

CSRF Violation is detected

Similar Messages

Maybe you are looking for