Welcome Guest, Login


Quick Search

 Source:  - The input stream is not a valid binary format. The starting contents (in bytes) are: 54-6F-75-62-2E-52-65-6D-6F-74-69-6E-67-2E-53-65-63 ...
Server stack trace:
   at System.Runtime.Serialization.Formatters.Binary.SerializationHeaderRecord.Read(__BinaryParser input)
   at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadSerializationHeaderRecord()
   at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
   at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean 
isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean 
isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Remoting.Channels.CoreChannel.DeserializeBinaryResponseMessage(Stream inputStream, IMethodCallMessage reqMsg, Boolean bStrictBinding)
   at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.DeserializeMessage(IMethodCallMessage mcm, ITransportHeaders headers, Stream stream)
   at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at jVersionCheck.jVersionControl.jVersionCheck.get_VersionObject()

   at Client.frmLogin.VersionIsOK()
   at Client.frmLogin.cmdLogin_Click(Object sender, EventArgs e)

This problem is often fixed by deleting the ClientTierSettings.xml file and then opening the CAREWare client application again. CAREWare will recreate the clienttiersettings.xml file, but you will need to add your server name on the server list to connect successfully. You can find the ClientTierSettings.XML file in the client tier directory located by default at C:\Program Files\CAREWare\RW CAREWare Client Tier. Make sure the client tier application is not open, and then delete the ClientTierSettings.XML file. Make sure the client application has necessary permissions to update the ClientTierSettings.xml file by following the instructions here.

To add a server to the server list:

  1. Click Options.
  2. Click Server List.
  3. Click Add.
  4. Add the correct server name to the list.
  5. Click Save.
  6. Click Close.
  7. Choose that server and login again.

If the above steps do not resolve the issue, then you may have a cache copy of the clientTierSettings.XML file in the Windows Users directory. The easiest way to determine if there is one is to use Windows Search.

  1. Go to Computer>C:\ Drive>Users.
  2. Press Ctrl-F to open the find window.
  3. Type in ClientTierSettings.XML and then press Enter.
  4. Highlight any file returned named ClientTierSettings.XML and press Delete.
  5. When prompted press Yes to confirm.

Once the cached copy and original copy of the clientTierSettings.XML file are deleted, re-open the client tier and again add the server IP address or hostname using steps #1 - 7 above.

Back to Errors

Back to Frequently Asked Questions

jProg is a registered trademark of Jeff Murray's Programming Shop, Inc. All other products mentioned are registered trademarks or trademarks of their respective companies. Questions or problems regarding this web site should be directed to JeffMurray@jprog.com.

© 1998- Jeff Murray's Programming Shop, Inc. (jProg) , all rights reserved.