Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 Can't install 1446

You must be registered to post a reply.
Click here to register.

Screensize:
UserName:
Password:
Format: BoldItalicizeUnderlineStrikethrough Align leftCenterAlign right Insert horizontal ruleUpload and insert imageInsert hyperlinkInsert email addressInsert codeInsert quoted textInsert listInsert Emoji
   
Message:

Forum code is on.
Html is off.

 
Check to subscribe to this topic.
   

T O P I C    R E V I E W
obirsoy Posted - Jun 15 2006 : 12:36:58 PM
Hi,
Install for 1446 just stops responding at the end (It reads File:VAssist.dll, the progress bar seems complete.). I tried installing Symantec Antivirus Autoprotect disabled, it didn't affect the outcome.

I have VC7.1, VC8.0 and VA1445 installed. After ending the process (cancel does not work) I can not start neither visual studio's. After disabling VAssistNET addin (from registry) I can start both Visual Studios. uninstalling VA stops responding as well. Installing 1445 back seems to work.

Note: 1552 fails the same way as 1446.

VA_X.dll file version 10.2.1445.0 built 2006.04.12
Licensed to:
VA X: [email protected] (1-user license) Support ends 2006.06.23
VA.NET 7.1:
VAOpsWin.dll version 1.3.2.4
VATE.dll version 1.0.4.15
DevEnv.exe version 7.10.3077.0
msenv.dll version 7.10.3077.0
Font: Courier New 15(Pixels)
Comctl32.dll version 5.82.2900.2180
WindowsNT 5.1 Build 2600 Service Pack 2
2 processors

Platform: Win32
Stable Includes:
c:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\include;
c:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\include;
c:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\PlatformSDK\\include\\prerelease;
c:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\PlatformSDK\\include;
c:\\Program Files\\Microsoft Visual Studio .NET 2003\\SDK\\v1.1\\include;
C:\\Development\\include;

Library Includes:
c:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\src\\mfc;
c:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\src\\atl;
c:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\crt\\src;

Other Includes:

18   L A T E S T    R E P L I E S    (Newest First)
feline Posted - Oct 11 2006 : 4:07:15 PM
i have just downloaded and installed "cvsnt" (doing a standard install) under win2k and rebooted, as the installer required.
this has installed u3dapi10.dll to "C:\\Program Files\\CVSNT\\"

VA 1538, 1532 and 1446 all install perfectly happily for me.

is there some step that I have missed?
patria Posted - Sep 27 2006 : 12:49:58 AM
quote:
Originally posted by Stone

Can you tell us how can you find the real problem (u3dapi10.dll)?
Thanks


I used windbg in Debugging Tools for Windows for troubleshooting. When DLL modules are loaded, I found a deadlock and found out that u3dapi10.dll can be a problem.
Stone Posted - Sep 27 2006 : 12:03:32 AM
I also experience the same problem. I can't fix it until I read this topic. Patria, can you tell us how can you find the real problem (u3dapi10.dll)?
Thanks
bugfix Posted - Jul 06 2006 : 01:46:04 AM
Is it possible that this dll is listed in:
HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Windows\\AppInit_DLLs ?
pwaugh Posted - Jul 06 2006 : 01:28:03 AM
quote:
Originally posted by sean

Can anyone confirm that the behavior is different with build 1528?



With 1528, I was only able to install with the WinCVS file u3dapi10.dll renamed u3dapi10.dll.disabled.

However, it scares me just a bit that I have to do such a thing to allow your software to install. With the .dll renamed, it seems to run (the tips came up).

And, I just confirmed that it works once I rename the .dll back.

Now, instead of having played with your software for 4 or 5 hours, I have spent it just getting it installed, and now I'm off to bed.

Patrick
sean Posted - Jul 05 2006 : 8:36:49 PM
Can anyone confirm that the behavior is different with build 1528?
sean Posted - Jun 16 2006 : 6:53:14 PM
thanks for the confirmation - we're looking into it...
patria Posted - Jun 16 2006 : 5:09:02 PM
As I suspected, it seems like DLL loader problem. Even DllMain of VA_X.dll does not seem to be called. DllMain of u3dapi10.dll may be the problem.

D:\\Program Files (x86)\\Visual Assist X>testRegDll.exe
Attempting load...

(no response, I killed testregdll.exe from taskmgr)

D:\\Program Files (x86)\\Visual Assist X>ren ..\\CVSNT\\u3dapi10.dll u3dapi10.dll.disabled

D:\\Program Files (x86)\\Visual Assist X>testRegDll.exe
Attempting load...
Loaded
Calling DllRegisterServer...
Called DllRegisterServer
Unloading...
Unloaded


sean Posted - Jun 16 2006 : 5:00:30 PM
Could either of you try the following please?
Download http://www.wholetomato.com/downloads/testRegDll.exe
Put the file in your VA installation directory.
Open a console window.
Run testRegDll and let me know how far it gets (the u3 file named properly and with either 1446 or 1522 installed).
obirsoy Posted - Jun 16 2006 : 3:12:55 PM
It didn't do the trick.
regsvr32 vassistnet.dll --> this showed the succeeded dialog box.
regsvr32 va_x.dll --> this did not do anything. It just returned to the command line. No error msg etc.
regsvr32 vapkg.dll --> this showed the succeeded dialog box.
devenv /setup --> did not report anything either.

Starting VC7.1 still failed.
But I tried patria suggestion to rename u3dapi10.dll (I have cvsnt client installed). The install is succeeded and VC7.1 looks like its running.

If I rename u3dapi10.dll back to its original name, VC7.1 stops running again. Currently I am investigating what happens to cvs if it can not find this dll.
patria Posted - Jun 16 2006 : 2:58:12 PM
I found the real problem for this.
Deadlock is from "u3dapi10.dll". I renamed the u3dapi10.dll to disable it and now setup works fine.

u3dapi10.dll is included in cvsnt from www.march-hare.com or
if you bought u3 smart drive (www.u3.com) and installed the software from them.

It seems like DLL loader deadlock.
patria Posted - Jun 16 2006 : 2:47:32 PM
Do so manually:

regsvr32 vassistnet.dll --> this works
regsvr32 va_x.dll --> INDEFINITE WAITING (still seems like a deadlock)
regsvr32 vapkg.dll --> this works

sean Posted - Jun 16 2006 : 2:20:14 PM
Vassist.dll is only used by vc6, so if it fails to reg, that shouldn't affect your vs2003 install. But it might mean that the other dlls did not register.

Do so manually:
regsvr32 vassistnet.dll
regsvr32 va_x.dll
regsvr32 vapkg.dll
devenv /setup (to get the refactoring commands registered in the IDE)

Should also confirm that all the dlls did in fact get updated...
obirsoy Posted - Jun 16 2006 : 11:54:42 AM
quote:
Originally posted by support

Orhun: Do you have 64-bit Windows XP?

Can other people with 64-bit Windows XP install successfully?


No, I don't have 64-bit XP. patria and I must have something else in common. Is there anything else I can do? For example I can try to register VAssist.dll from the command line with extra options so that I can report more information.

But I have a release coming next week, so my responses will take time.

Thanks.
Orhun Birsoy
support Posted - Jun 16 2006 : 11:31:15 AM
Orhun: Do you have 64-bit Windows XP?

Can other people with 64-bit Windows XP install successfully?
patria Posted - Jun 15 2006 : 6:41:15 PM
I experience the same problem with my 64-bit Windows XP.
I did some experiments and found out that self-registration code in vassist.dll is an evil. It seems to wait indefinitely for some synchronization object (WaitForSingleObject?) in OS.

Hence, I gave up installing 1446 and 1552 on my system.

obirsoy Posted - Jun 15 2006 : 3:47:20 PM
Restarting before an install didn't seem to do anything. I also did a reboot after ending the install process, to see if VS will work, but it didn't. Thanks for the tip though...

Orhun Birsoy
support Posted - Jun 15 2006 : 1:37:28 PM
On a whim, you might try rebooting before the install.

© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000