D
dbeavon
Guest
I'm seeing a few behaviors that are different when deploying to the remote PASOE production instance. I will try to do some configuration comparisons, but I have a feeling it isn't my fault. I found a KB that indicates there are some types of failures that specifically happen when PASOE isn't running on the same machine as the .Net open client: "...the call will fail if the PASOE instance is not on the same machine" See knowledgebase.progress.com/.../invalid-state-for-read-net-open-client-to-pasoe Can anyone help me understand why PASOE would behave substantially differently when running it locally than when running on a remote machine? I don't think it is simply the difference between the dev and prod license. Thanks, David
Continue reading...
Continue reading...