Search This Blog

Here I will blog my daily efforts as a System Admin and hope that others will find answers here to problems that I already found the solutions for. I work with Hyper-V, DPM, SCCM, Office, Infopath, SQL Server, SQL Reporting Services, SharePoint, Windows Servers, Windows 10 and the 3CX PBX.

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 all the others too.

Problem: The link to Visual Quality does not work from within VM. (Under Eng/Mfg)
Solution: Login as SYSADM and open Application Global Maintenance. Click on the last tab called "Defaults". In the Visual Quality area the path should look something like this: c:\visual\vqMake sure the database name is correct and do not include vq.exe on the end of the path.

Problem: I cannot access Application Global Maintenance from within VQ.
Solution: Make sure you are logged in as IQS.

Problem: I created a test database and copied the VQ database from my live production database, but now VQ will not startup when I try to load it from my test database.
It says I must be running VM first and I am!
Solution: Inside of the VQ Application Global there is a place to specify the VM database. Your copied VQ database is still pointing to the production database. You need to open your production database in VM, change the Application Global Maintenance to point to the new test VQ database, login now to the VQ database as IQS and change the database name in Application Global to match your test database. When your done you will need to go back to the production VM database Application Global Maintenance and change the VQ database name back to what it was.

Problem: I cannot get the Reports to install in VQ.
Solution: Make sure you use UNC paths to the server and that you have created a share on the server so that everyone can access the reports. The path should look something like this:
"\\vmserver\visual\vq\My Reports\"
"\\vmserver\visual\vq\Quick Reports\"
Click on refresh and then Install. Make sure you have the "\" on the end of the path.

Comments

Popular posts from this blog

It's that time again! Time to add your Office 2016 KMS Keys to your Volume Activation Server!Yes, I forgot how to do it too.. so here are my notes for doing it.

If you are missing the KMS keys from the MVLSC for office 2016 then you need to contact Microsoft at KMSADD@microsoft.com to get your MAK key converted to KMS.If you want to call them, use this number: (866) 230-0560 Here is the format of my email to them:

When you get your KMS keys, then you are ready to download the update from the Microsoft Volume Licensing Service Center (VLSC) that will allow you to activate the KMS on your Server. Look for "Office Professional Plus 2016 Key Management Servi…

I had a few Hyper-V 2012 R2 hosts that didn't want to talk to my VMM 2012 R2 server, so I started down the long road of tracking down the problems. Sorry if some of this seems disjointed or out of order. I'm trying to document this all after a week of troubleshooting errors.

Here is my advice for tracking down the problems. Most are related to WinRM.

Step 1: Check the Health status of the HostTo check the Health status of a host, perform the following steps: 1. Open the VMM Console.2. Select the Fabric view, right-click the host that’s experiencing issues and chose properties. 3. Within the host properties, select Status. 4. Select the category that has the Red exclamation to view the error details. In my case, the third category down was WinRM that was giving me an error.

Lets start with the easy stuff.Make sure WMI is working...net start winmgmtIf you think the WMI repository is corrupted, you could try this:winmgmt /salvagerepositoryThere is more detail on fixing WMI here:http:/…

2. Go to the Volume License Service Center and see if you already have KMS keys.If your using Server 2012 R2 (2008 R2 is not supported for Windows 10 KMS) you will need to get a KMS key called "Windows Srv 2012R2 DataCtr/Std KMS for Windows 10".In VLSC - click License, then Relationship Summary. Now click the License ID of your current Active license. Once the page changes, click Product Keys. Scroll down the list and look for "Windows Srv 2012R2 DataCtr/Std KMS for Windows 10" If you are missing the KMS keys from the MVLSC then you need to contact Microsoft at KMSADD@microsoft.com to get your MAK key converted to KMS.You will need 2012R2 with SA to get this Special KMS key.…