Just a moment...

[coljay]

Hi,

Just Downloaded the free version to give a try again, but on opening it kind of hangs on the "just a moment" screen then fails to load saying i should try later. I've tried a few times waiting 10-15 mins between in some cases and it still does the same.

any ideas how to fix?

I'm running windows 7 ultimate 64bit OS on an i7 with about 6gig of ram if that's useful.

Thanks

[Semper Vaporo]

your use of the word "again" implys that you have tried it once before. if so, there is the possibility that the last usage left some files on the disk that the latest installation is finding and they may be corrupt... kind of depends on how the previous version was last shut down and how it was removed or how thoroughly it was removed.

I'd recommend that you do an uninstall of the new version ("Control Panel" -> "Programs and Features", Right- click on "Vitamin D Video" and click "Uninstall" in the context menu that appears). After the uninstall is complete, look for left over files in the following places: (I hope I remember all the places to look! )

C:\Program Files (x86)\Vitamin D Video
C:\Users\{your user ID}\AppData\Local\Vitamin D Video

If either of those folders still exist, I think you should delete them completely.

Then re-install Vitamin D Video from scratch.

You will have to redefine your video camera and such, but that is not all that hard in VDV (especially the free version since you can only have 1 camera... it is a bit tedious to have to redefine a whole bunch of cameras, but I got really good at it for a while there when I had a problem PC!)

I hope this helps. If not, come back here and I am sure one of the VDV techs will have a better answer for you.

[coljay]

hi,

thanks for your reply. yeah - i had downloaded the app before and liked what i had, but then my pc blew up so i had to re-install. I've tried installing and uninstalling a few times, also deleted some files from the user profile as suggested, but unfortunately it still doesn't load .

I am using NTFS junction points to re-point my user profile off of my SSD and onto my fixed disk. Could this have something to do with it? I know that some windows updates dont seem to like that setup, but as yet haven't found any apps with the same issue.

Any more suggestions i could look at?

Thanks

[doug]

coljay,

That sounds strange to me. Something is interfering with the startup process or with the communication of the different parts of Vitamin D Video. Are there any log files in the locations that Semper refers to? Sometimes looking at those can be a hint in cases like this one.

-Doug

[coljay]

Hi,

just managed to get back to trying this again. I've re-pointed my registry etc to see the physical location of my profile etc, but still no joy. Looking in my profile and the vitamin d logs it is complaining about an incorrect volume syntax. Sounds like it either still doesn't like where my profile is - or maybe is having trouble with my RAID setup? I'm a bit clueless really.

Have attached log files.

Any help appreciated.

Vitamin D Log:

2011-10-22 16:53:34,701 - INFO - r6168xw_1005221.pyo - OnInit - Starting Vitamin D Video...
2011-10-23 21:45:06,618 - INFO - r6168xw_1005221.pyo - OnInit - Starting Vitamin D Video...
2012-01-19 23:57:36,888 - INFO - r6168xw_1005221.pyo - OnInit - Starting Vitamin D Video...
2012-01-19 23:58:56,321 - INFO - r6168xw_1005221.pyo - OnInit - Starting Vitamin D Video...
2012-01-19 23:59:58,614 - INFO - r6168xw_1005221.pyo - OnInit - Starting Vitamin D Video...
2012-01-20 00:04:18,500 - INFO - r6168xw_1005221.pyo - OnInit - Starting Vitamin D Video...
2012-01-20 00:09:37,223 - INFO - r6168xw_1005221.pyo - OnInit - Starting Vitamin D Video...
2012-01-20 00:22:34,548 - INFO - r6168xw_1005221.pyo - OnInit - Starting Vitamin D Video...
2012-01-20 00:24:38,084 - INFO - r6168xw_1005221.pyo - OnInit - Starting Vitamin D Video...
2012-01-20 00:27:23,417 - INFO - r6168xw_1005221.pyo - OnInit - Starting Vitamin D Video...

BAckend App:

2012-01-20 00:31:58,466 - ERROR - r6168xw_1002z2l.pyo - main - Unhandled exception
<type 'exceptions.WindowsError'>: [Error 123] The filename, directory name, or volume label syntax is incorrect - r6168xW_1002Z2l.pyo(1582); r6168xW_1002Z2l.pyo(215); __init__.pyo(218); queues.pyo(36); __init__.pyo(111); connection.pyo(189)
2012-01-20 00:31:58,467 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,467 - INFO - r6168xw_1002z2l.pyo - __del__ - Beginning back end shutdown
2012-01-20 00:31:58,467 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,471 - INFO - r6168xw_1002z2l.pyo - run - Starting the back end, pid: 2192
2012-01-20 00:31:58,473 - ERROR - r6168xw_1002z2l.pyo - main - Unhandled exception
<type 'exceptions.WindowsError'>: [Error 123] The filename, directory name, or volume label syntax is incorrect - r6168xW_1002Z2l.pyo(1582); r6168xW_1002Z2l.pyo(215); __init__.pyo(218); queues.pyo(36); __init__.pyo(111); connection.pyo(189)
2012-01-20 00:31:58,473 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,473 - INFO - r6168xw_1002z2l.pyo - __del__ - Beginning back end shutdown
2012-01-20 00:31:58,473 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,476 - INFO - r6168xw_1002z2l.pyo - run - Starting the back end, pid: 2192
2012-01-20 00:31:58,476 - ERROR - r6168xw_1002z2l.pyo - main - Unhandled exception
<type 'exceptions.WindowsError'>: [Error 123] The filename, directory name, or volume label syntax is incorrect - r6168xW_1002Z2l.pyo(1582); r6168xW_1002Z2l.pyo(215); __init__.pyo(218); queues.pyo(36); __init__.pyo(111); connection.pyo(189)
2012-01-20 00:31:58,476 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,477 - INFO - r6168xw_1002z2l.pyo - __del__ - Beginning back end shutdown
2012-01-20 00:31:58,477 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,480 - INFO - r6168xw_1002z2l.pyo - run - Starting the back end, pid: 2192
2012-01-20 00:31:58,482 - ERROR - r6168xw_1002z2l.pyo - main - Unhandled exception
<type 'exceptions.WindowsError'>: [Error 123] The filename, directory name, or volume label syntax is incorrect - r6168xW_1002Z2l.pyo(1582); r6168xW_1002Z2l.pyo(215); __init__.pyo(218); queues.pyo(36); __init__.pyo(111); connection.pyo(189)
2012-01-20 00:31:58,482 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,482 - INFO - r6168xw_1002z2l.pyo - __del__ - Beginning back end shutdown
2012-01-20 00:31:58,482 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,486 - INFO - r6168xw_1002z2l.pyo - run - Starting the back end, pid: 2192
2012-01-20 00:31:58,486 - ERROR - r6168xw_1002z2l.pyo - main - Unhandled exception
<type 'exceptions.WindowsError'>: [Error 123] The filename, directory name, or volume label syntax is incorrect - r6168xW_1002Z2l.pyo(1582); r6168xW_1002Z2l.pyo(215); __init__.pyo(218); queues.pyo(36); __init__.pyo(111); connection.pyo(189)
2012-01-20 00:31:58,486 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,486 - INFO - r6168xw_1002z2l.pyo - __del__ - Beginning back end shutdown
2012-01-20 00:31:58,486 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,492 - INFO - r6168xw_1002z2l.pyo - run - Starting the back end, pid: 2192
2012-01-20 00:31:58,492 - ERROR - r6168xw_1002z2l.pyo - main - Unhandled exception
<type 'exceptions.WindowsError'>: [Error 123] The filename, directory name, or volume label syntax is incorrect - r6168xW_1002Z2l.pyo(1582); r6168xW_1002Z2l.pyo(215); __init__.pyo(218); queues.pyo(36); __init__.pyo(111); connection.pyo(189)
2012-01-20 00:31:58,492 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,492 - INFO - r6168xw_1002z2l.pyo - __del__ - Beginning back end shutdown
2012-01-20 00:31:58,493 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,496 - INFO - r6168xw_1002z2l.pyo - run - Starting the back end, pid: 2192
2012-01-20 00:31:58,496 - ERROR - r6168xw_1002z2l.pyo - main - Unhandled exception
<type 'exceptions.WindowsError'>: [Error 123] The filename, directory name, or volume label syntax is incorrect - r6168xW_1002Z2l.pyo(1582); r6168xW_1002Z2l.pyo(215); __init__.pyo(218); queues.pyo(36); __init__.pyo(111); connection.pyo(189)
2012-01-20 00:31:58,497 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,497 - INFO - r6168xw_1002z2l.pyo - __del__ - Beginning back end shutdown
2012-01-20 00:31:58,497 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,502 - INFO - r6168xw_1002z2l.pyo - run - Starting the back end, pid: 2192
2012-01-20 00:31:58,503 - ERROR - r6168xw_1002z2l.pyo - main - Unhandled exception
<type 'exceptions.WindowsError'>: [Error 123] The filename, directory name, or volume label syntax is incorrect - r6168xW_1002Z2l.pyo(1582); r6168xW_1002Z2l.pyo(215); __init__.pyo(218); queues.pyo(36); __init__.pyo(111); connection.pyo(189)
2012-01-20 00:31:58,503 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,503 - INFO - r6168xw_1002z2l.pyo - __del__ - Beginning back end shutdown
2012-01-20 00:31:58,503 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,507 - INFO - r6168xw_1002z2l.pyo - run - Starting the back end, pid: 2192
2012-01-20 00:31:58,507 - ERROR - r6168xw_1002z2l.pyo - main - Unhandled exception
<type 'exceptions.WindowsError'>: [Error 123] The filename, directory name, or volume label syntax is incorrect - r6168xW_1002Z2l.pyo(1582); r6168xW_1002Z2l.pyo(215); __init__.pyo(218); queues.pyo(36); __init__.pyo(111); connection.pyo(189)
2012-01-20 00:31:58,509 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,509 - INFO - r6168xw_1002z2l.pyo - __del__ - Beginning back end shutdown
2012-01-20 00:31:58,509 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,513 - INFO - r6168xw_1002z2l.pyo - run - Starting the back end, pid: 2192
2012-01-20 00:31:58,513 - ERROR - r6168xw_1002z2l.pyo - main - Unhandled exception
<type 'exceptions.WindowsError'>: [Error 123] The filename, directory name, or volume label syntax is incorrect - r6168xW_1002Z2l.pyo(1582); r6168xW_1002Z2l.pyo(215); __init__.pyo(218); queues.pyo(36); __init__.pyo(111); connection.pyo(189)
2012-01-20 00:31:58,513 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,513 - INFO - r6168xw_1002z2l.pyo - __del__ - Beginning back end shutdown
2012-01-20 00:31:58,515 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,519 - INFO - r6168xw_1002z2l.pyo - run - Starting the back end, pid: 2192
2012-01-20 00:31:58,519 - ERROR - r6168xw_1002z2l.pyo - main - Unhandled exception
<type 'exceptions.WindowsError'>: [Error 123] The filename, directory name, or volume label syntax is incorrect - r6168xW_1002Z2l.pyo(1582); r6168xW_1002Z2l.pyo(215); __init__.pyo(218); queues.pyo(36); __init__.pyo(111); connection.pyo(189)
2012-01-20 00:31:58,519 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,519 - INFO - r6168xw_1002z2l.pyo - __del__ - Beginning back end shutdown
2012-01-20 00:31:58,519 - INFO - r6168xw_1002z2l.pyo - cleanup - Back end cleanup complete
2012-01-20 00:31:58,526 - INFO - r6168xw_1002z2l.pyo - run - Starting the back end, pid: 2192
2012-01-20 00:31:58,528 - ERROR - r6168xw_1002z2l.pyo - main - Unhandled exception
<type 'exceptions.WindowsError'>: [Error 123] The filename, directory name, or volume label syntax is incorrect - r6168xW_1002Z2l.pyo(1582); r6168xW_1002Z2l.pyo(215); __init__.pyo(218); queues.pyo(36); __init__.pyo(111); connection.pyo(189)

and so on.... (45K rows there of )

[ryan]

Is there anything special about your RAID setup or windows install? Is it local or remote? Are you running any special disk management software, or anti-virus/firewall software?

[coljay]

Hi,

RAID is standard raid 5 on 3 disks, using intel rapid storage management software, standard install as far as i am aware. I have redirected a few folders off my initial windows install drive, as i said earlier on. Specifically - i have moved the C:\Users, C:\Program Files\ and C:\Program Files (x86) off the SSD and onto a standard hard drive and have used NTFS junction points to redirect the folders.

I am also running Avast! anti-virus and have tried both with and without it running.

Thanks

Col

[ryan]

Hi Col,

I am definitely not an NTFS expert, but reading some errata it appears that there can be problems with certain command line operations (simple things like move) and that some behavior with regard to junction points is different across the various versions of windows. I have a windows 7 machine I will get running and see if I can reproduce this purely with the junction points, though the problem might also lie with a specific combination of the junctions and drive crossing.

[coljay]

Hi Ryan,

I seem to have fixed this now, although i'm not 100% sure how as i now can't reproduce the issue. It seems to have stemmed from the fact my %TEMP% env variable was pointing at "E:\". changed it to "E:\Temp" (note no trailing backslash) and it seemed to start. I changed the variable back and it still works, so i'm not too sure if i'm barking up the wrong tree or not.

Incedently i found this by accident. I was trying to install "Origin" from EA, and it kept complaining about not being able to find a cache folder or something. Made the above changes and it started working. I then thought i'd try the same thing with VitaminD, and hey-presto it worked. Whether there have been some other Registry tweaks i've performed that also helped, i'm not sure. Now all is initialised though, i cant seem to break it again which is weird.

Thanks

Col

[Semper Vaporo]

It is possible that there was a non-printable character in the data for the Temp variable and when you retyped it the character got overwritten. It could also be that some pointer was corrected while updating the variable and that cured the problem.

Glad it is working for you!