Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

The Project could not be opened, Database context does not exit or invalid

Created by: tyleong at: 10/29/2014 10:24 PM (10 Replies)

Rating (0)

Thanks 1

Result pages:: |; 1 | 2; |

11 Entries

Entries per page: 10 | all

10/29/2014 10:24 PM	Rate (0)
tyleong Posts: 10 Rating: (0)	Hi, I have a problem to download OS from ES, the message show " The Project could not be opened, Database context does not exit or invalid". I also cannot find my OS from the simatic shell from ES and vice versa.. At the Station configuration i also unable to find the OS server station. but I able to ping the address from ES to OS and also OS to ES. Please the attachment Any hero can help? Thanks a lot Attachment OS download Error .JPG (1015 Downloads)
tyleong Posts: 10 Rating: (0)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users AutoGen_5444499

10/30/2014 12:28 PM	Rate (0)
Ralfinio Posts: 567 Rating: (107)	Hi, please check if user name and pass word are the same on both PC stations. If OS is not in the same subnet check if you have configured a multicast proxy in the settings of the SIMATIC Shell. Please check if the network adapter which is used for the terminal bus on fist place in the advanced network settings (windows). You can also find some more points to check under the following link: http://support.automation.siemens.com/WW/view/en/33123686
Ralfinio Posts: 567 Rating: (107)
Suggestion To thank Quote Answer

10/30/2014 1:55 PM	Rate (0)
tyleong Posts: 10 Rating: (0)	Thanks Ralfinio, the username and password are same on both station. and also the multicast in simatic shell was set to 1. Do you think that maybe a problem for the network adaptor? Regards, Tyleong
tyleong Posts: 10 Rating: (0)
Suggestion To thank Quote Answer

10/30/2014 2:12 PM	Rate (0)
Ralfinio Posts: 567 Rating: (107)	Hi, the network settings should be configured as descripted in PCS 7 compendium part a (chapter 3.3.6) http://support.automation.siemens.com/WW/view/en/63187279 Isthe os server the same subnet? If not than you have to add multicast proxy in the SIMATIC Shell. To get more information about the multicast proxy press the help button in SIMATIC Shell.
Ralfinio Posts: 567 Rating: (107)
Suggestion To thank Quote Answer

11/3/2014 2:53 PM	Rate (0)
tyleong Posts: 10 Rating: (0)	Hi, Those stations are using the same subnet. what I curious is ES simatic shell can see the Batch server, and OS simatic shell can see the Batch Server too. But ES simatic shell and OS simatic shell cannot see each other.why? thanks
tyleong Posts: 10 Rating: (0)
Suggestion To thank Quote Answer

11/3/2014 5:57 PM	Rate (0)
RugbyGuy Silver Expert Joined: 1/15/2009 Last visit: 4/19/2024 Posts: 316 Rating: (40)	Please see the following link. You must check everything on this list, as it may be 1 or a few things causing this issue. https://www.automation.siemens.com/tf/WW/en/Posts/79008#top good luck
	The best location for all PCS 7 content (manuals, guides, application notes, FAQs, and videos). https://support.industry.siemens.com/cs/ww/en/view/63481413
Suggestion To thank Quote Answer

6/27/2020 2:32 PM	Rate (0)
travis128154 Regular Member Joined: 8/15/2018 Last visit: 5/4/2023 Posts: 3 Rating: (0)	good morning, Im having some issues with an OS download, a multi station system project one es/os client and OS server and AS. issue is every time i go and make an OS download i get error The project could not be opened. Database context does not exist or is invalid. I have windows file sharing enabled on both machines, I can clearly ping and see both machines on the network and simatic shell and shared folder pathway is selected?? any thoughts utilizing pcs7 v9sp1 windows 10 ltsb 2015 and windows server 2016 (Also there is no password protection over both machines) -Cheers Travis

Suggestion To thank Quote Answer

6/28/2020 5:18 PM	Rate (0)
JazTai Gold Member Joined: 9/9/2015 Last visit: 11/12/2024 Posts: 728 Rating: (280)	Dear travis128154, Please follow my step here to check your system 1. Ping check using computer name from ES to OS and OS to ES, eg. Ping computername If this failed, please check your host file. Run this command "nbtstat -c" , ensure all the entry are correct. 2. win+r -> lusrmgr.msc , ->User -> look for your device specific account (window logon account) -> right click-> member role-> ensure "SIMATIC HMI" is there for OS Server and OS Client and ensure "SIMATIC NET" in OS Server For ES, ensure SIMATIC NET, SIMATIC HMI, Siemens TIA Engineer in the ES Windows Logon group. 3. Check the Target OS path folder -> at the local station-> ensure the project folder is shared and permission is given -> right click at the folder-> properties-> sharing -> tick the sharing -> add the SIMATIC HMI into the folder permission. And next tab -> Security -> add SIMATIC HMI -> tick read/write access. 4. check OS Server Station configuration. ensure the station configuration is healthy. If step 1-3 cannot help, I will continue to explain the station config. Hope this is helpful for you.
	Please give me 5 stars Rating if my post is helpful for you. :) Thank you for Rating! Control System Manager Jaz Tai , Linde Gas Singapore PCS 7 Complete Overview PCS 7 Technical Documentation
Suggestion To thank Quote Answer

9/26/2021 10:37 PM	Rate (0)
adriyan Member Joined: 11/10/2020 Last visit: 11/25/2022 Posts: 1 Rating: (0)	The Project could not be opened, Database context does not exit or invalid In my project, I only had to write logic on the ES computer, and in the monitoring OS, which I am currently having this problem with, can anyone show me the settings with a photo because my problem was not solved from the MANUAL.

Suggestion To thank Quote Answer

12/20/2021 1:57 PM	Rate (0)
AutoGen_9419844 Member Joined: 9/5/2020 Last visit: 10/8/2024 Posts: 1 Rating: (0)	Este SCADA no deja de sorprenderme con errores poco lógicos y sin sentido. Con los desarrollos se pierde demasiado tiempo intentando descifrar este tipo de errores.

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on