Veda2.0 Released!


Issues during start-up and use of VEDA-FE
#1
After a "succesful" installation of VEDA-FE and VEDA-BE, I try to run the VEDA-FE as administrator in trial mode where I get these errors (91, 429, 430 & "-2147221163") (I get the same errors when running as normal user).
I have excel 2016 installed and the veda_savecode add-in activated as seen by the screenshot, however it still pops up with a message that it is not able to sense it??
I'm running Windows 10 as OS.
VEDA-FE gives error codes 9, 13, 91(object variable and importing data), 92, 429, 430 & "-2147221163" when syncing and solving.

I have tried to install as administrator as well, that didn't help either. I have tried to repair my MS Office installation as well.
I have registered all .dll-extensions in the C:\VEDA\VEDA_FE folder.


Attached Files Thumbnail(s)
                                       
Reply
#2
(02-01-2018, 06:12 PM)FrederikPloug Wrote: After a "succesful" installation of VEDA-FE and VEDA-BE, I try to run the VEDA-FE as administrator in trial mode where I get these errors (91, 429, 430 & "-2147221163") (I get the same errors when running as normal user).
I have excel 2016 installed and the veda_savecode add-in activated as seen by the screenshot, however it still pops up with a message that it is not able to sense it??
I'm running Windows 10 as OS.
VEDA-FE gives error codes 9, 13, 91(object variable and importing data), 92, 429, 430 & "-2147221163" when syncing and solving.

I have tried to install as administrator as well, that didn't help either. I have tried to repair my MS Office installation as well.
I have registered all .dll-extensions in the C:\VEDA\VEDA_FE folder.

Have you added an antivirus exclusion of VedaInstaller.exe, VEDA-FE.exe & VEDA-BE.exe?

It will be beneficial for you if retry installing using the following steps:
  • Download the latest VEDAInstaller from VEDA Support Site.

  • From the account who will be using the VEDA Application(s), create a folder called as VEDA and assign Full Permissions to him.  VEDA Support Site has all the details on assigning user permissions. 

  • Place the latest downloaded VedaInstaller.exe in this folder.

  • Right click over it and under 'General' tab, select 'Unblock' the application, if it's blocked. If you're using an Antivirus software, add an exclusion of the VedaInstaller.exe

  • Execute VedaInstaller.exe using the procedure as mentioned here: VEDA-FE and VEDA-BE: Installing from scratch.

  • After installation, and before requesting for a license, add VEDA_FE.exe and VEDA_BE.exe exclusions to your Antivirus.

  • Request for a license- You may use the Evaluation version in case you do not have a license.

  • Go through the Testing Successful Installations page and test your installation.


[Image: cleardot.gif]
Utsav Jha VEDA Support
Reply
#3
(03-01-2018, 10:49 AM)utsavjha Wrote:
(02-01-2018, 06:12 PM)FrederikPloug Wrote: After a "succesful" installation of VEDA-FE and VEDA-BE, I try to run the VEDA-FE as administrator in trial mode where I get these errors (91, 429, 430 & "-2147221163") (I get the same errors when running as normal user).
I have excel 2016 installed and the veda_savecode add-in activated as seen by the screenshot, however it still pops up with a message that it is not able to sense it??
I'm running Windows 10 as OS.
VEDA-FE gives error codes 9, 13, 91(object variable and importing data), 92, 429, 430 & "-2147221163" when syncing and solving.

I have tried to install as administrator as well, that didn't help either. I have tried to repair my MS Office installation as well.
I have registered all .dll-extensions in the C:\VEDA\VEDA_FE folder.

Have you added an antivirus exclusion of VedaInstaller.exe, VEDA-FE.exe & VEDA-BE.exe?

It will be beneficial for you if retry installing using the following steps:
  • Download the latest VEDAInstaller from VEDA Support Site.

  • From the account who will be using the VEDA Application(s), create a folder called as VEDA and assign Full Permissions to him.  VEDA Support Site has all the details on assigning user permissions. 

  • Place the latest downloaded VedaInstaller.exe in this folder.

  • Right click over it and under 'General' tab, select 'Unblock' the application, if it's blocked. If you're using an Antivirus software, add an exclusion of the VedaInstaller.exe

  • Execute VedaInstaller.exe using the procedure as mentioned here: VEDA-FE and VEDA-BE: Installing from scratch.

  • After installation, and before requesting for a license, add VEDA_FE.exe and VEDA_BE.exe exclusions to your Antivirus.

  • Request for a license- You may use the Evaluation version in case you do not have a license.

  • Go through the Testing Successful Installations page and test your installation.


[Image: cleardot.gif]
Thank you for your answer!

I tried to follow your instructions, unfortunately none of that helped. I still experience the exact same issues when starting up, syncing and solving.
I am using the evaluation version as part of a course I am taking at the Technical University of Denmark.
Can you suggest anything else I could possibly do to get VEDA to work?
Reply
#4
I am just another user, and hardly can help much about it, but your earlier screenshot shows that you have an "Interface not registered" error at the start, even though you said that you have registered all the .dll-extensions.  Obviously something still seems not "registered". But what could it be?

On the net I read that this error is typically related to MS Office. You said you have installed Excel2016, but I guess VEDA might still require also MS Office Word (or some common Office interfaces) installed.

Or possibly it could be related to registering OCX files. Previously, VEDA had a batch file VC.BAT for making sure all OCX files are registered, but I am not sure if it is needed/included anymore (??).

Just my fuzzy thoughts...
Reply
#5
Actually, we probably forgot to register MSSTDFMT.dll, as described in the following post http://forum.kanors-emr.org/showthread.php?tid=235&highlight=MSSTDFMT.dll Would it make sense given the error message that Frederik reported?

On a side note, I've just tried installing VEDA on my Windows 10 with 1709 update and have the following observations:
1) Neither FE nor BE gets registered in Control Panel\Programs\Programs and Features i.e., it is not possible to uninstall them properly.
2) FE throws COMDLG32.OCX error.
3) After dealing with with COMDLG32.OCX, FE becomes silent: no errors are thrown no matter how you run it (as admin or not); it just won't start.
4) Registering MSCOMCTL.OCX, COMCT332.OCX, MSFLXGRD.OCX, TABCTL32.OCX, and MSSTDFMT.dll brings FE to life...

I wonder why no errors are thrown at 3)? Is it anything 1709 specific?

Cheers,
Olex
Reply
#6
(04-01-2018, 02:52 AM)olexandr Wrote: Actually, we probably forgot to register MSSTDFMT.dll, as described in the following post http://forum.kanors-emr.org/showthread.php?tid=235&highlight=MSSTDFMT.dll Would it make sense given the error message that Frederik reported?

On a side note, I've just tried installing VEDA on my Windows 10 with 1709 update and have the following observations:
1) Neither FE nor BE gets registered in Control Panel\Programs\Programs and Features i.e., it is not possible to uninstall them properly.
2) FE throws COMDLG32.OCX error.
3) After dealing with with COMDLG32.OCX, FE becomes silent: no errors are thrown no matter how you run it (as admin or not); it just won't start.
4) Registering MSCOMCTL.OCX, COMCT332.OCX, MSFLXGRD.OCX, TABCTL32.OCX, and MSSTDFMT.dll brings FE to life...

I wonder why no errors are thrown at 3)? Is it anything 1709 specific?

Cheers,
Olex

Hi Olex and FrederikPloug,
Ran into a similar issue, but figured it out here while applying for the forum, maybe that it will help you as well.
What led to issues here was the removal of the Office package (I found out we had multiple versions running, and removing one created the actual problems). Suddenly had an error 48, and DLL problems, in addition to the "veda_savecode add-in" for excel (while it was visible through tools)

The solution was to remove all office installations, the access database, empty the registers, and remove VEDA.
Reinstall in the following order:
*Clean install Office and validation.
*Clean install Veda + database access 2007
Solved the problem here.

The additional problem proved the office365 package. I only removed the older "office" install at first. Make sure you remove everything (the older office and the new 365), before cleaning the registers.
Reply
#7
(29-01-2018, 10:18 AM)Enzo Wrote:
(04-01-2018, 02:52 AM)olexandr Wrote: Actually, we probably forgot to register MSSTDFMT.dll, as described in the following post http://forum.kanors-emr.org/showthread.php?tid=235&highlight=MSSTDFMT.dll Would it make sense given the error message that Frederik reported?

On a side note, I've just tried installing VEDA on my Windows 10 with 1709 update and have the following observations:
1) Neither FE nor BE gets registered in Control Panel\Programs\Programs and Features i.e., it is not possible to uninstall them properly.
2) FE throws COMDLG32.OCX error.
3) After dealing with with COMDLG32.OCX, FE becomes silent: no errors are thrown no matter how you run it (as admin or not); it just won't start.
4) Registering MSCOMCTL.OCX, COMCT332.OCX, MSFLXGRD.OCX, TABCTL32.OCX, and MSSTDFMT.dll brings FE to life...

I wonder why no errors are thrown at 3)? Is it anything 1709 specific?

Cheers,
Olex

Hi Olex and FrederikPloug,
Ran into a similar issue, but figured it out here while applying for the forum, maybe that it will help you as well.
What led to issues here was the removal of the Office package (I found out we had multiple versions running, and removing one created the actual problems). Suddenly had an error 48, and DLL problems, in addition to the "veda_savecode add-in" for excel (while it was visible through tools)

The solution was to remove all office installations, the access database, empty the registers, and remove VEDA.
Reinstall in the following order:
*Clean install Office and validation.
*Clean install Veda + database access 2007
Solved the problem here.

The additional problem proved the office365 package. I only removed the older "office" install at first. Make sure you remove everything (the older office and the new 365), before cleaning the registers.

Ok, thanks a lot for sharing this, Enzo!
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Veda Help Saad Awan 2 1,302 11-07-2023, 02:51 PM
Last Post: Saad Awan
  Veda Help Saad Awan 15 6,144 11-07-2023, 12:55 PM
Last Post: AKanudia
  Veda Errors Saad Awan 0 746 03-07-2023, 06:10 PM
Last Post: Saad Awan
  Veda Errors Saad Awan 2 1,473 16-06-2023, 04:06 PM
Last Post: Saad Awan
  Issues in running the ancillary service market extension Vijay Kunmar 2 2,218 07-07-2022, 08:00 PM
Last Post: MikkelBosack
  CSV Export in Veda olexandr 4 4,812 21-04-2021, 08:36 PM
Last Post: AKanudia
  MAC vs. Windows for VEDA-TIMES FE & BE? mbr1818 5 10,556 22-02-2021, 01:52 PM
Last Post: AKanudia
  problem with (re)SYNC of previous working models/DB after reinstall of VEDA Koen Smekens 9 8,840 29-12-2020, 08:01 PM
Last Post: Antti-L
  Fatal error in VEDA opening vahid.aryanpur 2 4,387 15-07-2020, 06:05 PM
Last Post: vahid.aryanpur
  Unexpected termination of the VEDA-FE run seckg 3 5,968 21-09-2019, 07:25 PM
Last Post: Antti-L

Forum Jump:


Users browsing this thread: 1 Guest(s)