Snapin not running

[msi]

Hi,
Snapin Checked in but not completing the task. Does it has to do it below problem as status shows read? How can we fix that? My primary fog is at different network and different dns.

[Joe Schmitt]

@msi the log says Invalid Security Token Did you press Reset Encryption Data after re-installing the client like I mentioned in my prior post?

[Joe Schmitt]

@msi We’d need the C:\fog.log from a computer that is running the Snapin and not completing

[msi]

@joe-schmitt said in Snapin not running:
I have re-installed the client installer. Below is before and after log file

@msi We’d need the C:\fog.log from a computer that is running the Snapin and not completing

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 2/16/2018 1:53 PM Client-Info Version: 0.11.12
 2/16/2018 1:53 PM Client-Info OS:      Windows
 2/16/2018 1:53 PM Middleware::Authentication Waiting for authentication timeout to pass
 2/16/2018 1:55 PM Middleware::Communication Download: http://10.1.1.230/fog/management/other/ssl/srvpublic.crt
 2/16/2018 1:55 PM Data::RSA FOG Server CA cert found
 2/16/2018 1:55 PM Middleware::Authentication Cert OK
 2/16/2018 1:55 PM Middleware::Authentication ERROR: Could not get security token
 2/16/2018 1:55 PM Middleware::Authentication ERROR: Could not find file 'C:\Program Files (x86)\FOG\token.dat'.
 2/16/2018 1:55 PM Middleware::Communication POST URL: http://10.1.1.230/fog/management/index.php?sub=requestClientInfo&authorize&newService
 2/16/2018 1:55 PM Middleware::Response Invalid security token

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 2/16/2018 1:55 PM Client-Info Version: 0.11.12
 2/16/2018 1:55 PM Client-Info OS:      Windows
 2/16/2018 1:55 PM Middleware::Authentication Waiting for authentication timeout to pass
 2/16/2018 1:56 PM Controller Stop
 2/16/2018 1:56 PM Service Stop requested
 2/16/2018 1:56 PM Bus Emmiting message on channel: Status
 2/16/2018 1:56 PM Middleware::Authentication ERROR: Could not authenticate
 2/16/2018 1:56 PM Middleware::Authentication ERROR: Thread was being aborted.

Fog-Old

------------------------------------------------------------------------------
--------------------------------PowerManagement-------------------------------
------------------------------------------------------------------------------
 2/16/2018 1:48 PM Client-Info Client Version: 0.11.12
 2/16/2018 1:48 PM Client-Info Client OS:      Windows
 2/16/2018 1:48 PM Client-Info Server Version: 1.4.4
 2/16/2018 1:48 PM Middleware::Response ERROR: Unable to get subsection
 2/16/2018 1:48 PM Middleware::Response ERROR: Object reference not set to an instance of an object.

------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 2/16/2018 1:48 PM Client-Info Client Version: 0.11.12
 2/16/2018 1:48 PM Client-Info Client OS:      Windows
 2/16/2018 1:48 PM Client-Info Server Version: 1.4.4
 2/16/2018 1:48 PM Middleware::Response ERROR: Unable to get subsection
 2/16/2018 1:48 PM Middleware::Response ERROR: Object reference not set to an instance of an object.
 2/16/2018 1:48 PM Service Sleeping for 73 seconds

[Joe Schmitt]

@msi first off, reinstalling the client requires that you hit Reset Encryption Data button on the machine. Otherwise the new install will not be able to Authenticate with the server.

Secondly, we need the entire log, specifically the SnapinClient portion, from when it ran the snapin that didn’t complete

[msi]

@joe-schmitt It is not allowing me to upload the txt file. Perhaps I think its the certificate error as I had to re-run the fog installer for a different problem that I have been facing. link text. I think It has to do with FOG_STORAGENODE_MYSQLPASS. When we install new storage node that’s the password we provide; and its changed after re running the fog installer.

------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 2/16/2018 1:48 PM Client-Info Client Version: 0.11.12
 2/16/2018 1:48 PM Client-Info Client OS:      Windows
 2/16/2018 1:48 PM Client-Info Server Version: 1.4.4
 2/16/2018 1:48 PM Middleware::Response ERROR: Unable to get subsection
 2/16/2018 1:48 PM Middleware::Response ERROR: Object reference not set to an instance of an object.

[Joe Schmitt]

@msi to help you with the Object reference not set to an instance of an object. issue I’ll need to see the full log file. You shouldn’t need to upload a txt if you put the entire log into a codeblock (like you’re doing with the logs you currently post).

[msi]

@joe-schmitt Hi, I just tried again. I am getting bellow error

[Joe Schmitt]

@msi the log says Invalid Security Token Did you press Reset Encryption Data after re-installing the client like I mentioned in my prior post?

[Tom Elliott]

@msi open the host in the GUI and press reset encryption data and confirm.

[msi]

@Tom-Elliott @joe-schmitt said in Snapin not running:

@msi the log says Invalid Security Token Did you press Reset Encryption Data after re-installing the client like I mentioned in my prior post?

It is working but the status still shows no such devices or address as show below:

[Tom Elliott]

@msi No such device or address simply means the fog ping service cannot ping that hostname. This is usually due to firewall on the host machine not allowing a ping response.

FOG Uses port 445 for it’s pinging.

“TCP port 445 is used for direct TCP/IP MS Networking access without the need for a NetBIOS layer.”

If this port is not opened, it will not be able to find the device or address.

• Source: https://support.symantec.com/en_US/article.TECH88796.html

[msi]

@tom-elliott said in Snapin not running:

@msi No such device or address simply means the fog ping service cannot ping that hostname. This is usually due to firewall on the host machine not allowing a ping response.

FOG Uses port 445 for it’s pinging.

I checked the port 445. its open.

[Joe Schmitt]

@msi said in Snapin not running:

I checked the port 445. its open.

Then it’s likely just a DNS configuration issue: if the FOG server can’t resolve hostnames, then it can’t ping them. If you’d like help with that please open a new thread, though this is ultimately not a FOG issue, so it may be best to search other resources on how to configure DNS (assuming this is the issue).