|“HTTP Error 404 - File or Directory not found” appears during StorageZones Controller configuration
||The message typically results from an issue with IIS or ASP.NET. Make sure that the IIS role is enabled on the Windows installation and that the ASP.NET feature is enabled on IIS. For more information, see Prepare your server for ShareFile data.
|“HTTP Error 404.2 – Not Found” appears when browsing localhost on the StorageZones Controller
||The message indicates that ISAPI and CGI restrictions for ASP.NET are not set to Allowed. For more information, see Prepare your server for ShareFile data.
|“HTTP Error 413 – Request entity too large” appears after an upload attempt
||The message can appear on a network trace after a failed upload attempt to a StorageZone and can result from a client certificate setting in IIS. To work around this issue:
- On the StorageZones Controller server, open IIS.
- Navigate to Default Web Site and then open SSL Settings.
- For Client certificates select Ignore.
- Restart the Citrix ShareFile Management Service.
For more information, see http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/7e0d74d3-ca01-4d36-8ac7-6b2ca03fd383.mspx?mfr=true.
|IIS errors occur during StorageZones Controller configuration
||IIS errors typically indicate that ASP.NET is not fully configured.
- Verify in the IIS Manager, under ISAPI and CGI Restrictions, that Restriction is set to Allowed for all of the ASP.NET listings.
- Verify that ASP.NET is registered in IIS: In IIS Manager, under Application Pools, verify that there are ASP.NET listings.
To manually register ASP.NET, see the command lines following this table.
If you continue to have issues, review your IIS and ASP.NET setup. For more information, see Prepare your server for ShareFile data.
|“Failed to Save Storage Center Binding” appears during StorageZones Controller configuration
||The message indicates a permissions problem on the IIS Account Pool user. By default, application pools operate under the Network Service user account. StorageZones Controller uses the Network Service account by default. If you use a named user account instead of the Network Service account, the named user account must have full access to the network share used for private data storage.
|“Access denied” appears during zone configuration
||The message can occur if the ShareFile account you are logged on as does not have permission to create and manage zones. Use the ShareFile administrator console to set that permission.
|Outbound requests are blocked
||When outbound requests are blocked, the cfgsrv log includes System.Net.WebException: The remote server returned an error: (403) Forbidden. This issue is likely due to the proxy server blocking outbound requests. Verify that your firewall meets the requirements specified in StorageZones Controller system requirements.
|“Unable to connect to remote server” appears when you log on to StorageZones Controller
||The message typically indicates a proxy issue. Make sure that your proxy settings are configured, as described in Specify a proxy server for StorageZones.
If the proxy settings are correct, verify that:
- You can log into your ShareFile account from StorageZones Controller.
- You have administrator-level permissions to configure StorageZones Controller.
- Port 443 is open on the external firewall.
|The folder named ShareFileStorage on your network share does not include SCKeys.txt after you enable and configure StorageZones for ShareFile Data
||StorageZones Controller creates SCKeys.txt during installation unless the account you used to install StorageZones Controller is not in the access control list. Update the access control list and reinstall StorageZones Controller.
|File uploads to a shared folder fail after you create a zone
||This issue indicates a problem with your internal DNS. You must have both an internal and external DNS record for the StorageZones Controller FQDN unless the zone is a restricted StorageZone.
|On the Monitoring tab, the Heartbeat Status is red
||A red icon indicates that StorageZones Controller isn’t able to send heartbeat messages to the ShareFile web site.
- Check if the icons for other components are red. If so, refer to the logs for more information.
- If the s3uploader log shows a failure to send the heartbeat, the StorageZones Controller server might not be able to contact the ShareFile web site unless it goes through a proxy server. To specify a proxy server for StorageZones Controller, open the controller console and go to the Networking tab.
- If the StorageZones Controller server cannot access the ShareFile web site using a network service user, either allow the network service user to access the ShareFile web site or set up a Windows user account with outbound access to the proxy server.
|A StorageZone does not appear in the ShareFile administrator interface
||This issue can indicate a problem with the external address or firewall.
First verify in the StorageZones Controller console that the External Address does not include the port. If it does, remove the port and then restart the controller.
If the External Address does not include the port, make sure that your Windows firewall is configured correctly. By default, Windows firewall settings allow outbound traffic for the ShareFile services on port 443. StorageZones Controller requires that setting. Verify that Windows firewall allows outbound traffic on port 443 for the following processes:
|StorageZones Controller does not upload data to ShareFile
- In the NetScaler console, right-click the load balancing virtual server for statistics, to verify whether traffic is reaching NetScaler from the ShareFile control plane, StorageZones Controller, and ShareFile clients. When you upload a file and the virtual server shows an increase in hits, then the traffic is passing through NetScaler.
Verify the traffic for every point of the NetScaler connection:
- Content switching virtual server
- Load balancing virtual servers for Connectors and for ShareFile data
- HTTP callouts bound to one of the two virtual servers
- Responder policy bound to the ShareFile data virtual server
- Connectors virtual server binding to AAA
- Test uploads for ShareFile data:
- Unbind the responder policy in the load balancing virtual server for ShareFile data. (The responder policy drops incoming traffic that is not signed by the ShareFile control plane.)
- From a web browser, type the external FQDN of StorageZones Controller. If there is connectivity, the ShareFile logo appears.
- From a web browser, type the URL for a connector.
- Test accessibility of StorageZone Connectors:
If the following URLs are successful, you will be prompted for credentials even if the back-end server is down. Or, if you are logged on as a user, you will get an API response.
The API response is in this form:
- Test devices from the external network. Device connectivity issues can result from DNS setup. You must have an external DNS record and you might also need an internal DNS record for the external StorageZones FQDN.
- If you are having trouble with a particular device only, test that device. For more information, see “A mobile device won’t connect to a connector” in the table in "Troubleshoot ShareFile clients and web app", next.
|The ShareFile Connectivity from File Cleanup Services status is a red icon after you upgrade StorageZones Controller
||A red icon occurs if Windows starts the File Cleanup Service before StorageZones Controller establishes a network connection. The status will return to a green icon after the controller server is back on the network.
|“Path exceeds max length (1024)” appears during connector creation
||The message can occur if the external address configured for StorageZones Controller points to the ShareFile web site instead of the StorageZones Controller server FQDN.
“Invalid name” appears when configuring a new StorageZones Controller after deleting an old one
Restricted Zone Error: HTTP Error 500 (internal server error)
|The message can occur if entities related to the old StorageZones Controller still exist. To resolve this issue:
- Uninstall the new StorageZones Controller.
- Delete the shared network folder.
- Delete the folder c:\inetpub\wwwroot\Citrix.
- Open regedit and delete this key: HKLM/Software/Wow6432Note/Citrix.
- Install and configure a new StorageZones Controller. If the issue persists, contact your support representative.
This message occurs when StorageZone Servers cannot resolve the StorageZone FQDN via DNS or the local hosts file. Ensure you have a DNS record or hosts file entry in place so that client workstations and devices can successfully connect to the restricted zone servers.