Lỗi none of specified aped databases are accessible năm 2024

Please show me the errors while i installed hysys 7.3. When opening the "Aspen Hysys", it appeared two consequential notice as following:

"None of specified APED databases are accessible. Hence you can not use Aspen Properties Enterprise Database"

And

"To use Aspen Properties in Hysys, at least one databank should be installed and registered through Aspen Properties database configuration tool"

Hope to receive your reply as soon as possible.

Thanks very much

Viettan Khuu

Fletch

Fletch

Veteran Member

• Members
• 40 posts

Posted 28 November 2013 - 03:38 AM

Hi Viettan,

I think i recall these warnings/errors, the Aspen properties database one annoyed me.

But what i recall the errors didn't stop HYSYS from running properly, as the errors were not directly impacting hysys.

I can't exactly recall what i did to get the errors to go away but i will try and give you some pointers.

Run a program called "Aspen Properties Database Manager". From the Start menu, head into the Aspentech folder, "Process Development V7.3" then "Aspen Properties" and then choose the program.

I think i just had select a database here.

Or in the same start menu folder, there is a program called "Aspen Properties Database Selector" maybe select here.

Sorry i cant recall exactly what i did, but hoping that this prompts someone elses recollections of this issue

Fletch

Fletch

Veteran Member

• Members
• 40 posts

Posted 18 December 2013 - 01:17 AM

Ironically, i had a colleague have this exact issue last week.

He was getting the same errors (i.e. the APED errors etc) , but underlying condition was that the token/license server wasn't getting configured through the SLM Config.

In the configuration process the registry was not getting updated with SLM server details, so we brute forced the actual registry keys required. HYSYS would then run, but the errors persisted.

Trying my suggestions above didn't show any fruit. As we were not able to select a database to get going.

One of our fall back plans to sort out the SLM, was to redo the install, but as administrator.

Our services guys, ended up taking that idea to try and sort out the APED errors, by running the "Aspen Properties Database Manager" as administrator and he was able select the database, which in turn cleared the error.

So in short, try running the "SLM Configuration Wizard" as administrator, this should allow the application to actually write to the registry

And run "Aspen Properties Database Manager" as administrator to select the properties database.

What i found interesting is that an error didn't really spit out from the SLM config program saying that it was unable to write to the registry, it didn't do its normal routine, but said it was successful (where you could see it wasn't)

Aspen Troubleshooting: Database issues

Errors include:

• Aspen may not start, giving a message that databases need to be repaired.
• Aspen gives improper property info on components, or can not find components at all. Cause:

When you run Aspen, it creates a folder at C:\ProgramData\AspenTech\APED V11.0\[unityid] and copies the database files there. These are the properties databases that Aspen uses when you run the program. However, sometimes these databases are corrupted somehow, resulting in the above errors. AspenTech is aware of this issue. They do not provide information on what would cause this, but they provide two solutions: delete and re-create your databases, and if that doesn’t work, restore them using the Aspen Database Tester.

Troubleshooting method 1: Delete the databases

1. The first step is to quit Aspen, log out of Windows, and log back in. This ensures that no Aspen utilities/files are running in the background.
2. Once logged back in, do not run Aspen yet. First delete the folder at C:\ProgramData\AspenTech\APED V11.0\[unityid]
   1. If you are on a computer where you have permission, like a grad student desktop, you can manually delete that folder. (Note that the ProgramData folder is hidden, but you can get to it by typing %programdata% in the address bar and pressing Enter. This will take you into the folder, and you can browse from there.)
   2. On WVD, we have put a script on the desktop that does the same thing.
      1. Run the Fix Aspen Properties Databases link on the desktop.

              ![](https://https://i0.wp.com/it.engr.ncsu.edu/software/wp-content/uploads/sites/31/drive/11Pv2jSCT2MzfRdIjYFyVUGAD9P92jAVu/aspen_ts_03.png)  

      2. A window will appear regarding security. Click More info. ![](https://https://i0.wp.com/it.engr.ncsu.edu/software/wp-content/uploads/sites/31/drive/1mZ1RZC7sQsU17Xygs0OXg6KVDJTKVdMK/aspen_ts_04.png)
      3. Click Run anyway. ![](https://https://i0.wp.com/it.engr.ncsu.edu/software/wp-content/uploads/sites/31/drive/1BwN4lEAC38NWOCBn7Rs1NXAvDNd2QXe6/aspen_ts_05.png)
      4. The folder will be deleted, and a window will appear with the below message. ![](https://https://i0.wp.com/it.engr.ncsu.edu/software/wp-content/uploads/sites/31/drive/1WDoGNAI7MLlJtGq4V_ZN9rF6jft2dW_M/aspen_ts_06.png)
      5. Try running Aspen again and see if the problem has been resolved. Troubleshooting method 2: Restore databases using Database Tester
3. If the above method did not work, quit all Aspen components again, log back out, and back in as in the above method.
4. Once logged back in, do not run Aspen yet. First, open the Aspen Database Tester utility by going to Start Menu > Aspen Properties > Database Tester – Aspen Properties V11
5. Click Restore databases directly at the bottom of the window, the click Yes on the prompt that appears.
6. Aspen will begin restoring the databases. This will take a few minutes.
7. When that is complete, you should see a window as below. Click OK to close.
8. Try running Aspen again and see if the problem has been resolved.