Topic
FlexPro displays multiple error messages when starting up
Startseite ' Community ' Allgemein ' FlexPro displays multiple error messages when starting up
- Dieses Thema hat 2 Antworten sowie 2 Teilnehmer und wurde zuletzt vor vor 21 Jahren, 9 Monaten von Richard Weisang aktualisiert.
-
AutorBeiträge
-
07.08.2003 um 23:18 Uhr #34299Richard WeisangAdministrator
When I start FlexPro I see the following error messages:
[img]/aspnetforums/SupportFiles/Images/CannotLoadSYSTATImport.png[/img]
[img]/aspnetforums/SupportFiles/Images/CannotLoadSPSSImport.png[/img]
[img]/aspnetforums/SupportFiles/Images/CannotLoadSEFRAMImport.png[/img]
FlexPro seems to work despite of the errors. What is the reason for the messages?
08.08.2003 um 00:10 Uhr #34297Richard WeisangAdministratorWhen I start FlexPro I see the following error messages:
[img]/aspnetforums/SupportFiles/Images/CannotLoadSYSTATImport.png[/img]
[img]/aspnetforums/SupportFiles/Images/CannotLoadSPSSImport.png[/img]
[img]/aspnetforums/SupportFiles/Images/CannotLoadSEFRAMImport.png[/img]
FlexPro seems to work despite of the errors. What is the reason for the messages?
08.08.2003 um 00:10 Uhr #34298Bernhard KantzTeilnehmerWhen FlexPro is started all modules in [path]System[/path] are loaded, where [path][/path] is the FlexPro installation path, normally [path]C-Program FilesFlexPro 6.0[/path]. Some of the module require additional DLLs – that are present in the System folder too – especially the ones given in t8 error messages above.
Due to the strategy which is used by Windows when starting an application the [path]System[/path] folder must be in the path for FlexPro.EXE, when FlexPro is started (otherwise only the folder [path][/path] is searched for the additional DLLs.If one or more of the above error messages occur one of the following issues could be the reason:
[ul][li]installation of FlexPro failed[/li][li]the application path for FlexPro was overwritten by a later installation of FlexPro to a different folder (could also be FlexPro 5.0)[/li][li]FlexPro is started not from the machine where it is started[/li][/ul]To fix this issue there are two possible solutions:
[ul][li]If you do not need the SPSS-, SYSTAT- and/or SEFRAM-Import you can delete the following files in [path]System[/path]:[/li][/ul][ol][li]SEFRAM-Import: SeframImport.dll, SEFRAMRecorderImport.dll[/li][li]SPSS-Import: SPSSImport.dll, spssio32.dll[/li][li]SYSTAT-Import: SYSIO32.DLL, SYSTATImport.dll[/li][/ol]
[ul][li]If you need the import filter proceed as follows:[/li][/ul][ol][li]Run REGEDIT.[/li][li]Navigate to the key [path]HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrent VersionApp PathsFlexPro.EXE[/path].[/li][li]Edit the string value [b]Path[/b] and set it to the following value: [path];System[/path][/li][li]Close REGEDIT[/li][/ol]
Afterwards when starting FlexPro no error should occur. -
AutorBeiträge
- Du musst angemeldet sein, um auf dieses Thema antworten zu können.