Jared,It seems to work now, as I no longer get the error I had above. It now appears that some business objects are not being filled when using the fillByPrimaryKey method.
This is probably because you restared IIS, the Application Pool, or reboot the machine. When you make a configuration change, restart the Application Pool or restart IIS. If you did not restart then the Application Pool just cycled which reset the ES connection.
Any ideas what may be causing this?
This doesn't sound ES related to me. The ONLY way I could see this happening is if your ES connection is talking to a different database or server than when you talk directly. The exact same information is passed over for the query regardless of whether you are using the ES or talking directly. The ES simply communicates between the DAL on the client differently, but if you have the ES side setup with an OracleDataSourceItem with the same connection string, then you will get the same results.
Turn on debugging to see what is being passed to the server. You can use this in ES and direct modes.
Databasics.DataSources("").SetDebugOn("c:\myoutput.html",True)