Difference between revisions of "Publishing Troubleshooting"
Line 121: | Line 121: | ||
</security> | </security> | ||
− | = HTTPS Connections = | + | == HTTPS Connections == |
XLCubed web supports HTTPS connections for all of the above security settings. | XLCubed web supports HTTPS connections for all of the above security settings. |
Revision as of 09:51, 18 April 2011
Contents
[hide]Connection failure
When you click "Connect" in the publishing dialog XLCubed will try to contact your web server.
If you can't connect to the web server, you can try the following
Client configuration
If you use a proxy server to access the internet this can prevent XLCubed connecting correctly
To allow the connection turn on the option to bypass the proxy for local addresses.
Note that you only need to do this is you use a proxy, otherwise there is no need to make this change.
If this fails an administrator can check the following to try to resolve the problem.
Windows Authentication
IIS Settings
Depending on your IIS version, take the following steps:
IIS 5
Right click the XLCubedWeb directory and select "Properties" Select the "Directory Security" tab Ensure that "Integrated Windows authentication" is checked and all others are not.
IIS 6
Select the XLCubedWeb directory and open the "Authentication" section.
Ensure "ASP.NET Impersonation" and "Windows Authentication" are enabled, and others are disabled.
If you do not have these options you must add them from Control Panel -> Programs -> Turn Windows features on or off
web.config Settings
In the bindings section the security should be as follows for all bindings.
<security mode="TransportCredentialOnly"> <transport clientCredentialType="Windows"/> </security>
Basic Authentication
IIS Settings
Depending on your IIS version, take the following steps:
IIS 5
Right click the XLCubedWeb directory and select "Properties" Select the "Directory Security" tab Ensure that "Basic authentication" is checked and all others are not.
IIS 6
Select the XLCubedWeb directory and open the "Authentication" section.
Ensure "ASP.NET Impersonation" and "Basic Authentication" are enabled, and others are disabled.
web.config Settings
In the bindings section the security should be as follows for all bindings.
<security mode="TransportCredentialOnly"> <transport clientCredentialType="Basic"/> </security>
Anonymous Authentication
IIS Settings
Depending on your IIS version, take the following steps:
IIS 5
Right click the XLCubedWeb directory and select "Properties" Select the "Directory Security" tab Ensure that "Enable anonymous access" is checked and all others are not.
IIS 6
Select the XLCubedWeb directory and open the "Authentication" section.
Ensure "ASP.NET Impersonation" and "Anonymous Authentication" are enabled, and others are disabled.
If you do not have these options you must add them from Control Panel -> Programs -> Turn Windows features on or off
web.config Settings
In the bindings section the security should be as follows for all bindings.
<security mode="TransportCredentialOnly"> <transport clientCredentialType="None"/> </security>
HTTPS Connections
XLCubed web supports HTTPS connections for all of the above security settings.
web.config Settings
Change the security mode for all of the bindings to:
<security mode="Transport">
Publishing failure
If you can connect to the web server, but can not publish a file, you can try the following
Validate IIS Config
Navigating to the repository web service on the server will give a detailed error message if there is a problem with the configuration.
For example, navigate to:
http://localhost/xlcubedweb/webservices/RepositoryServer.svc
If everything is configured correctly you will see some sample code about using the service, otherwise a detailed error message will be displayed.
Permissions
Users need write permission to the repository directory in order to be able to publish files.
If this permission is missing often users can connect to the web server, but don't see a "My Reports" folder, and get an error when attempting to publish a file.
To check if this is the problem you can grant Read and Write Access to the Repository directory in the XLCubedWeb site to everyone and retry publishing.
If the publish then succeeds then permissions was the issue, and you can restrict access to the users you wish to be able to publish.