RES Workspace Manager Relay server does not update cache or receive transactions

Version 4


    Consider the following scenario:

    • RES ONE Workspace Relay Servers are installed in a cascaded setup, one or more RES ONE Workspace Relay Servers are connecting to a master RES ONE Workspace Relay Server.
    • In the RES ONE Workspace Console at Administration > Relay Servers , there will be a RES ONE Relay Server which is not getting cache updates nor any transactions are uploaded to the RES ONE Workspace Relay Server.

    Other symptoms may be:

    • After trying to force the cache update, the cache is still not updating.
    • CPU usage of the RelayServer.exe process is close at 100%
    • Running the RES ONE Relay Server in interactive mode is working fine.


    In the Microsoft Windows Application Event Log, there may be errors for RelayServer.exe that looks like this:


    Error: The file exists.

    Version: (2015) CS:281340


      at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

      at System.IO.Path.InternalGetTempFileName(Boolean checkHost)

      at RES.Core.IO.Windows.FileOperationsWindows.GetTempFile()


    Error: Value cannot be null.

    Parameter name: filePath


    Version: (2015) CS:281340



       at RES.WorkspaceManager.Caching.Common.IO.LongFileReference..ctor(String filePath, Boolean deleteOnDispose)

       at RES.WorkspaceManager.RelayServer.Messages.Core.BaseFileMessage.FromClient(IConnectedStateBase client, Int64 dataLength, Boolean isCompressed, String messageTypeId)

       at RES.WorkspaceManager.Caching.Cacher.SendTransaction(BaseTransaction transaction, String extension)

       at RES.WorkspaceManager.Caching.Cacher.SendComputerUpdate(Boolean createIfNotExists)

       at RES.WorkspaceManager.Caching.Cacher.VerifyComputerIdentity(IRemoteDataProvider remoteDataProvider)

       at RES.WorkspaceManager.Caching.Cacher.ThreadedStart()



    The %windir%\temp is full (approximately 65572 files) or there is a backup of files in %windir%\temp that may have not been deleted.

    The file names look like tmp####.tmp.

    If the Relay Server Service is running with a service account the tmp files are created in %LOCALAPPDATA%\Temp for that user.



    This issue is resolved in RES ONE Workspace Relay Server 2015 SR2.


    In case the Service Release is not (yet) available or in case the Service Release cannot be installed, a revision containing this update is available on request at RES Support.


    IMPORTANT: A revision contains multiple fixes. Only apply this revision when you are experiencing a specific problem.

    Unless you are severely impacted by this specific problem, RES Software recommends that you wait for the next service release containing these fixes.




    Delete the temp files in %windir%\temp that match the pattern tmp####.tmp, (where #### is a hexadecimal number).

    Once this is cleared, errors should no longer appear, and the cache should update as normal as well as the transactions should be uploaded and processed again.



    In case of running the RES ONE Workspace Relay Server in interactive mode click the "STOP" button and close the interactive Window,

    now start the RES ONE Workspace Relay Server service from the Microsoft Windows Services management console.