Native client error in 7.7

We have one instance where Windows native client cannot connect to the server. The Windows native client works for our other servers on both 7.7 and 7.6.

Basic error shows in red on launcher as “Exception during project info download: Gateway is unavailable (http status code 500, Server error)”

But of course the gateway is up and running.

Increasing the log level shows the following in the log. Anything else that we can check on the server in question to resolve the issue? bad argument for IP_MULTICAST_IF2: No IP addresses bound to interface
at Method)
at Source)
at Source)
at com.inductiveautomation.ignition.client.nativelaunch.ui.GatewayConfigPanel$MulticastReceiver.doInBackground(
at com.inductiveautomation.ignition.client.nativelaunch.ui.GatewayConfigPanel$MulticastReceiver.doInBackground(

Some network adapters don’t support multicast, even though they say they do. That is the multicast error you are seeing. However, that error is not related to your project download problem. Normally a 500 error is an exception that got thrown on the Gateway. Are there any Gateway errors that can be posted here?

The problem is in getting the project list. I had to issue the URL manually to see the error.

HOST:8088/main/system/projectlis … IVersion=2


Problem accessing /main/system/projectlist. Reason:

Server Error

Caused by:

at com.inductiveautomation.factorypmi.gateway.FPMIGatewayHook$VisionLaunchHandler.getLaunchDescriptor(
at com.inductiveautomation.ignition.gateway.servlets.ProjectListServlet.doGet(
at javax.servlet.http.HttpServlet.service(
at javax.servlet.http.HttpServlet.service(
at com.inductiveautomation.ignition.gateway.bootstrap.MapServlet.service(
at org.eclipse.jetty.servlet.ServletHolder.handle(
at org.eclipse.jetty.servlet.ServletHandler.doHandle(
at org.eclipse.jetty.server.handler.ScopedHandler.handle(
at org.eclipse.jetty.server.session.SessionHandler.doHandle(
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(
at org.eclipse.jetty.servlet.ServletHandler.doScope(
at org.eclipse.jetty.server.session.SessionHandler.doScope(
at org.eclipse.jetty.server.handler.ContextHandler.doScope(
at org.eclipse.jetty.server.handler.ScopedHandler.handle(
at org.eclipse.jetty.server.handler.HandlerList.handle(
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
at org.eclipse.jetty.server.Server.handle(
at org.eclipse.jetty.server.HttpChannel.handle(
at org.eclipse.jetty.server.HttpConnection.onFillable(
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
at org.eclipse.jetty.util.thread.QueuedThreadPool$
at Source)

I am assuming that the server throwing the errors is 7.7.0. There is something funny with the launch properties in one of your projects. The fastest way to isolate which project is to disable all the projects in the Gateway, enable them one at a time, and then call ip:port/main/system/projectlist until it breaks again. Then you can take a look at the launch properties for that project in the Designer or send the exported project to us. If all else fails, you can also send the Gateway backup to us and we can try it here.

The bad launch descriptor was the problem. Perhaps something left over from 7.6.x.

Anyway, the client launcher now gets a correct project list and all is good.