Forecasting using SAS Forecast Server, SAS/ETS, and more

SASEFAME Interface Engine Error

Reply
N/A
Posts: 0

SASEFAME Interface Engine Error

Hi,

I'm trying to read a FAME database (.db) and I'm using this example: http://support.sas.com/rnd/app/da/new/801ce/ets/chap3/sect13.htm.

I get an error message, saying:
ERROR: SASEFAME found but not loadable.
ERROR: OPERATING SYSTEM 126 ERROR OCCURED.

Any help is appreciated,

Thanks.
N/A
Posts: 0

Re: SASEFAME Interface Engine Error

The first question is whether this has ever worked on this machine. If it hasn't, then one has to consider install problems and issues such as required path specification may not have been met. A number of similar notes exist on the Support site.

I suggest looking at the documentation relating to the installation and ensure this has been met. If it has, then this is more likely to be an issue for Technical Support who have access to a much wider knowledge base.


On the other hand, if it has worked until recently and has now failed after some change or upgrade, then look at what changes were made and ensure changes to the PATH system variable or similar have not been made.

Kind regards

David
N/A
Posts: 0

Re: SASEFAME Interface Engine Error

Thanks David,

This is the first time I try to read a .db file so I guess this never worked before on my machine. I'll have a look at the other things you suggested,

Cheers,
D.
N/A
Posts: 0

Re: SASEFAME Interface Engine Error

I agree that the Microsoft OS errors can be hard to track sometimes, the reuse of some number ranges for specific modules can make diagnosis difficult.

However, in one article on MSDN, OS error 126 is defined as ERROR_MOD_NOT_FOUND, where MOD is an abbreviation for module.

Couple this with the page full of reports on support.sas.com that link OS errors and the incorrect path or system variable defining locations of modules and I'll wager there is some system variable or path definition you need to complete for this to work. Searching all relevant documentation should guide you to some installation requirement that is yet to be met. If it doesn't, Tech Support will have or will find exactly the answer you need.


In passing, two things are worth commenting on: one of the SAS Support notes refers to OS error nnn not 126, which means more than one error code has been produced. So when you search the SAS site, don't always expect hits on the error number. Windows is an arcane art sometimes, as I implied with my comment on error tables above.

The second point is that if it has never been made to work, then this isn't the result of installing some other piece of software you'll need to uninstall. This is GOOD news, since updates and patches by Microsoft on Windows have an often deserved reputation for causing more grief than they are worth. Mind you, I have seen a couple of anti virus packages commit some horrid acts on update as well, so it is the OS that probably has some critics to answer, rather than the patch distributor.

Good luck in finding your missing install option.

Kind regards

David
Ask a Question
Discussion stats
  • 3 replies
  • 702 views
  • 0 likes
  • 1 in conversation