Skip to main content
A
Anonymous
May 16, 2008
Question

End of Stream error messages

  • May 16, 2008
  • 1 reply
  • 796 views
We have been having several problems with RoboSource Control over the past few weeks. We have three authors working on the same project. We keep getting instances of the following or similar type messages in RoboHelp. These messages can occur when we are in RoboHelp or sometimes RoboHelp forces us to close and then we get this message when trying to reopen the project. Sometimes it prevents us from reopening the project, other times it lets us into the project after it displays. Does anyone have any idea what this message is or how to fix the problem?


Show Exception Stack Trace

Unable to read beyond the end of the stream.



at System.IO.__Error.EndOfFile()

at System.IO.BinaryReader.ReadString()

at NG3.Core.BinaryReaderEx.ReadString(String xval, Boolean& changed)

at NG3.Core.BaseNode.DeSerialize(NodeContext context, BaseNode parent, BinaryReaderEx r)

at NG3.MiddleTier.NG3MiddleTierDatabase.UpdateNode(NG3MiddleTierNode node)

at NG3.MiddleTier.NG3MiddleTierDatabase.GetFiles(NG3MiddleTierSession session, NG3MiddleTierNodeEntity node, String localPath, UInt32 systemVersion, RecursiveOption recurseOption, GetOption getOption)

at SCCAPI.SCCIMPL.SccGet(Int32 context, Int32 hwnd, String[] fileNames, SccGetFlags dwFlags, Int32 options)
This topic has been closed for replies.

1 reply

A
Anonymous
May 16, 2008
Another example of an error message:

RoboSource Error

Ticks must be between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks.
Parameter name: ticks

Show stack trace
Gravenstein
Gravenstein
Inspiring
May 16, 2008
I'm not entirely sure, but I think the "ticks" error is a random occurrence that you ought to be able to ignore.

As for the other set of messages, I don't know what they mean. I do know that RoboHelp/RSC *hates* it when a RoboSource-Controlled session crashes. It's after a crash that you're most likely to run into errors and corruption -- usually affecting the project.cpd file.

You might try having everyone rebuild their cpd files. (If the project is large--meaning that it'll take a long time to rebuild the cpd file--you can actually have just one person do the rebuild and share the cpd with the others.) You might also try rebooting the RSC server if you haven't done that in a while.

As a final note, it's a good idea to keep backups of your local project source files. If necessary, you can restore your project files with a backup that didn't get trashed during the crash.

G
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices