Service Name appears with RT Project in dev mode but not while deployed

[elibarber]

Exactly as the title says, I have had no network problems with this project for the last several months.

If i run the my main.vi while on my PC the service name appears. When i do a clean build of the project and deploy it. The service name is missing from dumpinfo. what can I do?

[wsimpson0050]

Can you confirm that the application is deployed on the target by going to the targets Dependencies -> New -> Real-Time Application

And then go to Source Files -> Select the VI you want to run on startup and click build 

Some other recommendations would be to:

1.) Verify Service Locator on Target:

Use NI MAX or SSH to confirm that the Service Locator is enabled and running on the RT target.

2.) Include Service Registration in Startup VI:

Ensure the code that calls 'TCP Create Listener' and registers "superboy" runs in the Startup VI and is included in the build specification.

3.) Static vs Dynamic Ports:

If possible, assign a fixed port instead of 0 to avoid dynamic port issues.

[elibarber]

wsimpson0050.

Yes i have the Main VI set as startup. I think I need to keep my Main as the entry point of my program, as it contains all other VIs.

The TCP listener is in the "Network Engine.vi".

I know the is enabled and running because i can visit port 3580/dumpinfo? ( in my case "http://10.0.5.83:3580/dumpinfo?") and the service names appear. all except "superboy"

The reason why I am using a service name and port 0 is because it auto assigns a port. This has actually worked for me in the past. I actually have another project running multiple service names. This project has been running for several months without any issues.

[wsimpson0050]

I would try to log the error that is happening while the system is deployed by saving the error to a text file. I would also just try to specify the port and use a timeout of 1000ms (or replace the 'TCP Create Listener' with the 'TCP Listen.vi'). 

[elibarber]

I am at a complete loss, I cant get anything to log. Its like 

even within the main vi if there is a single error on initialization then its logged to the same directory...

Nothing when I try to browse it.

[elibarber · Accepted solution]

UPDATE: Sometimes when we are at our lowest, we find the solution.

Creating a new build spec (not copying the old one) solved the issue. No idea why.