| Problem |
|
|
Console does not launch - you get a blank screen.
Console starts, but some tabs disappear.
Flex application receives "Send
Failed" error. |
| Server ASP.NET application
is not configured to use .NET 2.0 |
- Open IIS Manager
- Select application's virtual
directory
- Open the properties panel
- Select the ASP.NET tab
- Change the version number to 2.0
|
| ASP.NET application contains invalid
configuration. HTTP requests result in
webserver responses with the 500
status code. |
- Try to open
http://localhost/[virtual directory
name]/weborb.aspx
- If an ASP.NET error is reported, it
should provide pointers for the root
cause (possible causes could be an error
in the configuration file or missing
assembly)
- If 'document not found' is reported,
weborb.aspx must be registered in the
application's web.config (see Step 2 in
"Manual Deployment" in the "Deployment"
tab for details). Alternatively try load
the weborb diagnostics utility at:
http://localhost/[virtual directory
name]/diagnostics.aspx
|
|
ColdFusion installation registered with IIS
creates a handler mapping for the SWF
extension. |
- Open IIS Manager
- Select application's virtual
directory
- Open the properties panel
- Select the Virtual Directory tab
- Click the "Configuration" button in
the Application Settings section
- Open the Mappings tab
- Make sure there is no special
application mapping for the .swf
extension
|
|
| Server responds with error "None of
the handlers were able to handle method invocation
on the service" |
| Server
class is not available in the deployed
assemblies |
Use Management Console's "Services" tab to locate your class
in the Service Browser. If the class does
not show up, make sure the assembly is
deployed in the ASP.NET application.
|
|
| Server responds with error "unable
to find method with name - XXXX" |
| Method
is not public |
Make sure the invoked method has public
access |
| Client
arguments types do not match remote method's
formal argument types. For example, client
sends a complex type object where an integer
is expected. |
Inspect the remote method
arguments using Management Console's TestDrive under the
"Services" tab. Modify the client
application to pass correct argument types. |
|
| Code generation does not work.
Server reports IO errors |
| User account used by ASP.NET does
not have Write permission for the /[app's virtual
directory]/weborbassets/codegen folder. |
ASP.NET with IIS6 uses the "NETWORK
SERVICE" account, otherwise ASPNET user account is
used. Select the /weborbassets/codegen folder from
the virtual directory on the computer where WebORB
is deployed and grant Write permission to the user
account used by ASP.NET.
|
|
| Logging does not work. Log files are
not created, /logs folder is empty |
| User account used by ASP.NET does
not have Write permission for the /[app's virtual
directory]/logs folder. |
ASP.NET with IIS6 uses the "NETWORK
SERVICE" account, otherwise ASPNET user account is
used. Select the /logs folder from the virtual
directory on the computer where WebORB is deployed
and grant Write permission to the user account used
by ASP.NET. |
|
| Deployment through the console does
not work. Server reports "Access denied" errors. |
User account used by ASP.NET does
not have Write permission for the targeted virtual
directory
|
Select the target virtual directory
and grant the "Write" permission to the user account
used by ASP.NET. |
|
| WebORB does not accept license key
from a previous version and switches to the
Development mode |
New major versions of WebORB require
new license keys. If you are a customer and are
covered by the maintenance plan, you will get a free
upgrade.
|
Contact sales and request a new
license key |
|
.
