July 7, 2008 08:09am pdt

1. vadimrapp1 25,025
2. DatabaseMX 2,000
2. kcehtrak 2,000
4. TomasHelgi 1,800
5. Matti 1,000
6. 23637269 450
7. EDDYKT 300

1. vadimrapp1 25,025
2. jimhorn 10,100
3. emoreau 8,970
4. Shakti109 8,300
5. Sethi 7,775
6. kcehtrak 7,500
7. vinnyd79 7,450
8. AzraSound 6,775
9. TimCottee 6,770
10. mcrider 6,720
11. engelman... 6,000
12. MilanKM 5,500
13. Raisor 5,336
14. rockiroads 5,000
15. ryancys 4,800

03.31.2008 at 10:07AM PDT, ID: 23283199

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

7.1

VB Application Deployment best practices -- conflict with MS OFFICE 2007

Zones: WISE, Visual Basic Programming

Hi,

We are having an issue where running our program installer is somehow altering something in MS Office (perhaps a shared dll?) and in turn, causing the MS Office installer to run every time an office program is started.

First, has anyone heard of this or know of a fix?

Second, if it is a DLL issue, what is the best practice for deploying DLLs in our local program directory vs the System32 folder? Right now we do both.

All of our programming is in VB6, and we use a WISE installer.

Thanks,

Jon

Start your free trial to view this solution

Question Stats

Zone: Programming

Question Asked By: Allston44

Solution Provided By: vadimrapp1

Participating Experts: 2

Solution Grade: B

Translate:

Loading Advertisement...

Microsoft

Internet Protocols
Applications

Development
OS

Hardware
Windows Security

Apple

Operating Systems
Hardware

Programming
Networking

Software

Internet

Search Engines
File Sharing
WebTrends / Stats
Spy / Ad Blockers

Web Browsers
New Net Users
Web Development
Chat / IM

Anti Spam
Web Servers
Anti-Virus
Email Clients

Gamers

Tips
Online / MMORPG
Puzzle
Emulators

Action / Adventure
Role Playing
Consoles
Game Programming

Strategy
Sports
Misc
Computer Games

Digital Living

Hardware
New Net Users
New Users

Software
Digital Music
Gaming World

Home Security
Apple
Networking Hardware

Virus & Spyware

Vulnerabilities
IDS
Encryption
Anti-Virus

Operating Systems Security
Software Firewalls
WebApplications
Cell Phones

Operating Systems
Internet
Hardware Firewalls

Hardware

Handhelds / PDAs
Displays / Monitors
Components
Networking Hardware

Peripherals
Laptops/Notebooks
Storage
Servers

Desktops
New Users
Misc
Apple

Software

System Utilities
Industry Specific
Network Management
Photos / Graphics
Page Layout
VMWare
Misc
Web Development

OS
CYGWIN
Voice Recognition
Message Queue
Quality Assurance
Security
Firewalls
MultiMedia Applications

Development
Database
Office / Productivity
Business Management
OS/2 Apps
Server Software
Internet / Email

ITPro

OS
Storage
Encryption
Operating Systems Security
Apple Hardware
Laptops & Notebooks
Servers
Networking Hardware
Peripherals

Devices
Displays / Monitors
WebTrends / Stats
Search Engines
Firewalls
WebApplications
IDS
Vulnerabilities
Email Clients

File Sharing
Spy / Ad Blockers
Web Browsers
Web Servers
Networking
Anti-Virus
Chat / IM
Anti Spam

Developer

Web Servers
Web Browsers
Game Programming
Dev Tools
Industry Specific
Office / Productivity

Database
CYGWIN
Web Development
Search Engines
File Sharing
WebTrends / Stats

Programming
Content Management
Application Servers
Protocols

Storage

Removable Backup Media
Storage Technology
Servers

Grid
Remote Access
Backup / Restore

Misc
Hard Drives

Miscellaneous
Security
Development
Linux
VMWare

MainFrame OS
Unix
Apple
OS / 2
AS / 400

BeOS
Microsoft
VMS / OpenVMS

Database

Oracle
Miscellaneous
MySQL
Software
Sybase
Contact Management
PostgreSQL
Data Manipulation
Clarion
InterSystems Cache

Siebel
MUMPS
OLAP
SQLBase
SAS
GIS & GPS
4GL
Berkeley DB
DB2
Informix

Interbase / Firebird
FoxPro
Reporting
LDAP
Filemaker Pro
MS SQL Server
dBase
MS Access

Security

Misc
Web Browsers
Software Firewalls
Operating Systems Security
File Sharing

Spy / Ad Blockers
Vulnerabilities
WebApplications
IDS
Anti-Virus

Encryption
Anti Spam
Email Clients
VPN
Chat / IM

Programming

Editors IDEs
Installation
Handhelds / PDAs
Multimedia Programming
System / Kernel

Algorithms
Game
Signal Processing
Project Management
Open Source

Database
Misc
Languages
Processor Platforms
Theory

Web Development

Scripting
Blogs
Web Servers
Software
Search Engines
Web Graphics
Images

Internet Marketing
Images and Photos
Components
Document Imaging
Web Languages/Standards
Illustration
WebApplications

Fonts
WebTrends / Stats
Authoring
Digital Camera Software
Miscellaneous

Networking

Protocols
Apple Networking
Network Management
Message Queue
Application Servers
Content Management
File Servers
Email Servers
Misc
Java Editors & IDEs

Wireless
Networking Hardware
Backup / Restore
System Utilities
ISPs & Hosting
Web Servers
Storage Technology
Removable Backup Media
Servers
Broadband

Grid
OS / 2
Novell Netware
Unix Networking
Windows Networking
Security
Telecommunications
Operating Systems
Linux Networking

Other

Community Advisor
Lounge
Community Support
New Net Users

Philosophy / Religion
Math / Science
Miscellaneous
URLs

Expert Lounge
Politics
Puzzles / Riddles

Community Support

Suggestions
New to EE
New Topics
Community Advisor

CleanUp
Announcements
General

Feedback
Input
EE Bugs

03.31.2008 at 10:24AM PDT, ID: 21247332

merowinger:

have you installed multiple office versions on one computer?

03.31.2008 at 10:32AM PDT, ID: 21247396

Allston44:

Yes, there's a good possibility that multiple office versions have been installed, but they wouldn't be installed all at once, just upgraded over time. And actually, the issue seems only to occur with Office 2007.

03.31.2008 at 10:35AM PDT, ID: 21247430

merowinger:

check out this kb articel...in detail the NoReReg registry key for word!
http://support.microsoft.com/kb/928091/en-us

04.01.2008 at 07:27AM PDT, ID: 21254258

vadimrapp1:

Here's how you can find out what's going on:

open event viewer, and in the application event log find entries with event id 1001. It may or may not say what exactly is missing, that's what Installer subsequently is trying to repair, so that's what your product is damaging. If it only says what component is undetected, then you can enable detailed logging of Installer (http://support.microsoft.com/kb/223300) and after it repairs, look into the log, find the mentioned component and hopefully it will say what file or registry setting is in it.

04.02.2008 at 06:24AM PDT, ID: 21262731

Allston44:

Haven't found a solution yet. At first I thought merowinger might be right about having installed previous versions of office, but i've replicated the issue on a machine that i know has only one version of Office installed.

I tried enabling detailed logging for the installers as vadimrapp1 suggusted, but didn't see anything useful--no entries with id 1001....

04.02.2008 at 06:36AM PDT, ID: 21262837

vadimrapp1:

There must be some. Maybe with another id, also id 1004. Look for entries written by msiInstaller, with text like this:

Detection of product '{762E75A3-57CB-43CA-8ABF-9757200BAEB3}', feature 'Complete', component '{1646F159-7950-41D9-BE45-7F5B09690A58}' failed. The resource 'C:\Program Files\test\Project1.exe' does not exist.

These entries are always written when auto-repair is triggered.

Capture-04-02-00001.png (14 KB) (File Type Details)

screenshot

04.02.2008 at 06:42AM PDT, ID: 21262889

Allston44:

This might be a dumb question, but will i see these warnings when running my program installer, or the office installer?

04.02.2008 at 06:50AM PDT, ID: 21262980

vadimrapp1:

After you try to start office program, and office self-repair process is triggered. These entries show the reason it's triggered.

04.02.2008 at 08:34AM PDT, ID: 21264144

Allston44:

ah ok, i did get a few messages now:

First one of note says:

event 1025:
Product: Microsoft Office Enterprise 2007. The file C:\Program Files\Common Files\Microsoft Shared\OFFICE12\MSO.DLL is being held in use by the following process Name: OUTLOOK , Id 6076.

I'm don't really know what to make of that message, but I am sure that our installer is not touching anything in the Office12 folder.

Also, i probably should have said this before, but initially it's some sort of MS Office diagnostic screen that is triggered upon opening outlook. This in turn triggers the msinstaller, so the msinstaller event messages may not be too useful.

Along the same lines as the msintaller, Is there a similar way to see why the ms office diagnostic screen pops up?

Specifically, the window that pops up is titled "Microsoft Office Enterprise 2007", and below there is a progress bar that it says, "Configuring Microsoft Enterprise 2007..."

I'm boosting the point total to 500.

Thanks,

Jon

04.02.2008 at 08:39AM PDT, ID: 21264209

merowinger:

have you installed two outlook versions as this is not possible or supported!

04.02.2008 at 08:45AM PDT, ID: 21264274

Allston44:

Nope, just the one. Though we do have a self contained excel module that we distribute with the application (ver 2003). However, we've seen this behavior occur on computers that supposedly have the same version of office as the excel mod that we're distributing....

04.02.2008 at 12:28PM PDT, ID: 21266502

vadimrapp1:

suggestions:

1. The installation that you are distributing - is it yours? if it does not have too many files, especially in system32 as the most likely culprit, you might try removing them one by one and see when office stops self-repairing.

2. you said you are using Wise. What product exactly? installing the files side-by-side rather than in system32 might be the answer.

3. take a look at this tool: http://office.microsoft.com/en-us/help/HA012340761033.aspx . Chances are, if you run it after the installation of your program, it will detect whatever triggers Office self-repair, and tell you.

Accepted Solution

04.02.2008 at 12:32PM PDT, ID: 21266537

vadimrapp1:

...also, when you run office diagnostics, I would run filemon (sysinternals.com) to see if it generates some log file that might be examined afterwards.

20080236-EE-VQP-29 / EE_QW_2_20070628