Archive

Archive for the ‘IIS’ Category

Change the File or Report Upload Size

June 19th, 2017 No comments

When you publish a Crystal Report file or document to Ripplestone you are moving the physical file from the local storage to the web server. Ripplestone has a default file size of 20 MB, so report files that are larger than 20 MB will not upload.

With some documents and reports the file can be larger than 20 MB and the limit will need to be increased.

This size can be changed in the web.config file located in C:\Sites\Ripplestone. The web.config file is an XML file that can be edited with any text editor or XML reader (we use Notepad++ to edit our files and love it). Look for the httpRuntime section and change the maxRequestLength to whatever value you would like (1024 = 1MB).

Below is an example of the httpRuntime section with the default values that come with Ripplestone.

image

Setting the IIS Idle Time-out

June 28th, 2013 No comments

The Idle Time-out within IIS can effect Ripplestone by closing the worker process before the session has timed out.  This will cause an error within Ripplestone when you click on a link.  This is because the worker process has been stopped due to inactivity and will result in an error like the one below.

image

The session timeout is set in the web.config file and the two setting (session timeout and the Application Pool Idle Time-out) need to work together.  The Idle Time-out should be equal to or larger than the Session timeout value.

For example, if the session timeout in the web.config file is set to 30 minutes, then the Idle Time-out should be set to a value of 30 minutes or greater.  In the screen shot below it is set to 35 minutes.

image

Accessing Ripplestone From The Server

November 15th, 2012 No comments

There are times when the URL \\localhost\ripplestone will not work on the server. If this happens you can try the following to allow the server to run the Ripplestone website locally.

  1. Click Start, click Run, type regedit, and then click OK.
  2. In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
  3. Right-click Lsa, point to New, and then click DWORD Value.
  4. Type DisableLoopbackCheck, and then press ENTER.
  5. Right-click DisableLoopbackCheck, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Quit Registry Editor, and then restart your computer.

How to Change the File Upload Size in Ripplestone

February 23rd, 2012 No comments

When you publish a Crystal Report file or document to Ripplestone you are moving the physical file from the local storage to the web server. Ripplestone has a default file size of 10 MB, so report files that are larger than 10 MB will not upload.

This size can be changed in the web.config file located in C:\Sites\Ripplestone. The web.config file is an XML file that can be edited with any text editor or XML reader. Look for the httpRuntime section and change the maxRequestLength to whatever value you would like (1024 = 1MB).

Below is an example of the httpRuntime section with the default values that come with Ripplestone.

Changing the Timeout Within Ripplestone

February 22nd, 2012 No comments

Ripplestone has a default timeout period of 20 minutes. If the application has not been used for 20 minutes, the session will end and the user will need to login again to continue. The default value can be changed by editing the web.config file located in C:\Sites\Ripplestone. The web.config file is an XML file that can be edited with any text editor or XML reader. Look for the authentication section and change the timeout to whatever value (in minutes) you would like.

Below is an example of the authentication section with the default value of 20 minutes.

Running Ripplestone on Vista and Windows Server 2008

June 16th, 2009 No comments

I was working with a Ripplestone client to get the software installed on a Vista PC and had a do a few things different than if this was XP Pro or Windows Server 2003. The main differences were that Vista and Windows Server 2008 use IIS 7 and the .NET framework 1.1 is not installed by default.

I started with the following article on setting up Vista and Windows 2008 to run an ASP.NET 1.1 application.

Install ASP.NET 1.1 with IIS7

Once I got ASP.NET 1.1 installed and configured, I need to make sure that Crystal Reports was installed correctly with the Ripplestone installer. This was just a matter of checking the permissions and testing the running of a report within Ripplestone.

All together it took an extra 30 minutes to get everything installed and configured correctly.