Topics created by ITSolutions

I’ve solved this thread so I don’t go nuts thinking I have keep finding and fixing this issue. Filenames with spaces (as well as other special characters) will be replaced with _ and this will be available to the next RC release.

So after all kinds of testing and complete confusion I finally figured out what was causing the issue with this. But not sure what happened to cause it. It was caused by my increasing the max size for snapins. I had a snapin the was approx 500mb so I changed the php settings in the old server to accept 3000m (3gb) and it seemed to work. But when I went to the new server and changed the settings to allow for it, it wouldn’t work. When I deleted that snapin completely from the server, everything started to work. Still not sure why when I would delete the snapin tasks from the host and deployed any other snapin it didn’t work. But everything seems to be running smoothly now that I don’t have any large snapins. I think I am going to go back to using scripts for large snapin tasks.

@Jbob
Setting the “runwith” to cmd.exe did work to run it. Thanks for the help.

That makes sense, but why did it run the first time and not the second time then? Both times it was a batch file, with no “runwith” specified. Obviously it did not run correctly the first time, but it didn’t give an error. I know I run bat scripts quite often with FOG and don’t set the “runwith” argument. I guess I am going to definitely start adding it in as it can cause issues at times.

Sorry for not responding earlier, Yes this is solved. Thanks again for all the hard work @Developers and everyone else.

@ITSolutions
Installed .net4 and client installed fine.
Thanks again for your guidance

@Wayne-Workman Thanks for that pointer, that will definitely help in getting started in this. I am learning how to do simple sql queries in PS and VBscript to try and accomplish this but none of them would work without this part.

@Wayne-Workman, Well I could just copy the key from a backup and be ok then. But the issue then comes into why did my snapins directory get cleared out and recreated. I hadn’t had that happen before. It should have been left there and the key should have been present. Might be an issue for @Tom-Elliott to look at. Unless he feels that this could have been a fluke. I might be able to copy my server in a couple days and try the update again and see if I get the same results with the snapin folder being cleared. But if it shouldn’t be cleared I will just copy the file from a back up for now.

Although the new clients are working as is, even with the key missing.

I appreciate the help and all the effort everyone puts into FOG. I wish I had more time to contribute to the product. But unfortunately I am not able to much at the time. So I understand the dedication it takes to keep this awesome product moving forward.

I’m solving this thread as the issue should be fixed. I imagine there may be issues in the future but only from a reporting standpoint. I have moved all of the states to use the task state class elements. Older data used to close tasks with a state is of 2. Task state is 2 is in-line so some of the reports may say this.

@Wayne Workman, Yes it looks as though I will be rebuilding much of the network. I know all about documentation. That is a big part of when I come into a company, when I go in I am not contracted as a full time replacement. Usually as a consultant or cases like this to help them determine how thing should proceed into the future and/or hire a replacement. This is a special case as I am going to work with whoever gets hired to assist for a longer term in getting everything to a point that is manageable, and documentation is key. For this case I was just trying to make my job easier as the last tech had things setup pretty well and running rather smoothly. Too bad he didn’t value documentation.

So I got this working in a round about way. I tried to create a new snap in and it gave me an FTP credential error, so I went in and changed my fog user password to match what the configuration showed it should be and now it works. The log viewer also works.

Not sure but maybe the install script is changing the fog password in one place and not another. But I am able to edit snap ins and view my event logs again.