I could connect to my CRM system with Workbench, but when I tried to get the data objects, the connection would timeout.  I did the same test on my test CRM system and it worked flawlessly.  Finally I came across this item on Scribe’s knowledge base and forum site:

This article describes one solution for helping with timeouts when working with the Scribe Adapter for Dynamics CRM. We have seen timeouts occur when the adapter is trying to update its metadata and when the adapter is being used by a DTS to do some operation against the CRM system, such as an update or insert.

    Here are some examples of error messages that may occur:

    CrmService.Execute(AssignRequest) – The operation has timed out.

    CrmService.Execute(UpdateRequest) – The operation has timed out.

    System.Net.WebException: The operation has timed out

    The default timeout is 100 seconds. This solution calls for increasing the amount of time the adapter tries to do its work before it times out. For some situations, this may be enough to solve the problem, for others, you may need to look for the cause of why it is taking so long to do the operation.

    You can add a DWORD to the registry on the Scribe server that will make the adapter wait longer before timing out. Note that this setting is recognized by the adapter version 4.3 and higher. If you have an earlier version of the adapter and you want to try this solution, you need to upgrade the adapter. Also, note that this setting has no impact on the publisher.

    This solution calls for editing the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs.

    1.       Add a new DWORD value to the registry on the Scribe server in this location – [HKEY_LOCAL_MACHINE\SOFTWARE\Scribe\Adapters\DynamicsCRMAdapter].

    2.       Make the name of the DWORD “SOAPTimeoutSeconds”.

    Then enter a value for the DWORD as the number of seconds you want to adapter to wait before it times out. For example if you wanted it to wait for 5 minutes, enter a decimal value of 300.
This worked like a charm.  It also looks like my original problem occurred due to a hardware failure.