SwedeSpeed - Volvo Performance Forum banner

221 - 240 of 390 Posts

·
Registered
Joined
·
109 Posts
Discussion Starter #221 (Edited)
Installing a clean install of Windows 10 Pro x64 1703 (en-US) now. Will try to follow my guide and see what happens.

Will be back with result.
 

·
Registered
Joined
·
109 Posts
Discussion Starter #222
Guide is still current with Windows 10 Pro x64 1703. The errors you guys above experience must be due to other circumstances (didn't even have the port in use problem - maybe a Home edition problem?). I did steps 9 through 20 without upgrading to SQL 2016 (although I recommend doing this). Try doing either a new clean install of Windows or try my cleanup guide before installing VIDA again. And once again, this guide is for Windows 10 Pro, if it works or not in the Home version I do not know but have been proven by other people in this thread with earlier versions of Windows to work ok.
 

·
Registered
Joined
·
1 Posts
Just signed up to say thanks to trixeo. The guide worked beautifully for me. Got the copycat dice from eBay, then installed w10 on my old laptop and finally got it all going fine. All thanks to this thread. Read it all but just followed the initial post. Thanks again!
 

·
Registered
Joined
·
9 Posts
Hello.

Now I have installed VIDA on a New computer With Win 8.1 Pro
I got it to work once, but the second time i tried vida monitor only is red, an status says "halted" and I get a pop up Message that says: "Can not Connect to database"

Any idea what is wrong?
 

·
Registered
Joined
·
9 Posts
A bit from the VidaMonitor log.
Some in Norwegian, but I hope you get the important part :)

"
28.05.2017 12:16:44 : Log started
28.05.2017 12:16:44 : Reading configuration file system\config\VidaMonitor.conf.xml
28.05.2017 12:16:44 : Debug set to false
28.05.2017 12:16:45 : Checking databases
28.05.2017 12:16:45 : SQL server started
28.05.2017 12:16:45 : Trying to open a connection database server (Master DB)
28.05.2017 12:16:45 : Could not open a connection...error message:

ERROR [IM002] [Microsoft][ODBC Driverbehandling] Finner ikke datakildenavnet, og det er ikke angitt noen standarddriver
 

·
Registered
Joined
·
9 Posts
Has anyone a solution on VIDA not starting after latest update on W10 Creators Update?

About this problem
Maybe a Log will help.

16.05.2017 17.18.04 : Trying to shut down JBoss gracefully
16.05.2017 17.18.13 : JBoss shut down
16.05.2017 17.18.13 : Killing cmd
16.05.2017 17.18.13 : Number of deletete cache files: 0
16.05.2017 17.18.13 : Checking JBoss remoting port 4447
16.05.2017 17.18.13 : Starting JBoss
16.05.2017 17.18.13 : Wait for+ java to start. Checking port 80
16.05.2017 17.22.31 : Process java waited too long to start
16.05.2017 17.22.31 : Process java didn't start
16.05.2017 17.22.31 : VIDA failed to start
 

·
Registered
Joined
·
9 Posts
About this problem
Maybe a Log will help.

16.05.2017 17.18.04 : Trying to shut down JBoss gracefully
16.05.2017 17.18.13 : JBoss shut down
16.05.2017 17.18.13 : Killing cmd
16.05.2017 17.18.13 : Number of deletete cache files: 0
16.05.2017 17.18.13 : Checking JBoss remoting port 4447
16.05.2017 17.18.13 : Starting JBoss
16.05.2017 17.18.13 : Wait for+ java to start. Checking port 80
16.05.2017 17.22.31 : Process java waited too long to start
16.05.2017 17.22.31 : Process java didn't start
16.05.2017 17.22.31 : VIDA failed to start
Problem Solved.

Did Step 16f, reinstalling Java. Now VIDA monitor is Green :)
 

·
Registered
Joined
·
4 Posts
Thanks so much for your detailed instructions. I had VIDA working last week on Windows 10 following your instructions, but a few days later my computer upgraded to the latest Windows 10 Creators Update. Now the VIDA monitor icon stays on yellow for a long time until it change to "?".

I followed your instuctions again to uninstall and reinstall VIDA but same problem.

Any help would be appreciated.
 

·
Registered
Joined
·
2 Posts
Hi guys,
My laptop is an HP Compaq 6715b, 64 bit AMD Turion 64x2 with 3Gb of RAM and a 2Ghz processor and is running Windows 7 64 bit.
I have tried installing Vida 2014D numerous times over the last month but I keep getting an exception error when accessing the diagnostics tab.
It read the car without any problem but that's as far as it goews.

The exception I get is as follows:

System.Runtime.InteropServices.COMException (0x80040154): Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))
at System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance(Guid& clsid, Object punkOuter, Int32 context, Guid& iid)
at System.Windows.Forms.AxHost.CreateWithoutLicense(Guid clsid)
at System.Windows.Forms.AxHost.CreateWithLicense(String license, Guid clsid)
at System.Windows.Forms.AxHost.CreateInstanceCore(Guid clsid)
at System.Windows.Forms.AxHost.CreateInstance()
at System.Windows.Forms.AxHost.GetOcxCreate()
at System.Windows.Forms.AxHost.TransitionUpTo(Int32 state)
at System.Windows.Forms.AxHost.CreateHandle()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.AxHost.EndInit()
at Vcc.Vida.DiagSwdl.UI.Components.NavImage.init()
at Vcc.Vida.DiagSwdl.UI.Components.NavImage..ctor()
at Vcc.Vida.DiagSwdl.UI.Components.CustomerSymptomsDtcRefInfoControl.InitializeComponent()
at Vcc.Vida.DiagSwdl.UI.Components.CustomerSymptomsDtcRefInfoControl..ctor(IWorkshopSession workshopSession, IVehicleAccess vehicleAccess, IInfoElementsRepository infoElementsRepository, ICarComRepository carComRepository, INavImageProvider navImageProvider, IEcuMetaProvider ecuTypeResolver, IDiagnosticSessionWF diagnosticSessionWF)
at Vcc.Vida.DiagSwdl.UI.Diagnostics.ReferenceInformationForm.myInitalizeComponent()
at Vcc.Vida.DiagSwdl.UI.Diagnostics.ReferenceInformationForm..ctor(IWorkshopSession workshopSession, IVehicleAccess vehicleAccess, IInfoElementsRepository infoElementsRepository, ICarComRepository carComRepository, INavImageProvider navImageProvider, IEcuMetaProvider ecuTypeResolver, IDiagnosticSessionWF diagnosticSessionWF)
at Vcc.Vida.DiagSwdl.UI.Diagnostics.DiagnosticManager.GetReferenceInformationFormForm()
at Vcc.Vida.DiagSwdl.UI.Diagnostics.DiagnosticManager._referenceInformationButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at Vcc.Vida.DiagSwdl.GuiComponents.FlatButton.OnClick(EventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
-------------------------------------------------------
Loaded assemblies
ProgressHandler, Version=2.0.5394.27532, Culture=neutral, PublicKeyToken=null
System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
VehCom2, Version=2.0.5394.27561, Culture=neutral, PublicKeyToken=null
AppServices.VehicleAccess, Version=2.0.5394.27567, Culture=neutral, PublicKeyToken=null
AxInterop.ISOVIEWXLib, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
System.Runtime.Serialization, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
BizServices.ScriptRepository, Version=2.0.5394.27556, Culture=neutral, PublicKeyToken=null
BizServices.SoftwareProductInformation, Version=2.0.5394.27556, Culture=neutral, PublicKeyToken=null
System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
BizServices.NavImageRepository, Version=2.0.5394.27555, Culture=neutral, PublicKeyToken=null
System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
dejrlij9, Version=2.0.5394.27562, Culture=neutral, PublicKeyToken=null
AppServices.Scripting, Version=2.0.5394.27565, Culture=neutral, PublicKeyToken=null
BizServices.VehicleImageRepository, Version=2.0.5394.27556, Culture=neutral, PublicKeyToken=null
SMDiagnostics, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
BizServices.VehicleResolver, Version=2.0.5394.27557, Culture=neutral, PublicKeyToken=null
ValueObjects, Version=2.0.5394.27551, Culture=neutral, PublicKeyToken=null
GuiComponents, Version=2.0.5394.27558, Culture=neutral, PublicKeyToken=null
AppServices.Dro, Version=2.0.5394.27562, Culture=neutral, PublicKeyToken=null
ICSharpCode.SharpZipLib, Version=0.84.0.0, Culture=neutral, PublicKeyToken=1b03e6acf1164f73
ResourceManager.resources, Version=2.0.5394.27529, Culture=en-GB, PublicKeyToken=null
BizServices.AccessServer.DB, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
BizServices.SoftwareOrdering, Version=2.0.5394.27566, Culture=neutral, PublicKeyToken=null
BizServices.SoftwareOrderRepository, Version=2.0.5394.27564, Culture=neutral, PublicKeyToken=null
AppServices.SoftwareOrderProcessing, Version=2.0.5394.27566, Culture=neutral, PublicKeyToken=null
BizServices.PartsLists, Version=2.0.5394.27560, Culture=neutral, PublicKeyToken=null
Util, Version=2.0.5394.27531, Culture=neutral, PublicKeyToken=null
BizServices.Scripting, Version=2.0.5394.27564, Culture=neutral, PublicKeyToken=null
BizServices.CarCom.VehicleServices, Version=2.0.5394.27554, Culture=neutral, PublicKeyToken=null
System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
BizServices.DiagnosticSession, Version=2.0.5394.27554, Culture=neutral, PublicKeyToken=null
BizServices.VehicleCommProvider, Version=2.0.5394.27562, Culture=neutral, PublicKeyToken=null
AppServices.WorkshopSession, Version=2.0.5394.27559, Culture=neutral, PublicKeyToken=null
ResourceManager, Version=2.0.5394.27529, Culture=neutral, PublicKeyToken=null
AppServices.EcuDataResolver, Version=2.0.5394.27559, Culture=neutral, PublicKeyToken=null
u-6tkklm, Version=2.0.5394.27560, Culture=neutral, PublicKeyToken=null
System.IdentityModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Transactions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
BizServices.InfoElementsRepository, Version=2.0.5394.27554, Culture=neutral, PublicKeyToken=null
System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
BizServices.CarCom.DB, Version=2.0.5394.27553, Culture=neutral, PublicKeyToken=null
System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Workflow, Version=2.0.5394.27569, Culture=neutral, PublicKeyToken=null
System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
BizServices.DroResultFileProducer, Version=2.0.5394.27560, Culture=neutral, PublicKeyToken=null
-------------------------------------------------------
Loaded databases

You lot seem quite knowledgeable in these matters, so I'm hoping you can come to the rescue.

Thanks

Dave
 

·
Registered
Joined
·
43 Posts
I'm having a strange problem with my DiCE. I can no longer select my DiCE in the 'Communication Tool' dropdown menu, it only displays 'Not Selected', with no other available options. My DiCE shows up in the Device Manager, and the diagnostic tool reports no issues with the unit. VIDA Online 2015 can see the DiCE, and I've scanned and uploaded software using it. I've uninstalled VIDA 2014D and reinstalled, only to have the problem persist. This is a recent problem, and I had been using this DiCE with VIDA AIO for almost 2 years without a problem.

The only way I've been able to make the DiCE showup in VIDA is by deleting this registry key: 'HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PassThruSupport.04.04'. After restarting I can select my DiCE in VIDA, but can't actually use it since the driver is no longer functional.
 

·
Registered
Joined
·
1 Posts
Now tested and working as expected even on Windows 10 1703 (10.0.15063.447) Creators Update.
Hi Trixeo! Thank you very much for such a good manual. I have followed your instruction and successfully installed Vida 2014 on my laptop with Windows 10 Home. Vida starts and connects to Dice (Chinese copy) OK. I can read all the errors. Everything seems to be ok, apart from COMMUNICATION TAB where I can only select ECM module. I can not select any other green modules such as CEM and others. I click on them and nothing happens. Any ideas how to fix this? I would really appreciate your help. I use IE 11 on Windows 10. Tried everything already and no result.
Thanks!
 

·
Registered
Joined
·
2 Posts
Now tested and working as expected even on Windows 10 1703 (10.0.15063.447) Creators Update.
Have you got Vida 2014D to work with any versions of Windows 10 than 1703 (10.0.15063.447). An update to 15063.483 resulted in the Vida Monitor failing to start with the log entries:

Process java waited too long to start
Process java didn't start
 

·
Registered
Joined
·
109 Posts
Discussion Starter #235
Hi Trixeo! Thank you very much for such a good manual. I have followed your instruction and successfully installed Vida 2014 on my laptop with Windows 10 Home. Vida starts and connects to Dice (Chinese copy) OK. I can read all the errors. Everything seems to be ok, apart from COMMUNICATION TAB where I can only select ECM module. I can not select any other green modules such as CEM and others. I click on them and nothing happens. Any ideas how to fix this? I would really appreciate your help. I use IE 11 on Windows 10. Tried everything already and no result.
Thanks!
Sorry, I have no clue. Maybe it's your Chinese copy that does not do what it is supposed to do :/
 

·
Registered
Joined
·
109 Posts
Discussion Starter #236
Have you got Vida 2014D to work with any versions of Windows 10 than 1703 (10.0.15063.447). An update to 15063.483 resulted in the Vida Monitor failing to start with the log entries:

Process java waited too long to start
Process java didn't start
I have since I updated the guide last time been on 15063.414, 15063.447, 15063.483 and 15063.502 and currently on 15063.540. No issues on my machines at all. VIDA still works as expected. Did you try my guide?
 

·
Registered
Joined
·
2 Posts
I have since I updated the guide last time been on 15063.414, 15063.447, 15063.483 and 15063.502 and currently on 15063.540. No issues on my machines at all. VIDA still works as expected. Did you try my guide?
I had previously successfully installed Vida 2014D using your guide over a year ago. It was the update to 447 from an earlier subversion that caused the problem. I tried reinstalling Java without success. I guess I will have to uninstall and reinstall from scratch to get it working again. Thanks.
 

·
Registered
Volvo S60 T4 MY20 - R-Design - Bursting Blue - B&W - Polestar
Joined
·
124 Posts
Just wanted to chime in on that re-installing the Java update re-enabled VIDA on the 1703 Creators Update W10 build.
 

·
Registered
Joined
·
109 Posts
Discussion Starter #239
A guy pm'ed me asking for help. Why not ask it here? Either way, if you really have to pm me, make sure you accept pm's.
"The following errors occurred with your submission

Boli has chosen not to receive private messages or may not be allowed to receive private messages. Therefore you may not send your message to him/her.

If you are trying to send this message to multiple recipients, remove Boli from the recipient list and send the message again."
 

·
Registered
Joined
·
4 Posts
Vida installion: doinstall.3pp.components.copy.ewd.utility. Reason: Datafault CRC-Test)

Hallo,
first of all, I would like to thank the author very much for this excellent guide with respect to the installation of VIDA. Nevertheless I did not succeed. The Installation stops with the following notice (log):

**************************************************
2017-10-07 19:16:35 [INFO] [install.doinstall.3pp.components.copy.ewd.utility] [STARTED]
2017-10-07 19:19:05 [ERROR] [install.doinstall.3pp.cAomponents.copy.ewd.utility] Error: install.doinstall.3pp.components.copy.ewd.utility. Reason: Datenfehler (CRC-Prüfung)

2017-10-07 19:19:05 [ERROR] [install.doinstall.3pp.components.copy.ewd.utility] [FINISHED] [NOK] [TOTAL TIME: 00:02:30.4712307] System.IO.IOException: Datafault (CRC-test)
bei alba.core.WorkerThread.start()

2017-10-07 19:19:05 [INFO] [install.doinstall.3pp.components] install.doinstall.3pp.components.remove.ewd.readonly.attribute Never started because it's predecessor failed!
***************************************************

The subsequent errors obivously are dependant on this error. Vida does not install!

My system is : Windows 10 Pro (creators update) 64 bit
A
What can I do to get VIDA running? Any help is greatly appreciated. Thanks a lot in advance.

putput
 
221 - 240 of 390 Posts
Top