Posts

Showing posts from 2004

How to fix a corrupt installation of Visual Quality

I found the solution to this problem posted on the Visual Quality newsgroup the other day.

Problem: One of my users deleted Visual Quality from his computer. He did not use CONTROL PANEL, Add and remove programs to remove visual Quality. He Deleted VQ right from Program files.
Now, I would like to reinstall the Quality but as soon as I launch the installation the system gives me choice to modify, remove or repair. I did all these options but nothing happens (Since al files are deleted). I’m not able to reinstall Visual Quality. I copied all Quality files from another computer to this computer but that didn’t help either.


Solution: Open regedit and delete this key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersionUninstall{4007C318-F138-11D4-B6A3-00C04F22103D}]

When you look at this key is should have the Uninstall information. When you delete it, the setup program assumes that VQ is not installed.

Lilly's Visual Quality for Visual Enterprise Troubleshooting

If you have Visual Quality installed at your site, then you know the wonders of setting up this very picky software. The hardest part for us has been getting it to work with Visual Enterpise. Also known as Visual Manufacturing. We are currently on version 6.3.8 of VM.

Here is a list of some tips on getting VQ to work.
I'm using SQL2000, but I'm sure this will apply to all the databases that Lilly supports.

Problem: I cannot login to Visual Manufacturing as IQS. I get a error window that asks me if I want to halt or continue.
Solution: Login as SYSADM and use the USERS dialog box to delete and recreate the IQS account. Then run "Fix Synonyms and Grants". Make sure you delete/create users from Visual Manufacturing and not from the database tools that come with SQL, Oracle or SQLbase.
I have had to do this on every test database I created. It does not harm the login of IQS to other VM/VQ databases. Remember, changing the password in one VM database will change it in …

Installing Visual Enterprise 6.3.8 to co-exist with version 5

Installing Visual 6.3.8 to co-exist with version 5

Install the new version of Visual 6.3.8 to the default locations.
Those default locations are:
C:\Program Files\Centura
C:\Program Files\Vmfg

When prompted for the location to install the config files enter the path to vmfg.
C:\Program Files\Vmfg

After everything is installed open regedit and delete this key:
HKEY_CURRENT_USER\Software\Lilly Software\VISUAL Manufacturing\Configuration\Local Directory

If this key is left in the registry then the old version of visual will try to get it’s serial number from the new version of Visual.

Installing SLQ 2000 Reporting Services after XP SP2 will kill your PC!

I just found out that the SQL 2000 Reporting Services support files overwrite some critical files that XP Sp2 updated.
It replaced two system32 files dated 8/4/2004 with older ones dated 10/8/2003 and hosed my system.
After I rebooted it went into a loop of almost getting to the login screen, but then rebooting the machine. Crash!
READ: Unbootable.So if you install XP SP2 before RS, make sure you backup these files before you run the RS setup replace the files BEFORE a reboot.
I ran the install followed by RS Sp1 and then replaced the files and everything was fine.These are the files from the system32 directory:
msvcp60.dll
msvcrt.dll

All of this is on my workstation. If you install XP SP2 after RS you would be fine of course.. that is unless later you pop in the CD to install the test database!

FYI
I had to kill MSDTC in the process list before it would let me replace msvcp60.dll.

Unattended Removal of the Oracle 8i Client

This week I'm working on the removal of the Oracle 8i Client, but found that something was locking core40.dll so that I could not delete the ORANT folder.
I went to www.systernals.com and got listdlls.exe to help track down what was locking that dll.
Turns out it was SMS 2003.
I repackaged the uninstall of the Oracle Client. This cleaned up the registry, but I had to do some work before I could delete the files from c:\ORANT.
After the package deleted all the reg keys I ran a batch file that used listdlls.exe to find the PID (process) that was holding core40.dll. Then I had SMS stop the service for CcmExec.exe and kill it's parent process svchost.exe. Then I was able to delete the ORANT folder.




Unattended Installation of Microsoft Fax Services

Today I setup a Fax Server on Microsoft Server 2003 and need to create a SMS 2003 package to setup all the XP workstations to install Fax Services and then install the network fax printer.

My examples can be downloaded here: http://www.cadjobs.net/blog/add-fax.zip

My first problem was to change the install path for XP so that when the fax services installed that it would not request that the user install the XP CD into the CD-ROM. I added UNC path to a share where I have the XP SP2 i386 files into the registry to fix that problem. Here is the location of that key:

HKEY_LOCAL_MACHINE
Key=SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
New Value=\\data\msi\xp
Value Name=SourcePath

Then I created an SMS Package (the SMS installer script is included in the above zip file) that started the Fax Services installer and then installed the network printer after that. Here are the details:

This installs the Fax Services.
SYSOCMGR.EXE /i:%windir%\inf\sysoc.inf /u:%temp%\install-fax.txt

Make sure …