wheribert - Thursday, July 10, 2008 4:29 AM:
Hello,
I've got a problem checking files in since I did an update from 8.2.0 to 9.0.1.
If I create a document with an assigned file, I can check the file in and out with no problem.
If I try to do the same thing with the same objects on the next day I get the following error message:
ProcessApplyItem: Innovator Server failed to ApplyItem (Failed to
update the File with ID 94EF01BAE6C64796897B0D8F4ED31619 :
Failed to version the FIle: Failed to version the File: Failed to update the
File with ID F027C6731EB34257B3A9DE2779C73494 : The value of
the effective_date property specified for the File is invalid. A value is
required and it must be greater than of equal to the release date ....)
If I look at the Fileobject in nash I get the following result:
<Item type="File" typeId="8052A558B9084D41B9F11805E464F443" id="94EF01BAE6C64796897B0D8F4ED31619" page="1" pagemax="1" itemmax="1">
...
<effective_date>2008-07-08T06:47:24</effective_date>
<release_date>2008-07-08T06:47:24</release_date>
...
</File>
The file has got an effective_date and this has the same value as the release_date.
Therefore I do not understand the error message.
This is a big problem, because nobody can work with the filedata in the database. How can I get rid of this error message?
Thanks in advance
M.Schüler
P.S.: complete nash output for the file mentioned above:
<!-- (c) Copyright by Aras Corporation, 2004-2007. -->
<SOAP-ENV:Envelope xmlns:SOAP-ENV="">schemas.xmlsoap.org/.../">
<SOAP-ENV:Body>
<Result>
<Item type="File" typeId="8052A558B9084D41B9F11805E464F443" id="94EF01BAE6C64796897B0D8F4ED31619" page="1" pagemax="1" itemmax="1">
<state>Released</state>
<current_state name="Released" keyed_name="Released" type="Life Cycle State">C363ABDADF8D485393BB89877DBDCFD0</current_state>
<locked_by_id keyed_name="Innovator Admin" type="User">30B991F927274FA3829655F50C99472E</locked_by_id>
<config_id keyed_name="Teil2.SLDPRT" type="File">94EF01BAE6C64796897B0D8F4ED31619</config_id>
<mimetype>drawing/x-sld</mimetype>
<release_date>2008-07-08T06:47:24</release_date>
<checksum>654DF374783D8418B70358B2F9CE2A72</checksum>
<modified_on>2008-07-08T06:47:24</modified_on>
<not_lockable>0</not_lockable>
<major_rev>A</major_rev>
<created_by_id keyed_name="Innovator Admin" type="User">30B991F927274FA3829655F50C99472E</created_by_id>
<modified_by_id keyed_name="Innovator Admin" type="User">30B991F927274FA3829655F50C99472E</modified_by_id>
<is_current>1</is_current>
<id keyed_name="Teil2.SLDPRT" type="File">94EF01BAE6C64796897B0D8F4ED31619</id>
<classification>/*</classification>
<created_on>2008-07-08T06:47:22</created_on>
<permission_id keyed_name="File" type="Permission">28D6DF9D51FA4B85A479D6D3341CE97B</permission_id>
<file_size>89088</file_size>
<checkedout_path>C:</checkedout_path>
<new_version>0</new_version>
<file_type keyed_name="SOLIDWORKS" type="FileType">197CC5F7C4504F49A5C337314189DBEB</file_type>
<is_released>1</is_released>
<keyed_name>Teil2.SLDPRT</keyed_name>
<effective_date>2008-07-08T06:47:24</effective_date>
<generation>1</generation>
<filename>Teil2.SLDPRT</filename>
</Item>
</Result>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Anonymous - Thursday, July 10, 2008 8:46 AM:
I suspect you only rean a service update on the code tree, and did not do a database upgrade. Database upgrades are not done by the installer. I reccommend you contact Aras to discuss your upgrade process before upgrading your database.
Until your upgrade is completed, you can reinstall the Aras Innovator 8.2.0 code tree and restore the previous functionality.
wheribert - Thursday, July 10, 2008 9:25 AM:
than i will do a fresh install of the 9.0.1
thanks
wheribert - Friday, July 25, 2008 2:05 AM:
Hi,
now with a frech installation of 9.0.1 I heve got the same problem again. Any hints that can help?
Best regards
wheribert
Bill - Sunday, July 27, 2008 10:28 PM:
Are you using a new database, or the one you had originally installed when you got the error previously?
-Bill
wheribert - Monday, July 28, 2008 1:57 AM:
Bill:
Are you using a new database, or the one you had originally installed when you got the error previously?
-Bill
I deleted the old database and created a new one.
wheribert - Tuesday, July 29, 2008 2:31 AM:
Hello,
I tried out different things an the problem is gone. I think the change of the default data format of windows made it work again. I am using a german windows xp version. The default date format has been an iso-format (yyyy-mm-dd) an I changed it to the usual german format (dd.mm.yyyy) an I was able to check my files in again.
wheribert
