Access Runtime Language Problem

[Roger Trewenack]

Hi there,
We've had a database developed, and I then used Office XP Developer to
create an Access Runtime to distruibute to all our company PC's. They run a
variety of Win98SE thru WinXP-SP2. All PC's have the language set to English
(Australian).
In most cases this has worked just fine, and the resultant package has
installed OK on PC's.
However, there was initially one Win98SE PC where the package would not
install, stating that "The Office System Pack cannot be installed on this
system because the languages are not the same. Install the Office System Pack
for the appropriate language on your computer. For assistance, contact your
application provider."
That didn't cause too much of a drama, but now I find that some of the
latest Windows XP-SP2 PC's with Office 2003 are having the same problem.
I ahven't been able to find anything helpful in TechNet, perhaps someone in
the Discussion group can help, please??

Regards

 

[Gerald Lindinger]

Hi Roger

I have a similar problem. But in my case I have 5 new PC with preloaded
Windows XP SP2 (Language setup German-German) and NO Office Product
installed, and there I have the same error.

Till now it worked on PC with W98, W2000, XP SP1. It also works on my
developement PC with XP SP2 (but this is a MSDN XP-SP1 Version, and I
installed SP2 by myself), so it seems to be not a basical "SP2" Problem.

In the meanwhile I posted it in several newsgroups, but got no answer.

Gerald

 

[Tom]

Hi

Encountered the same problem with OfficeXp Developer about 3 years back.
Having talked to MS tech suport it appeared that the problem appears to be
that when Developer produces the runtime version it uses the US English
language code and when you try install to a pc, and the default language
code is not US English, you will get that error message. What we were
advised to do was to change the default language codes, on the pc that you
want to install the package on, to US English and after the installation
re-set same to original settings.

Hope this helps

Tom

 

[Gerald Lindinger]

Hi Tom

Thanks, I tried this already, but this did not help. I am not sure, but I
think, the problem is not in the developer runtime installation package,
because it worked most times in the past with the same language settings on
the destination PCs ???
But on the new XP-SP2 PCs this problem occurs, even with the same language
settings. Anyway I changed it on the destination PC to US English and to
several other languages with no success.

Gerald

Hi

Encountered the same problem with OfficeXp Developer about 3 years back.
Having talked to MS tech suport it appeared that the problem appears to be
that when Developer produces the runtime version it uses the US English
language code and when you try install to a pc, and the default language
code is not US English, you will get that error message. What we were
advised to do was to change the default language codes, on the pc that you
want to install the package on, to US English and after the installation
re-set same to original settings.

Hope this helps

Tom

 

[Tom]

Gerald

possibly a very long shot but on the problem pc is Control Panel/Regional
SettingsAdvanced also set to US English?

Tom

Hi Tom

Thanks, I tried this already, but this did not help. I am not sure, but I
think, the problem is not in the developer runtime installation package,
because it worked most times in the past with the same language settings
on
the destination PCs ???
But on the new XP-SP2 PCs this problem occurs, even with the same
language
settings. Anyway I changed it on the destination PC to US English and to
several other languages with no success.

Gerald

 

[Gerald Lindinger]

Hi Tom

- Access Runtime Installation created on PC with language "German/German".

- Till now: about 30 Destination PC (W2k-XP SP1), language setting in the
ContolPanel has been "German/German": Runtime Installation worked..

- Now I have 5 preinstalled new destination PC with XP SP2, language setting
in the ContolPanel is "German/German": Runtime Installation did not work..

So I changed on this destination PC the language to "US English", but with
no success too, same error message. I tried some other languages like
"German/Austria" (because i am from Austria), but with no success too ???

What I did not mention at all: On one of this 5 PC I installed the complete
XP-Developer version, then I made a new Access Runtime Package and tried to
install this new Runtime-package on this 5 new PCs: It did not work, same
error message !! Also on that PC with the installed developer version !!! I
cannot understand that !

Thanks
Gerald

 

[Aerin]

O, my friends! I have exactly the same problem! I am so glad I am not along.

I have two computers where we resolved the problem by re-installing Windows
XP with all possible check boxes checked ON. And we were able to install it
there. Windows version - Wnidows XP-SP2 HOME Edition

2other computers - Win XP Professional SP2 - nothing could help.
Re-installed coupl times, no way, nothing is working

I will be more than happy to resolve it. Any ideas?

 

[Tom]

Gerald
what language is set on the advanced tab?

Tom

 

[Tony Toews]

However, there was initially one Win98SE PC where the package would not
install, stating that "The Office System Pack cannot be installed on this
system because the languages are not the same. Install the Office System Pack
for the appropriate language on your computer. For assistance, contact your
application provider."

Some other solutions someone contributed were as follows:

2) Manually run "osp.msi" which is included in the runtime directory
of the deployment cd. This effectively upgrades the users machine in
the same way that the installation routine should. After the osp.msi
file has installed, you can then run the setup routine again and the
fault will not occur.

3) Type mismatch error while installing a localized MS-Access 2000
application
http://www.inventec.ch/chdh/notes/9.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Gerald Lindinger]

Hi Tony

In my case it did not work:

======== ad 2)
"Manually run osp.msi which is included in the runtime directory"

Doing this I got the error message (Sorry - translation from germany):

"There are no system files to update on this PC, to execute MS Office
Proffesional with Frontpage. Systemfiles update cannot be started on this PC"

and then

"The installation was prematurely cancelled due an error"

====== ad 3)
"Type mismatch error while installing a localized MS-Access 2000 application
http://www.inventec.ch/chdh/notes/9.htm"

This did not apply to my "setup.lst". The values in this file has been
correct.

Thanks
Gerald Lindinger

 

[Gerald Lindinger]

Hi Tom

On the advanced Tab the setting was German/Austria. Based on your mail I set
now all language parameters in the Control Panel Regional
Settings/Advanced to the same languages:

1) German or German/Germany

-> Here I got I new error mesage: "The office system pack cannot be
installed on this system, because it need Windows NT4.0 SP6 or higher" (?? it
was Windows XP SP2!)

2) English or English/US

The same as before: "The Office System Pack cannot be installed on
this system because the languages are not the same. Install the Office
System Pack for the appropriate language on your computer."

Thanks
Gerald

 

[Aerin]

Hi Gerald,

Probably, I could help you with the second message about NT pack:

http://www.kbalertz.com/kb_837150.aspx

Please, keep me posted if you find the way how to resolve the problem. I
have this problem on any new computer now

Regards,
Aerin

 

[Roger Trewenack]

Hi Tony, and thanks for your response, which was partially successful.
Maybe Gerald & Tom & Aerin can glean something from this too:

I first tried it on a Windows XP-SP2 PC running Office 2003 SBE - It failed
with the following:
"This system does not require any system file updates to Microsoft Office XP
Professional with FrontPage: the System Files Update will not run on this
computer"

So here we have a situation where the "Windows" on the target PC is ahead or
equal to the "Windows" on the Development PC.....any ideas?

Secondly, I have just tried your suggestion on another PC - Win98SE running
Office XP SBE (I know that's not a recommended combination!) and it worked
successfully.

So this second situation is where the "Windows" on the target PC is behind
the "Windows" on the development PC

Thirdly, I have tried it another PC - WinXP-SP2 running Office 2000 Pro,
where it failed, in the same way as the first......

Sounds like Win-XP-SP2 is contributing to the confusion..........?????

Regards,

Roger T.

 

[Aerin]

I did it! I don't have Win 98 computers, so osp.msi doesn't helps at all. We
have new customers and they have all new computers with Win XP SP2 already
installed and it was a nightmare. My message was exactly the same like
Gerald's message.

I was using all suggestions together.
- First, I installed SP2 for Win XP on my comp
- I installed all updates that it is possible to install including SP1 for
Office XP Developer Edition.
- I put English language for Unicode (on advanced tab in regional settings).
I know all my customers will use this Unicode language only
- I removed in the Ospfilelist.txt file, the line that contains the
Dbmsadsn.dll and Saved this file.
- I created the package after all, with runtime and also I included system
components (you know the second check box after runtime)

We sent the package to the customer on CD and Thanks God! today we received
the answer. It works So, I am still alive and going to sleep well this
night.

 

[Gerald Lindinger]

Hi Aerin

Thanks !! Your link

http://www.kbalertz.com/kb_837150.aspx

was the solution in my case. I removed in the Ospfilelist.txt file, the line
that contains the Dbmsadsn.dll, saved this file and made a new package. This
worked !!

Thanks to Tom, Roger and Tony too for the help !!

Gerald

 

[Roger Trewenack]

Thanx to Gerald, and Aerin - A bit delayed but your fix worked today - I have
happy users again.
What a great forum!!!

 

[Sahar]

Thanks everyone for this forum. I encountered the same error message with the
Windows NT 4.0 Service Pack 6 problem and looks like the article will do the
job!