Yes, after 2 years driving around with a CEM I finally got vida working again. I tried many fixes but only got it to boot up once, something about system clock out of sync , then it failed when I tried again. Followed this video carefully and it worked. Rebooted the laptop and it still works so I think its solved. Finally, thanks a million.
What a guy. i spent a week getting the right setup and installing everything right only to find it would not log in. followed this and BOOM fully working. Your a star thank you very much
I hope you are still around... I have the exact same issue, but IM missing the C:/VIDA/VIDA folder hence no license etc. I ran the installer succesfully ran the patch also copied the patch to the C:/VIDA/ folder and ran it from there, but there is simply no VIDA subfolder... any idea where the license file could be hidden else ? search inside the VIDA folder doesnt reveal any files named "license"
In my case I had also to adjust the security options of the internet/intranet of the "Internet Options" down to a minimum and disable the protection mode just below the adjustment bar of the above options.
Doesnt work for me. Followed the exact steps, did not work. Looked into filldb cmd file and it seems there are problems with the path/s !? Previously installed and patched VIDA 2014D in c:\vida etc, installed the patch in c:\vida and then c/p into the main Vida... Changed license, stopped/restarted the service, does not work. I re-edited the filldb file to the direct patch paths and now I seem to get the following error (and cannot find where this line is): " Program Filessqlq null is not a recognizable command etc". Help ?
On Windows 7 x64 issue persisted, because when I started the filldb.cmd I get: C:\VIDA\patch>filldb.cmd The system cannot find the path specified. So I edited the file - filldb.cmd like this: @echo off set lic='c:\VIDA\patch\license' echo %lic% set sqlf=c:\VIDA\patch\q.sql echo %sqlf% set fdb=c:\VIDA\patch\filldb.sql echo %fdb% echo declare @lic nvarchar(50) set @lic=%lic% > %sqlf% type %fdb% >> %sqlf% "C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\OSQL.EXE" -S localhost\Vida -U sa -P GunnarS3g3 -i %sqlf% > nul del %sqlf% ren %VIDA_HOME%WslLogin.exe WslLogin.exe.bak 2> nul ren %VIDA_HOME%ClientLogger.exe ClientLogger.exe.bak 2> nul Issue was resolved!
Need to modify path in filldb.cmd according your Win7 installation as OSQL.exe tool may be located under ProgramFiles(x86) directory. You may issue SQLCMD -L under Windows command prompt in order to be sure your Vida Sql instance is running. Be sure to copy patch under ../Vida/patch before as it is where the script is going to execute various patched files. Patch objective is to modify Vida Sql database. @echo off set lic='%VIDA_HOME%patch\license' set sqlf=%VIDA_HOME%patch\q.sql set fdb=%VIDA_HOME%patch\filldb.sql Set Sqlroot=Microsoft SQL Server echo declare @lic nvarchar(50) set @lic=%lic% > %sqlf% type %fdb% >> %sqlf% "%ProgramFiles(x86)%\%Sqlroot%\100\Tools\Binn\OSQL.EXE" -S localhost/VIDA -U sa -P GunnarS3g3 -i %sqlf% > nul del %sqlf% ren %VIDA_HOME%WslLogin.exe WslLogin.exe.bak 2> nul ren %VIDA_HOME%ClientLogger.exe ClientLogger.exe.bak 2> nul Worked like a charm after I modifing orginal script.
ha ha, no i haven't put it anywhere, i think it is just a unprofessional work, but THANK YOU for a compliment. Nice to hear some one else like it too...
This method doesn't work for me. Do I need to install the patch on C: / VIDA on C: / before installing it? Does DICE have to be connected to the OBD2 socket?
Viss aizgāja. 1) Izdzēsu patch mapi un VIDA mapi; 2) Izslēdzu VIDA; 3) No šī linka paņemu patch: blog.buyobdii.com/how-to-solve-volvo-vida-dice-2014d-error-cant-log-in/ 4) Ieinstalēju C diskā (C:\)
Yes, I saw that. I originally installed the patch to "C:". But after I installed it to "C:/VIDA" I saw patch folder and license file, however after editing the license file with notepad, it still did not work. I eventually installed a different patch that I found online, and that FIXED the problem. Thanks for the help though!
Probably you have, like me, in your fildb.sql script the wrong path to OSQL.exe Change "c:\program files (x86)\Mircrosoft SQL Server\" to "c:\program files\Microsoft SQL server.\....." with notepad. And run Filddb script again.
