Kbase P110195: .Net application fails to connect to AppServer but does not get any errors, first call to 4GL progra
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
25/10/2005 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge 10.0x
SYMPTOM(s):
ASP.Net application which uses Open Client proxies to talk to the AppServer fails to connect but does not get any errors (connection appears to work)
When first attempt to invoke 4GL method happens a .Net error is returned
The .Net error is 'Specified slot number was invalid'
The application uses several different Open Client proxies in the same program
The Open Client proxies all use the 'StrongNamed & Signed' option
CAUSE:
One of the Open Client proxies was regenerated and the 'StrongNamed & Signed' option was accidentally turned off. Because all the proxies were referenced in the program the Visual Studio.Net IDE, during its build cycle copied the Progress.*.dll files from each proxy to the output directory and regardless which set of Progress.*.dll files were copied in last at least one Open Client proxy had the wrong set of Progress.*.dll files.
FIX:
Regenerate the Open Client proxy which was incorrectly generated without the 'StrongNamed & Signed' option