Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Update to 9.5.200 1

Status
Not open for further replies.

jbelk11

IS-IT--Management
Jan 8, 2004
57
US
I updated from ES v9.5.100 to ES v9.5.200 last evening. Everything went well on most client machines...except for 4. I received an Internal Error 2908 (along with a GUID) during the Exact CRW XI install. I cancelled out of the error, rebooted the PC, uninstalled Macola ES, rebooted again, deleted the Exact Software directory, and then installed with WSetup.

Everything seemed to go well and then Office apps began failing saying "<App> was not installed for the current user". Click OK and the app closes. Since most everyone in my organization lives in Office apps all day long, this was completely unacceptable. The Office issue was addressed (sorta) by blowing away the user's profile and recreating it.

One might question my logic that the Macola install was somehow the culprit with the office error. However, all 4 machines that experienced the installation error had the Office problem.....none of the PC's that installed correctly have exhibited the Office error.

I tried to do a search on Exact's site looking for info about the install error, but sadly, couldn't find anything.

Has anyone else run across this? I will be reformatting the 4 PC's that had trouble....just so I don't have any further Windows Installer issues.

Jen
 
The exact error was dependent on the application you were actually going into....

"Microsoft Office Outlook is not installed for the current user"

"Microsoft Excel is not installed for the current user"

etc

The GUID on the original Crystal install error was
D98A0FA7-986A-4038-BF1B-47AF50F4FF64.

Jen
 
Wow! Definitely the first I have ever heard of that one. What did Exact say on this?

Software Sales, Training, Implementation and Support for Macola, Synergy, and Crystal Reports. Check out our Macola tools:
 
Exact hasn't said anything....I have my issues with them at the moment.

I used to work for an Exact business partner which was bought out by them a couple years ago. I now work in the corporate sector for an Exact customer. We do not require a support agreement costing us 10% of our total value.

In years past, I purchased a 6 pack of support incidents that were good for 1 year. I have done this twice and both times, I did not require the use of all 6 incidents.

However, I encountered a bug last week and was told that they would no longer sell me the 6 pack of support incidents (so I could report the bug).....that the only way for me to get assistance was to a) have a consultant come out or b) pay the 10% for a support agreement.

I find that extremely short-sided on the part of Exact. What are customers like me supposed to do? I cannot justify 10% for asking less than a handful of questions a year. But yet, I cannot report any issues as serious as the one I've described either....

Jen
 
jbelk11 - I'm in the same boat as you. We are currently changing our ERP systems for all of our companies. But we still use Macola for some of them, we will move them off Macola next year. We have been without a Macola support aggreement for over a year. I have found I get better support from this site than I ever got from Macola. I think I've gotten a solution here for every query I've made. It's a lot cheaper too.
 
This is happening when exactly? When you update the workstation? Do they in fact, not have the application in question installed? Any other applications this is happening to besides Excel and Outlook?

My guess is that they don't and the workstation update is trying to install the Excel and Outlook addins for ES and it is failing because that application is not installed (or maybe you have a very old version of excel that is not compatible).

Let me know what you find out.

Software Sales, Training, Implementation and Support for Macola, Synergy, and Crystal Reports. Check out our Macola tools:
 
I am upgrading the same to 9.5.200 this friday. have you resolved this issue yet?
(we also did the same with the support contract a year ago and the same with the 6-pack). I just use occassional consulting and resolve my own bugs for the most part since they can never seem to figure anything out . I feel like their quality control dept. Bugs? don't expect any quick fixes...
Thanks all!
 
I have done several 9.5.200 updates without seeing this issue. The only problem I've encountered that is 9.5.200 specific is a payroll problem whereby employees that get paid by check end up showing as on credit during the authorization process (known problem).

Peter Shirley
Macola Consultant, PA and surrounding states.
 
Hey folks....

Sorry for the disappearing act.

The error occurs after all the files are installed and Exact Crystal XI is being configured (just before the registering of files). It has occurred on 5 of my 19 workstations. The only things common to the PC's are Windows XP SP3 and Office 2003 Professional SP3....with all updates applied. Only problem is that the other 14 PC's have the exact same software.

If the error occurs, you can get Microsoft Office functional by removing the Windows profile and setting up a new one. I went a step further and actually reformatted the PC's. No errors were encountered with the reinstall of everything.

I sent the information regarding the errors to my Account Manager at Exact....but I haven't heard a thing since the email was sent.

Jen
 
jbelk11 - did you end up rebuilding the workstations? I heard of several cases where the 200 client installation caused corruption on the workstation and the only solution was to rebuild. Exact has not acknowledged that there is a problem, however, my reseller has advised me not to install 200 at this time. I'm curious if anyone else has run into this problem.
 
kbieber....

Yes....I ended up reformatting the mucked up PC's. It was not totally required in order to get the PC operational again (see above my remarks about removing the Windows profile and then creating a new one)...but I was uncomfortable not knowing whether I removed the problem for good. I would much rather know with absolute certainty that I will not continue to have issues with a PC...so I went ahead and reformatted them.

Jen
 
Klaus,

"I heard of several cases where the 200 client installation caused corruption on the workstation and the only solution was to rebuild."

Do any of these issues occur on a terminal server?

I am (was) planning this upgrade for Nov. 8. I don't want to have to rebuild my terminal servers at the same time.

Does the 'corruption' you refer to only impact MS Office, or are there other issues?
 
Peter,

Did you install 9.5.200? Or did this problem present with the 9.5.300 upgrade.

I did my 9.5.300 upgrade two weeks ago and did not have these issues. However the only Office app that is installed on the Terminal Servers is MS Outlook 2003 SP3. The OS is Windows Server 2003 SP2.

Jay
 
Hi Jay - you'll see from my post earlier in this thread that I'd never run into this problem before when it was first posted. Last week I did an update from 372 to 9.5.300 pending a 2008 SQL and O/S upgrade. There were 3 workstations out of the 20 or so that were updated that got this error. All of the workstations that encountered this error did not have local administrative rights - the other workstations did.

Peter Shirley
Macola Consultant, PA and surrounding states.
 
Just wanted to add another report of workstation corruption. We upgraded from 9.5.100 to 300 over the weekend and several workstations did not automatically run the Macola update (out of about 40), so we ran the wsetup instead. Most updated without issue except for 3 which would not run Office apps after the Macola update was completed. The users did have local admin rights and we tried recreating profiles with no luck. Fortunately for us, we are able to re-image a PC fairly quickly, so we went that route instead of further troubleshooting, but I did at least want to corroborate the earlier incidents. For the same reasons stated above, we will not report this to Exact.
 
We had this problem last year, and have found a fix (only after rebuilding 5 machines)

You simply delete the following key in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Windows\CurrentVersion\Installer\UserData\
S-1-5-21-1123561945-1935655697-1060284298-1003\
Components\

AD95649F068525549B26938D7D18FEA7
(the key above will start with letters AD - delete it)

 
psuno1's solution is exactly what worked for us. I had 5 clean updates and 2 failed. I ran "sys resore" to get the 2 machines working again, then called Exact support. They suggested same as psuno1. I have not yet updated to ES9.5.400.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top