Error 429 - but not in development
- From: "Richard Cole" <googlegroups@xxxxxxxxx>
- Date: 31 Jan 2006 08:52:53 -0800
I've been tearing my hair out for the last 2 weeks trying to get a
program to install.
It's a fairly simple bit of code linking a mainframe system to the
in-house telephone system so that the mainframe can originate calls and
any incoming calls get the caller's number passed back to the
mainframe. It is compiled with VB6 Sp5 and uses comdlg32.ocx and 3
third party OCXs (none of which require a run time licence according to
their suppliers), see the vbp which follows.
When this is installed on either an in-house 'standard' build NT PC or
a on very simple NT PC created in a Virtual PC (the only 2
non-development NT boxes I have available to me) the program, when run,
produces the error message "You do not have an appropriate license to
use this functionality".
There are lot's of fixes available for when this message occurs in the
development environment (which it doesn't) but none for when it occurs
in a runtime environment.
I've tried the following:
Re-registering every OCX and tried rerunning the program between each
re-registration.
Running VBC6.exe (aka VB6cli.exe).
Running vbctrls.reg.
Running VBC6 on the development PC and recompiling, repackaging and
reinstalling.
None of these work.
I know that the program isn't even starting as the 1st thing it does is
to write a log file line of *'s and no log file has been created and I
inserted a msgbox as the very first line of the program, so it seems
that the program isn't even launching.
No events significant events are recorded in the event viewer log
files.
Help. I need this to be installed by Friday (when UAT starts) and first
it has to be packaged, which takes about a day.
***** vbp content *****
Type=Exe
Reference=*\G{00020430-0000-0000-C000-000000000046}#2.0#0#C:\WINNT\System32\stdole2.tlb#OLE
Automation
Object={F9043C88-F6F2-101A-A3C9-08002B2F49FB}#1.2#0; comdlg32.ocx
Object={6DCBF49D-A918-11D6-B4E7-0004ACB243C3}#1.0#0; PROHOSTCONTROL.OCX
Object={C1561A4B-7001-11D3-99AA-0004ACB243C3}#1.1#0; CONPROTODIAL.OCX
Object={44F1CB13-B34B-11CF-B48E-0020AF300B7D}#7.4#0; abcon32.ocx
Form=frmStartup.frm
Form=frmSplash.frm
Form=frmLogin.frm
Form=frmTerminate.frm
Module=modATif; modATif.bas
Form=frmAbout.frm
IconForm="frmStartup"
Startup="frmStartup"
HelpFile=""
Title="Aspect Target Interface"
ExeName32="AspectTargetIF.exe"
Command32=""
Name="AspectTargetIF"
HelpContextID="0"
Description="Aspect Target Interface"
CompatibleMode="0"
MajorVer=1
MinorVer=2
RevisionVer=0
AutoIncrementVer=0
ServerSupportFiles=0
VersionComments="Connects Aspect telephones to Target Result software."
CompilationType=0
OptimizationType=0
FavorPentiumPro(tm)=0
CodeViewDebugInfo=0
NoAliasing=0
BoundsCheck=0
OverflowCheck=0
FlPointCheck=0
FDIVCheck=0
UnroundedFP=0
StartMode=0
Unattended=0
Retained=0
ThreadPerObject=0
MaxNumberOfThreads=1
[MS Transaction Server]
AutoRefresh=1
****** End of vbp content *****
.
- Follow-Ups:
- Re: Error 429 - but not in development
- From: J French
- Re: Error 429 - but not in development
- Prev by Date: Connection to sql server database
- Next by Date: Re: Error 429 - but not in development
- Previous by thread: Connection to sql server database
- Next by thread: Re: Error 429 - but not in development
- Index(es):
Relevant Pages
|
