Unable to access the Firestreamer Storage Controller.

The technical support forum for Firestreamer (the virtual tape library).
Post Reply
johnmantle
Posts: 6
Joined: 07 Feb 2012, 09:45

Unable to access the Firestreamer Storage Controller.

Post by johnmantle » 09 Mar 2017, 13:51

Hi,

I am getting the following error message when starting the Firestreamer console:

"Unable to access the Firestreamer Storage Controller. - Not enough storage is available to process this command"

I have checked the software version levels against the storage driver levels, as suggested within the help, but every is correct. It also as lost the license key and request me to purchase one! However, I can't install our license key as the Install License Key option doesn't appear in the console tree, when Firestreamer is right-clicked!

Can anyone help?

jsf
Cristalink Support
Posts: 300
Joined: 29 Aug 2010, 09:03

Re: Unable to access the Firestreamer Storage Controller.

Post by jsf » 09 Mar 2017, 20:17

The Install License option won't be available if Firestreamer Snap-In is unable to communicate with the driver.

The error indicates that your system is out of memory. Have you checked the memory status in Task Manager? What does it show? Have you rebooted your server recently?
Best regards,
John Smith
Cristalink Support

johnmantle
Posts: 6
Joined: 07 Feb 2012, 09:45

Re: Unable to access the Firestreamer Storage Controller.

Post by johnmantle » 09 Mar 2017, 21:20

Of the 128GB main memory installed, just over 30GB is still free...
Regarding restart - it's a server :) ... and our next outage window is planned for Saturday, however we will need to be sure that Firestreamer is accessible as this window will be used to apply O/S patches and upgrade DPM from 2012R2 to 2016. All FS backups are still running without issue.
Best regards...

jsf
Cristalink Support
Posts: 300
Joined: 29 Aug 2010, 09:03

Re: Unable to access the Firestreamer Storage Controller.

Post by jsf » 09 Mar 2017, 22:52

From your response it appears that the server has been running for a while. If so, it's even more likely it's run out of kernel memory. Check the paged and non-paged pool usage, overall and per process (you need to add relevant columns on the Details tab of Task Manager and sort by clicking the column header). If it's high (especially comparing to that just after the server is restarted), then most likely some faulty driver leaks memory. The server restart is likely to fix the error - until the memory is exhausted again.

Small IrpStackSize might also be the cause, see here.

There might be other less likely reasons, for example, if you are running Driver Verifier with low memory simulation against Firestreamer drivers, but I guess it's not the case.
Best regards,
John Smith
Cristalink Support

johnmantle
Posts: 6
Joined: 07 Feb 2012, 09:45

Re: Unable to access the Firestreamer Storage Controller.

Post by johnmantle » 21 May 2018, 16:44

Sorry, forgot to post the conclusion.
Yes, after the restart the issue no longer occurred.
Yes, by using Process Explorer we were able to ascertain that there was a lot of Kernel Memory being used. After the restart (which was caused be the maintenance application of multiple MS patches) the issue has not returned.
We also upped the IrpStackSize just to be sure.
Thanks for the support.

Post Reply