[rt-users] rt2 -> rt3 version 1.12 failure.

[B. Ash]

Hi,

I have attached t-32 and t-33,  t-32 seems to get imported correctly, it 
seems to be t-33 that causes the problems with the hash for NewValue. 


b. ash




Jesse Vincent wrote:

>On Tue, May 13, 2003 at 04:50:09PM -0600, B. Ash wrote:
>  
>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>Hi,
>>
>>I am still running into errors while attempting to upgrade to rt3.0.1.
>>
>>I have discovered that if I remove the tickets after they have been 
>>imported using dumpfile-to-rt-3.0, the script will move on to next 
>>ticket that failed to be imported on the first run.  This ticket will be 
>>imported along with a handful of others, and then the error about the 
>>"NewValue for HASH" comes up again. 
>>    
>>
>
>Can you send us the ticket dump file that contains the hash for
>NewValue?
>
>  
>


-- 
------------------ <-=-> ----------------------
Benjamin Ash
Systems Analyst II 
ECE Dept. University of New Mexico   | University of New Mexico, 87131  
+1 505 277 1082 /Fax +1 505 277 1439 | e-mail: bash at eece.unm.edu

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: t-32
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20030514/04f02c50/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: t-33
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20030514/04f02c50/attachment-0001.ksh>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 252 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20030514/04f02c50/attachment.sig>