Home Server
New Blog Posts: Merging Reports - Part 1 and Part 2

Unable to connect to server

edited January 2003 in Server
Hello,

I am very new at Report Builder... I have been designated to try it out and
see if it would suit our needs. I have downloaded the trial version this
morning and with the "Report Builder Server Edition; Developer's Guide", I
am trying to publish reports to the web... I am working on my workstation
(Windows XP, IIS 5.1).

I have done the example of a Report Server App., followed with the thin
client app and then tried the WebTier thing... I can't seem to make it work.
I went to page 53 and followed the Tutorial to a T and still I am not able
to connect...

Am I missing something?

HDumas

Comments

  • edited January 2003

    The demos and tutorials do indeed work correctly.

    The trial version is limited such that you must run the server, thin-client,
    and webtier applications on the same machine and only use 127.0.0.0 as the
    IP address.

    I assume from your comments that you have successfully completed each of the
    tutorials preceeding the tutorial called 'Publish Reports to the Web'.
    Therefore, I assume that on your machine you have a report server
    application running as a Windows service and that you can connect to that
    report server application using a Windows thin-client application.

    If you are receving an "Unable to connect to server" error in the web
    browser:

    1. Make sure that you are using 127.0.0.0 for the report server application
    and web tier application.

    2. Make sure that the report server application is running.
    a. Verify that RB Services system tray icon is green.
    b. Clieck on the RB Services system tray icon verify the status indicates
    the server is running.
    c. Run the Windows thin-client application from the previous tutorial and
    verify that it can connect and function properly.

    3. Run the web browser from your machine and verify that it can function
    properly.

    4. If you are receiving some other type of error. Read the article below.

    5. If you still have an issue, please specify more details on this thread.
    :)




    ----------------------------------------
    RB WebTier and IIS User Accounts
    ----------------------------------------

    Question: I am trying to configure and test the RB WebTier using IIS. When
    I try to test the web tier via my web browser an Internal Server 500 Error
    page is displayed.

    This is generic error page returned by IIS.

    One cause of this error is that the WebTier application does not have
    sufficient user access rights.


    Solution:

    1. Unload the WebTier application.

    Use IIS to access the properties dialog for the rbWebPub virtual directory.
    Press the UnLoad button to unload the ISAPI dll.

    2. Delete rbWebPub subdirectories

    Use Windows Explorer to delete all subdirectories inside the rbWebPub
    directory. If you are using different WebTier CacheDirectory or WebTier
    LogSettings, then delete those directories also.


    3. Configure IIS User Accounts

    There are two user accounts created by IIS: IUSR_MachineName and
    IWAM_MachineName. (MachineName is replaced by the name of your computer).

    a. Use Windows Explorer to access the properties dialog for the rbWebPub
    directory.

    b. Check whether the IUSR_MachineName and IWAM_MachineName accounts appear
    in the list of users. If not then add them.

    c. The IUSR_MachineName account is the Internet Guest Account. This account
    requires Read, Execute, and Write access to rbWebPub.

    d. The IWAM_MachineName account is a user account that IIS uses to run web
    applications such as the web tier. This account requires full control of the
    rbWebPub directory. The web tier must be able to read, write, and create new
    files and sub directories for the CacheDirectory and the Log. Therefore if
    you configure the WebTier to use directories that are not subdirectories of
    rbWebPub, you will need to configure those directories as well.

    e. reboot the machine.




    --
    Nard Moseley
    Digital Metaphors
    http://www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
This discussion has been closed.