Unicode font
pe...@alexsoft.com
ever resolved?
I've just migrated an application from PB9 to PB11, and all
seemed fine. built and released as p-code. When a user
starts the application on his PC, which he is not an admin
for, he gets the following error.
"PowerBuilder failed to change the Unicode font
substitution. You must run at least once with administrator
privileges to complete this process."
I don't want every user to have to run once as
administrator. I will also never care about making this app
multi-lingual.
I've tried searching for this in google and PB Help, but
can't find anything. Can anyone provide a little direction?
Chris Pollach
What O/S version was that deployed to where this error happened?
--
Regards ... Chris
ISUG - NA RUG Director
http://chrispollach.pbdjmagazine.com
<pe...@alexsoft.com> wrote in message
news:2a964881-287e-4334...@2g2000hsn.googlegroups.com...
jorge....@gmail.com
> Peter;
>
> What O/S version was that deployed to where this error happened?
>
> --
> Regards ... Chris
>
> <pe...@alexsoft.com> wrote in message
>
> news:2a964881-287e-4334...@2g2000hsn.googlegroups.com...
>
>
>
> > somebody entered this on Sept 9 - I was wondering if this issue was
> > ever resolved?
>
> > I've just migrated an application from PB9 to PB11, and all
> > seemed fine. built and released as p-code. When a user
> > starts the application on his PC, which he is not an admin
> > for, he gets the following error.
> > privileges to complete this process."
> > I don't want every user to have to run once as
> > administrator. I will also never care about making this app
> > multi-lingual.
> > I've tried searching for this in google and PB Help, but
>
> - Show quoted text -
We have encountered this same problem in Windows XP SP2 and Windows
Vista when we migrated to PB11.5 (PB 11.2 did not have this problem).
I have contacted Sybase and logged case #11479501. They were not
aware of this issue previously. I am awaiting information from Sybase
Engineering and I will let you know if I hear anything further on this.
jorge....@gmail.com
>
> - Show quoted text -
Sybase has referred this to engineering as CR545778. The work around
is that PowerBuilder is looking for the following registry entry:
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT
\CurrentVersion\FontSubstitutes\PB Sans Serif
which needs to be set to Tahoma or Ariel.
On my PC it was set to Tahoma.
MAVERICK
> On Oct 1, 11:20 am, jorge.herr...@gmail.com wrote:
>
>
>
>
>
> > On Sep 26, 10:11 am, "Chris Pollach" <cpoll...@travel-net.com> wrote:
>
> > > Peter;
>
> > > What O/S version was that deployed to where this error happened?
>
> > > --
> > > Regards ... Chris
> > > ISUG - NA RUG Directorhttp://chrispollach.pbdjmagazine.com
>
> > > <pe...@alexsoft.com> wrote in message
>
> > >news:2a964881-287e-4334...@2g2000hsn.googlegroups.com...
>
> > > > somebody entered this on Sept 9 - I was wondering if this issue was
> > > > ever resolved?
>
> > > > I've just migrated an application from PB9 to PB11, and all
> > > > seemed fine. built and released as p-code. When a user
> > > > starts the application on his PC, which he is not an admin
> > > > for, he gets the following error.
> > > > privileges to complete this process."
> > > > I don't want every user to have to run once as
> > > > administrator. I will also never care about making this app
> > > > multi-lingual.
> > > > I've tried searching for this in google and PB Help, but
> > > > can't find anything. Can anyone provide a little direction?- Hide quoted text -
>
> > > - Show quoted text -
>
> > We have encountered this same problem in Windows XP SP2 and Windows
> > Vista when we migrated to PB11.5 (PB 11.2 did not have this problem).
> > I have contacted Sybase and logged case #11479501. They were not
> > aware of this issue previously. I am awaiting information from Sybase
> > Engineering and I will let you know if I hear anything further on this.- Hide quoted text -
>
> > - Show quoted text -
>
> Sybase has referred this to engineering as CR545778. The work around
>
> My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT
> \CurrentVersion\FontSubstitutes\PB Sans Serif
>
> which needs to be set to Tahoma or Ariel.
>
>
> - Show quoted text -
I have similar problem when I try to migrate PB 7 application to PB
11.5.
Question is,
Creating/Setting the registry key to Arial or Tahoma... Does it solve
the problem....?
Even after setting the registry key as recommended, I still have the
problem.
Reply appreciated.
-Boopathy.
MAVERICK
>
> - Show quoted text -
Creating the 'New String Value' in registry in the above location as
follows solves the problem.
PB Sans Serif = Tahoma (.....worked for me in Windows Vista).....
Other thoughts,
When will it be the time, the whole World can think 'Out
of Windows'........ It is happening in Tacos. "Think Outside the Bun".
Thanks, Jorge...
jorge....@gmail.com
>
> - Show quoted text -
I received this note from Sybase. They state that the font
substitution problem has been fixed in the latest EBF (though it is
not listed in set of bug fixes). I haven't had a chance to verify
yet. Here's their note:
"Engineering just posted PowerBuilder 11.5 EBF 16345 (build 3050) on
the Software Express
web site (http://downloads.sybase.com).
CR545778 - Unicode Font Substitution error is included in this EBF"
KevinGe...@gmail.com
>
> - Show quoted text -
I downloaded PowerBuilder 11.5 EBF 16345 (build 3050). I recompiled
the app under PB11.5 after installing the ebf and rebooting my PC.
Some of my XP users still get Font Substitution message. This EBF
does not fix this problem.
cbri...@gov.mb.ca
>
> - Show quoted text -
I can confirm this. I did a moved up to build 3050. Rebuilt my
application. And I still get the error message.
If they know what the problem is why do they not fix it. I have a
large user community which I can not go to each machine and perform
updates on the window registry or log in as admin and launch the
application once.
Man!
cbri...@gov.mb.ca
>
> - Show quoted text -
Oops... this problem is in fact fixed in 11.5 EBF 16345 (build 3050).
When I rebuilt my application using this version of powerbuilder I did
not update my runtime dlls with the most current (when you upgrade to
build 3050 you will see the runtime dlls modification dates change
from August 2008 to October 2008).
Therefore, I grabbed a new copy of the runtime dlls and added them to
the deployment package and problem solved.
God Speed my fellow developers!