[et_pb_section fb_built=”1″ admin_label=”section” _builder_version=”3.0.47″][et_pb_row admin_label=”row” _builder_version=”3.0.47″ background_size=”initial” background_position=”top_left” background_repeat=”repeat”][et_pb_column type=”4_4″ _builder_version=”3.0.47″ parallax=”off” parallax_method=”on”][et_pb_text admin_label=”Text” _builder_version=”3.0.47″ background_size=”initial” background_position=”top_left” background_repeat=”repeat”]<\/p>\n
In Windows installations (64-bit) of PITSS.CON, there have been times where a PITSS.CON non-ORACLE exception error, “304500: non ORACLE exception”, appears when you double-click on the Path text box in Module Handling. Most of the time, moving the following dlls:<\/p>\n
<\/p>\n
<\/p>\n
to the %ORACLE_HOME%\\bin directory will fix the problem. However, there are rare occasions when you try to select a module in Module Handling that the error does not get fixed. This is due to the fact that Forms cannot find the PitssFileDialog.dll. There is a known issue where if “Microsoft Visual C++ 2005 Redistributable (x64)” has not been installed on the server, the dll will not work correctly. To fix the problem, you will need to do the following:<\/p>\n
<\/p>\n
The PitssFileDialog.dll should be able to be found and you will be able to load modules into PITSS.CON.<\/p>\n
<\/p>\n
NOTE: If you get this error when you first start PITSS.CON, please read\u00a0https:\/\/pitss.org\/us\/2012\/10\/09\/non-oracle-exception-when-starting-pitsscon\/<\/a> for more information.<\/p>\n <\/p>\n NOTE: This has only been seen in Windows Server 2008 (R2 included).<\/strong><\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":" In Windows installations (64-bit) of PITSS.CON, there have been times where a PITSS.CON non-ORACLE exception error, “304500: non ORACLE exception”, appears when you double-click on the Path text box in Module Handling. Most of the time, moving the following dlls: AutoVol.dll PitssFileDialog.dll pitss_vc.dll statistics.dll to the %ORACLE_HOME%\\bin directory will fix the problem. However, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"In Windows installations (64-bit) of PITSS.CON, there have been times where a PITSS.CON non-ORACLE exception error, \"304500: non ORACLE exception\", appears when you double-click on the Path text box in Module Handling. Most of the time, moving the following dlls:\r\n\r\n \t
\r\n \t