Clarity

  • 1.  OWB - "The stream version from the server is not the same as the clie

    Posted Apr 19, 2010 07:20 AM
    We are using Clarity 7.5.3 FP08 and when a user tries to save a large project they receive the following on an intermittent basis:  "The stream version from the server is not the same as the client's stream version."  Their version OWB matches our current release.   Any information to shed light on this issue would be appreciated.  Here's an error output that seems to coincide with our issue:ERROR 2010-04-19 10:28:08,971 [ApplicationServerThread] niku.schedulers (******:845502952__86b19:schedulers.postProject) Rolling back transaction:
    com.evermind.server.http.HttpIOException: Connection reset
         at com.evermind._gs.read(.:210)
         at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
         at java.io.BufferedInputStream.read1(BufferedInputStream.java:222)
         at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
         at java.util.zip.InflaterInputStream.fill(InflaterInputStream.java:213)
         at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:134)
         at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:105)
         at java.io.DataInputStream.readUnsignedByte(DataInputStream.java:352)
         at com.niku.xmlserver.blob.PVInputStream.readPVByte(PVInputStream.java:92)
         at com.niku.xmlserver.blob.PVInputStream.readPVShort(PVInputStream.java:97)
         at com.niku.xmlserver.blob.PVInputStream.readPVDate(PVInputStream.java:121)
         at com.niku.xmlserver.blob.NkCalendarException.restoreFrom(NkCalendarException.java:82)
         at com.niku.xmlserver.blob.NkCalendarException. (NkCalendarException.java:23)
         at com.niku.xmlserver.blob.NkCalendarExceptionList.restoreFrom(NkCalendarExceptionList.java:151)
         at com.niku.xmlserver.blob.NkCalendar.restoreFrom(NkCalendar.java:653)
         at com.niku.xmlserver.blob.PVInputStream.readPVObject(PVInputStream.java:227)
         at com.niku.xmlserver.blob.NkSegment.restoreFrom(NkSegment.java:213)
         at com.niku.xmlserver.blob.NkSegment. (NkSegment.java:24)
         at com.niku.xmlserver.blob.NkSegmentList.restoreFrom(NkSegmentList.java:1210)
         at com.niku.xmlserver.blob.NkCurve.restoreFrom(NkCurve.java:390)
         at com.niku.schedulers.io.Import.readCurve(Import.java:125)
         at com.niku.schedulers.io.Import.getNextField(Import.java:177)
         at com.niku.schedulers.api.DataRow.restore(DataRow.java:92)
         at com.niku.schedulers.api.DataPackage.importDataRow(DataPackage.java:113)
         at com.niku.schedulers.api.DataPackage.getNextObject(DataPackage.java:91)
         at com.niku.schedulers.server.processors.SetProjectWebHelper.processRequest(SetProjectWebHelper.java:195)
         at com.niku.schedulers.server.processors.SetProjectWebHelper.process(SetProjectWebHelper.java:296)
         at com.niku.schedulers.server.SetProjectRequest.processRequest(SetProjectRequest.java:25)
         at com.niku.schedulers.server.SchedulersPageBuilder.buildPage(SchedulersPageBuilder.java:98)
         at com.niku.union.web.WebControlServlet.service(WebControlServlet.java:487)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
         at com.evermind._hb.doFilter(.:59)
         at com.niku.union.web.filter.GZIPResponseFilter.doFilter(GZIPResponseFilter.java:111)
         at com.evermind._cub._pod(.:387)
         at com.evermind._cub._bmc(.:177)
         at com.evermind._ax._ltc(.:666)
         at com.evermind._ax._uab(.:191)
         at com.evermind._bf.run(.:62)


  • 2.  Re: OWB - "The stream version from the server is not the same as the

    Posted Apr 19, 2010 12:12 PM
    If I recall correctly the version difference error comes from the schedule connect not from OWB.  Reinstalling both OWB and schedule connect from downloads from the server would ensure the versions are the same.  Martti K.


  • 3.  Re: OWB - "The stream version from the server is not the same as the

    Posted Apr 20, 2010 09:45 AM
    We did a full uninstall and reisntall of OWB and Clarity Sched. Connect and that did work for a little while and then the error reappeared.   It appears to happen with our larger projects (with 300 or more assignments). Does 7.5.3 PF08 have a limitation?


  • 4.  Re: OWB - "The stream version from the server is not the same as the

     
    Posted Apr 20, 2010 10:07 AM
    Hi James,
     
    I ran this by Support and they said you should log a ticket if you have extended support.
     
    Regards,
    Chris


  • 5.  Re: OWB - "The stream version from the server is not the same as the

    Posted Apr 20, 2010 10:09 AM
    Did so this AM - ticket # 19263912-1  Thanks


  • 6.  RE: Re: OWB - "The stream version from the server is not the same as t

    Posted Aug 01, 2013 05:59 AM
    Hi,
    any idea on how you solve the problem?

    we are having the same issue for some users:

    npWbench - Unable to open Project PRJXXXXXX. An Exception occured: java.lang.ClassCastExeception: com.niku.xmlserver.core.NKBoolean cannot be cast to com.niku.xmlserver.blob.NKCalendar

    Thx


  • 7.  RE: Re: OWB - "The stream version from the server is not the same as t

    Posted Aug 01, 2013 06:03 AM

    yvaindemolliere wrote:

    npWbench - Unable to open Project PRJXXXXXX. An Exception occured: java.lang.ClassCastExeception: com.niku.xmlserver.core.NKBoolean cannot be cast to com.niku.xmlserver.blob.NKCalendar
    That does not look like the same "OWB Version" issue as in this thread.

    You should contact CA Support over this sort of error though ; it looks like it would be a problem with a specific project (maybe a bug in ScheduleConnect/OWB).


  • 8.  RE: Re: OWB - "The stream version from the server is not the same as t
    Best Answer

    Broadcom Employee
    Posted Aug 01, 2013 06:23 AM
    From a support perspective it would be important indeed to have confirmation whether this problem only occurs with that one project and if so on different OWB machines or not.
    Also helpful would be to get the schedlogging log file ( below referred to as toClient.log).

    Note: Depending on your Clarity/OWB version this might not work on a Windows 7 computer.

    To turn on schedlogging on the workstation (this does require a reboot of the workstation):
    Create on c:\ directly a folder called schedlogging where you will write the schedlogging log files to (c:\schedlogging)

    My Computer/Properties/Advanced/Environment Variables
    Click New under System

    This entry turns on debug:
    Enter
    Variable Name: SCHED_FORK_OUTPUT
    Variable Value: TRUE
    Click OK

    (Please note, to disable schedlogging you would just change this variable value to FALSE)

    Click New

    This entry logs all data going from OWB/MSP to Clarity:
    Enter
    Variable Name: SCHED_OUTPUT_FILE
    Variable Value: c:\schedLogging\FromClient.log

    This entry logs all data coming from Clarity to OWB/MSP:
    Variable Name: schedlogging
    Variable Value: c:\schedLogging\ToClient.log

    After entering the variables reboot your computer to activate them. To
    verify they are active go to a command prompt and type set .

    Note that these logs get overwritten; only the freshest open and save data
    is kept around.