Veda2.0 Released!


import VD and GDX files related error
#1
Hello, I successfully imported my old model and get results. Now I am on the stage to compare the results with the old version. After I imported the GDX and VD files from old run, it gives me the attached error window "null values cannot be formatted as SQL identifier". After this happens, even my results are not displayed any more, constantly giving me this error message even after starting the model from scratch, after refreshing the results, after changing the AppData folder back when it was working, etc. Could you help please? Is there an option to un-import those GDX and VD files? What could be an issue with my VD and GDX files? Why do they give an error?


Kind regards.


Attached Files Thumbnail(s)
   
Reply
#2
I am not a VEDA expert, but Amit asked me to implement in TIMES some additional information to be written into the *.vd* files, to facilitate efficient importing of the results into VEDA2.0. Therefore, one possible explanation for the error is that you may have been using some old version of TIMES for the old runs, such that the additional information needed for VEDA2 is missing in the *.vd* files.
Reply
#3
(26-01-2021, 02:32 AM)Antti-L Wrote: I am not a VEDA expert, but Amit asked me to implement in TIMES some additional information to be written into the *.vd* files, to facilitate efficient importing of the results into VEDA2.0. Therefore, one possible explanation for the error is that you may have been using some old version of TIMES for the old runs, such that the additional information needed for VEDA2 is missing in the *.vd* files.
Thank you Antti, I will ask my colleague if in fact he used an old version and get back to you
Reply
#4
Hello, my colleague says that he is quite sure he updated the TIMES source code before running the old veda. He will double check it once again tomorrow but for now it seems that is not an explanation...
Reply
#5
Smile 
Ok, fine!  I am very glad if the problem was not related to TIMES at all!  Shy
I can thus only leave it to the Kanors staff for giving further help troubleshooting it.
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Error 170: Domain violation for element in syssettings kushagra 7 522 15-01-2026, 06:26 PM
Last Post: Antti-L
  Fatal Error Anuradha 2 268 20-09-2025, 08:31 PM
Last Post: Anuradha
  Subject: How to prevent VEDA from generating vd-files during model runs? KristofferEML 4 792 22-08-2025, 11:48 AM
Last Post: KristofferEML
  Error 170 Domain violation for element BrageAG 14 13,268 01-07-2025, 06:18 PM
Last Post: AKanudia
  Specifying emissions for the import process. janis 5 1,545 25-02-2025, 10:29 PM
Last Post: janis
  Sync error when including international trade xiao.li8@mcgill.ca 4 1,493 03-02-2025, 08:01 PM
Last Post: xiao.li8@mcgill.ca
  Optimizing solver-opt files for stochastic runs LucasRM 4 1,599 13-01-2025, 08:18 PM
Last Post: LucasRM
  VEDA2 fatal error (unexpected case sensitivity) Antti-L 2 1,163 30-08-2024, 10:49 PM
Last Post: Antti-L
  Unexpected error in model run BSR 2 1,368 17-07-2024, 07:07 PM
Last Post: BSR
  An error when I read JRC-EU-TIMES Lee 7 4,072 03-06-2024, 05:28 PM
Last Post: Lee

Forum Jump:


Users browsing this thread: 2 Guest(s)