Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Microsoft Visual C ++ Runtime Library Error
31-01-2008, 04:31 AM
Post: #1
Microsoft Visual C ++ Runtime Library Error
Hi there, we have autograph on the network, it works fine however doing a client install has given me the above error.

I have uninstalled etc but that was no help. Did a few things I found on this forum and have the standard element working but not the advanced which is what I need.

Any suggestions?

Thanks
Quote this message in a reply
31-01-2008, 02:28 PM
Post: #2
Re: Microsoft Visual C ++ Runtime Library Error
Hi,

Our apologies for the problems you are experiencing

In Order to help, I\'ll need to know what version of Autograph are you running?

kind regards
Quote this message in a reply
01-02-2008, 01:20 AM
Post: #3
Re: Microsoft Visual C ++ Runtime Library Error
Hi there - Version 3
Quote this message in a reply
05-02-2008, 06:14 AM
Post: #4
Re: Microsoft Visual C ++ Runtime Library Error
any ideas?
Quote this message in a reply
06-02-2008, 06:55 PM
Post: #5
Re: Microsoft Visual C ++ Runtime Library Error
Hi, sorry about the delay, you\'ll need to be a bit more specific about the version. If you have 3.11 or before then there\'s one fix but if you have 3.2 then its another.

Sorry about this.
Quote this message in a reply
07-02-2008, 01:41 AM
Post: #6
Re: Microsoft Visual C ++ Runtime Library Error
Sorry, it says version 3 but once i look into the properties it
says Autograph 3.20.
Quote this message in a reply
12-02-2008, 11:59 AM
Post: #7
Re: Microsoft Visual C ++ Runtime Library Error
Hi,

Well this error is usually caused by the toolbar files not having registered correctly. This seems to happen on a few networks.

For 3.20, the solution is to run regsvr32 on the 2 files found in our common files folder: for example

regsvr32.exe "c:\\program files\\Common Files\\Autograph 3\\Codejock.CommandBars.Unicode.v10.4.2.ocx" /s

regsvr32.exe "c:\\program files\\Common Files\\Autograph 3\\Codejock.DockingPane.Unicode.v10.4.2.ocx" /s

As you need to deploy this across the network, it is best done as a startup script. It doesn\'t matter if its run multiple times, so you can leave it on the script. Or you can remove it after its been run on all machines. The /s option stops it throwing up a nasty message box.

Hope this helps
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)