Import error: No module named project

[Claus_Nielsen]

A single client raises the import error on client start up. I have a client start up script using a function from a project library, however it seems to be missing on one client. This is the startup script that fails

import project # Was just a tiny hope it would help
from project.core.smartcardio import CreateDefaultProxCardReader

# Start the prox card reader in its own background thrad.
CreateDefaultProxCardReader().StartBackground()

The script currently fails in line 1 at the first import.

Any ideas anyone?

[Claus_Nielsen]

Hmm, changing the publish mode from manual to auto solves the issue. If changed back to manual the problem starts again.

[pturmel]

@Claus_Nielsen

from project.core.smartcardio import CreateDefaultProxCardReader

Don't do this. Don't import anything from shared.* or project.*. Your startup script should be one line:

project.core.smartcardio.CreateDefaultProxCardReader().StartBackground()

See this for more explanation:

Some Project Resources not publishing

This may be a side-effect of the fact that Ignition doesn’t/can’t track the usage and retention of python code objects throughout the gateway. This means that when your script modules have interlocking dependencies, updating one script won’t impact the code objects that other scripts have imported. You may need to make a trivial change in all of your scripts and save them all together to get it to “take”. You may also need to disable then re-enable the entire project. Consider renaming the o…

[Claus_Nielsen]

It was originally, those two imports was just a try to resolve the issue.
And they are not there anymore. The error persists if the publish mode is in manual.

[pturmel]

Please show the failure details. And anything ahead of it in the console log.