[SOLVED] SteamAPI initialization failed

[halfbarrell 4]

Having an issue with the latest update to Infistar.  Installed on test server with newest changes following update instructions and the server fails to connect to steam now.  Went back and did a complete install from scratch and still having the same problem.  Any ideas on what I may have overlooked?  I'm about to start drinking at 9 am.

 

15:14:11 SteamAPI initialization failed. Steam features wont's be accessible!

[slay 17]

Check your server logs.

[halfbarrell 4]

i did.  that is all that is on them. startup command line which hasn't changed then the steam message.

[Capt Caveman 10]

just a thought but have you tried getting in touch with InfiSTAR?

[halfbarrell 4]

not yet.  he has enough on plate already lol.  wanted to see if anyone else is having the same issues or had the same issue before i bug him.  more than likely it is something on my end that i am missing.

[Capt Caveman 10]

I have the same issues and again I have found no solution, on the other hand it doesnt seem to detract from the server running or having people join and enjoy it.

[halfbarrell 4]

my server wont even load.  installed infistar a million times i swear. but with the change to ahat.hpp from sqf i apparently screwed something up.  love the program and its worth every penny.  just hung up here a bit.

[StokesMagee 871]

15:14:11 SteamAPI initialization failed. Steam features wont's be accessible!

This dosent mean it dosent connect to steam, my servers have this and it works just fine. this is probably an arma bug, or a steam bug, may or may not be fixed next version. (probs when arma 3 updates their steam API) but this shouldent have anything to do with infistar, unless its stoping your server from loading.

Edited February 13, 2016 by †RiH† Stokes

[halfbarrell 4]

3 minutes ago, †RiH† Stokes said:

15:14:11 SteamAPI initialization failed. Steam features wont's be accessible!

This dosent mean it dosent connect to steam, my servers have this and it works just fine. this is probably an arma bug, or a steam bug, may or may not be fixed next version. (probs when arma 3 updates their steam API)

i reverted back to my previous version and it started and connected fine.  it is not searchable via remote function through arma launcher.  my logs show nothing initializing either. 

[StokesMagee 871]

 

3 minutes ago, halfbarrell said:

i reverted back to my previous version and it started and connected fine.  it is not searchable via remote function through arma launcher.  my logs show nothing initializing either. 

does it say that in your logs and gets stuck?