7.5.00098 - Release Notes

jongrimes · 2016-12-23T13:19:51.000Z

7.5.00098

Inventory

85763 - Finder crash when scanning devices via SSH

Download the latest version here: www.spiceworks.com/download

v-s · 2016-12-23T13:46:09.000Z

Looking forward to testing this out.

mikesmith9351 · 2016-12-23T14:11:29.000Z

I have an open support ticket related to this finder crash. My network scans have not been working since 7.5.00095, repeated crashes logged in the system event viewer. Downloading the update now, fingers crossed!

mikesmith9351 · 2016-12-23T16:52:45.000Z

Update seems to have tentatively fixed my problem. We’re scanning again, thanks!

b-c · 2016-12-23T17:49:05.000Z

Agreed this install appears to also have fixed my issue with the upgrade from .93…

.95 wouldn’t install with my custom http/s ports - would hang the installer -

currently this version installed correctly and is up and running - finder - will find out soon enough.

vhscarpacci · 2016-12-27T11:30:19.000Z

Too many updates. Please test these out first. I am not your beta tester.

timloga · 2016-12-28T14:40:18.000Z

We’ve installed the 7.5.00098 update – but the Spiceworks Update Check ( Spiceworks Update Check - Apps with updates: 1 ) shows that we might be running a beta version?

dbone3489 · 2016-12-28T20:42:17.000Z

Fun!

Anyone else encounter this during install? I’m posting this while Spiceworks is still installing right now, so I’m not sure if these errors are important or not, but pressing retry didn’t help. I pressed abort and the installer seems to still be installing.

dbone3489 · 2016-12-28T21:10:21.000Z

dBone:

Fun!

Anyone else encounter this during install? I’m posting this while Spiceworks is still installing right now, so I’m not sure if these errors are important or not, but pressing retry didn’t help. I pressed abort and the installer seems to still be installing.

sigh restoring…

mikesmith9351 · 2016-12-28T21:49:23.000Z

Usually an “error opening file for writing” error is because the file is locked, or otherwise open. 99% of the time I’ve seen this error it’s because the service is still running or the program wasn’t shut down correctly. Go through your services and task manager and make sure everything related to Spiceworks is shut down / stopped prior to beginning the upgrade.

Actually this goes for pretty much all Windows programs, lol.

dbone3489 · 2016-12-29T13:20:33.000Z

Oldsmobile_Mike:

Usually an “error opening file for writing” error is because the file is locked, or otherwise open. 99% of the time I’ve seen this error it’s because the service is still running or the program wasn’t shut down correctly. Go through your services and task manager and make sure everything related to Spiceworks is shut down / stopped prior to beginning the upgrade.

Actually this goes for pretty much all Windows programs, lol.

Thanks for the suggestion, I’ll give that a go. I’ve been doing the Spiceworks upgrades for several years now and I don’t remember encountering this issue before. As well, I would have thought perhaps the installer would be coded to do kill commands and perform checks, etc.

dbone3489 · 2016-12-30T15:27:55.000Z

dBone:

Oldsmobile_Mike:

Usually an “error opening file for writing” error is because the file is locked, or otherwise open. 99% of the time I’ve seen this error it’s because the service is still running or the program wasn’t shut down correctly. Go through your services and task manager and make sure everything related to Spiceworks is shut down / stopped prior to beginning the upgrade.

Actually this goes for pretty much all Windows programs, lol.

Thanks for the suggestion, I’ll give that a go. I’ve been doing the Spiceworks upgrades for several years now and I don’t remember encountering this issue before. As well, I would have thought perhaps the installer would be coded to do kill commands and perform checks, etc.

Upgrade successful last night

jamieheadley · 2017-01-05T19:00:25.000Z

Anybody using the Edge extension for Win10 Action center? I have it turned on and love the potential benefits however I am getting multiple alerts for every update to a ticket.

8489442 · 2017-01-17T10:57:41.000Z

Letter whith attach *.jpg named on russian language still dont create new tickets

las · 2017-01-19T08:33:59.000Z

dBone:

Oldsmobile_Mike:

Usually an “error opening file for writing” error is because the file is locked, or otherwise open. 99% of the time I’ve seen this error it’s because the service is still running or the program wasn’t shut down correctly. Go through your services and task manager and make sure everything related to Spiceworks is shut down / stopped prior to beginning the upgrade.

Actually this goes for pretty much all Windows programs, lol.

Thanks for the suggestion, I’ll give that a go. I’ve been doing the Spiceworks upgrades for several years now and I don’t remember encountering this issue before. As well, I would have thought perhaps the installer would be coded to do kill commands and perform checks, etc.

Had this due to 7.5.00095 finder crash on ssh scans

Windows changed the way it handle events and logs so the “DHCP Client” and “Windows Events Log” Services Locked the executable’s in such a way that they did not show as running in Taskmanager Processes but still Locked by the Windows Operating System.

Restarting the Services it allowed me to completely Uninstall 7.5.00095 after I copied the “db” and “data” folders to safe place.

Installed the 7.5.00098 without starting, copied the backed-up “db” and “data” folders to the newly installed 7.5.00098

Started 7.5.00098 and all working fine now, even got rid of some of the legacy issues

skylerhollin2 · 2017-02-23T17:35:56.000Z

After the update, we are experiencing issues where the site is unresponsive at times. Is this a known issue?

komputr · 2017-02-23T17:48:16.000Z

Others are reporting the same issue:

Updated spiceworks, Dashboard randomly freezes Spiceworks Support

I updated SW (Which I shouldn't have since everything was working fine) to version 7.5.00098 and I am running into this random issue where the whole interface freezes and can't click on anything. No matter if you are on the Dashboard or HelpDesk. It also happens to my colleagues. Is this a known bug? I have tried restarting SpiceWorks as well as restarting the server and clearing the browser cache with no luck.

niccrockett · 2017-02-23T17:51:05.000Z

FYI, I’ve had a problem for some time where SW will crash on the server and I have to relaunch it to get access again.

carstenbentzien2 · 2017-03-01T17:09:09.000Z

Any new information when there will be another version? A long time Spiceworks release monthly updates, for a longer period only quarterly or longer updates released. Are there any plannings to be more quicker releasing new versions?

Carsten

niccrockett · 2017-03-01T17:53:35.000Z

No offense to Carsten, we all have our own preferences. I’m personally a fan of fewer updates. This way I’m not having to do as much work. My schedule is already overloaded, so I don’t need any more. However, on the opposite side, I do enjoy the updates that are provided and the hard work that SW puts into these updates. Thank you!