| Pages:
1
..
6
7
8
9
10
..
19 |
curt999
Junior Member
Posts: 51
Registered: 24-7-2017
Member Is Offline
Mood: No Mood
|
|
you might have a ram module failing on that pc if you are getting intermittent failures could not be related to gsb..run some diagnostics
|
|
|
BigDog
Junior Member
Posts: 20
Registered: 25-4-2018
Member Is Offline
Mood: No Mood
|
|
Quote: Originally posted by curt999  | | you might have a ram module failing on that pc if you are getting intermittent failures could not be related to gsb..run some diagnostics
|
I appreciate the suggestion.
Ran diagnostics - no issues reported.
This error message only occurs with GSB and is 100% reliable, not intermittent.
|
|
|
BigDog
Junior Member
Posts: 20
Registered: 25-4-2018
Member Is Offline
Mood: No Mood
|
|
The error is caused by GSB handling of the Dot Net framework, in some way:
|
|
|
BigDog
Junior Member
Posts: 20
Registered: 25-4-2018
Member Is Offline
Mood: No Mood
|
|
I ran a complete Windows system file check (having already validated) the Dot Net installations. No errors were found. So there appear to be no
missing Windows files or system file corruption.
I uninstalled and reinstalled GSB several times to try to make sure it had installed all the files. I believe it did.
|
|
|
BigDog
Junior Member
Posts: 20
Registered: 25-4-2018
Member Is Offline
Mood: No Mood
|
|
It turns out that the problem is caused by Dot Net 4.6 not being installed, which is required by GSB.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by BigDog | | It turns out that the problem is caused by Dot Net 4.6 not being installed, which is required by GSB. |
thanks for update
|
|
|
cyrus68
Member
Posts: 171
Registered: 5-6-2017
Member Is Offline
Mood: No Mood
|
|
I am getting an error in 44.64. When I do WF on saved systems, this error appears for both worker and manager.
System.NullReferenceException: Object reference not set to an instance of an object.
at
SpV9nECqWoLyY6pzhkoaPOmgwF_c09gEu9WXNOKzM7vt.0GNAvD5J1sJZWSJ8mpPrG003d$Yp6wbNscrWuxg4KNUPbCtTIm0WKF15G9u1CqJwfOVeT2L3ZwiW38q4K6_VSv0.CmOm5KhaXxK7xOBSs
L3BUpooM7fyhmDGqUhUvSqo8WdC(
203;
; )
at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
at SpV9nECqWoLyY6pzhkoaPOmgwF_c09gEu9WXNOKzM7vt.KZX3YbPM54ejvr0vMHIjtec(IEnumerable`1 , Dictionary`2 , String )
at SpV9nECqWoLyY6pzhkoaPOmgwF_c09gEu9WXNOKzM7vt.eTt7t94ebiNRdKBm10cDMzI(DataGridView , List`1& , Boolean )
at SpV9nECqWoLyY6pzhkoaPOmgwF_c09gEu9WXNOKzM7vt.GmjcK7OQOYeh0RyQZxjlJbq$_$YorGzm9ibZCSLFAkVh()
Workplace Mode: Manager
Instance ID: J5xawXIMS6yJIMdYK
Workplace ID: J5xawXIMS6yJIMdYK.20180518-015107-367851
App Version: 1.0.44.64 / 2018-05-08
Machine Name: MAIN3
The WFs are carried out, but this error pops up every second. I end up having to delete thousands of these in the Exceptions folder.
This didn't happen in previous versions.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by cyrus68 | I am getting an error in 44.64. When I do WF on saved systems, this error appears for both worker and manager.
System.NullReferenceException: Object reference not set to an instance of an object.
at
SpV9nECqWoLyY6pzhkoaPOmgwF_c09gEu9WXNOKzM7vt.0GNAvD5J1sJZWSJ8mpPrG003d$Yp6wbNscrWuxg4KNUPbCtTIm0WKF15G9u1CqJwfOVeT2L3ZwiW38q4K6_VSv0.CmOm5KhaXxK7xOBSs
L3BUpooM7fyhmDGqUhUvSqo8WdC(
203;
; )
at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
at SpV9nECqWoLyY6pzhkoaPOmgwF_c09gEu9WXNOKzM7vt.KZX3YbPM54ejvr0vMHIjtec(IEnumerable`1 , Dictionary`2 , String )
at SpV9nECqWoLyY6pzhkoaPOmgwF_c09gEu9WXNOKzM7vt.eTt7t94ebiNRdKBm10cDMzI(DataGridView , List`1& , Boolean )
at SpV9nECqWoLyY6pzhkoaPOmgwF_c09gEu9WXNOKzM7vt.GmjcK7OQOYeh0RyQZxjlJbq$_$YorGzm9ibZCSLFAkVh()
Workplace Mode: Manager
Instance ID: J5xawXIMS6yJIMdYK
Workplace ID: J5xawXIMS6yJIMdYK.20180518-015107-367851
App Version: 1.0.44.64 / 2018-05-08
Machine Name: MAIN3
The WFs are carried out, but this error pops up every second. I end up having to delete thousands of these in the Exceptions folder.
This didn't happen in previous versions. |
Can you confirm if non saved systems have the same issue?
|
|
|
zdenekt
Junior Member
Posts: 37
Registered: 1-10-2017
Location: Czech Republic
Member Is Offline
Mood: No Mood
|
|
I have the same issue almost all the time.
It happens when I want delete systems with completed WFA which does not look good.
Sometimes itīs not possible to delete some system anyway. So I have to ignore it until the next GSB restart.
|
|
|
cyrus68
Member
Posts: 171
Registered: 5-6-2017
Member Is Offline
Mood: No Mood
|
|
I'm not sure if this is a bug in version 77, or just a nuisance, but you may want to check all your workers before a run is completed.
The pic below shows a worker where the central panels are missing or distorted. Also , the right hand panel has missing or incorrect information.
It did, however, generate systems - though I don't know how many. The total reported in the manager is incorrect. So it's best to check all workers
early and shut down defective ones. Unfortunately, I didn't check until the run was completed.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by cyrus68 | I'm not sure if this is a bug in version 77, or just a nuisance, but you may want to check all your workers before a run is completed.
The pic below shows a worker where the central panels are missing or distorted. Also , the right hand panel has missing or incorrect information.
It did, however, generate systems - though I don't know how many. The total reported in the manager is incorrect. So it's best to check all workers
early and shut down defective ones. Unfortunately, I didn't check until the run was completed. |
I havnt seen this before, and i have run a lot of workers, though I dont look at the workers a great deal. I will keep an eye on it. Is the issues
repeatable. First thing I would try is reboot the PC
|
|
|
cyrus68
Member
Posts: 171
Registered: 5-6-2017
Member Is Offline
Mood: No Mood
|
|
The more important issue is that the manager failed to correctly aggregate all the systems. It wasn't related to the defective worker. Excluding the
defective worker, the aggregate was far less than the sum of systems produced by all the other workers.
This is a serious issue because it forces the user to repeat the analysis on a multitude of workers instead of the manager only. The bug was fixed
many versions ago, but it seems to have reappeared. Now I'm wondering if running the 72 exe in the 77 directory will pose its own problems.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by cyrus68 | The more important issue is that the manager failed to correctly aggregate all the systems. It wasn't related to the defective worker. Excluding the
defective worker, the aggregate was far less than the sum of systems produced by all the other workers.
This is a serious issue because it forces the user to repeat the analysis on a multitude of workers instead of the manager only. The bug was fixed
many versions ago, but it seems to have reappeared. Now I'm wondering if running the 72 exe in the 77 directory will pose its own problems.
|
You shouldnt mix manager and worker versions is a good guide, but often there
is not significant differences that will cause issues.
Im not clear if you say you are running .77 manger with .72 worker
or just a standalone.72 with manager and worker being .77
|
|
|
Carl
Member
Posts: 342
Registered: 10-5-2017
Member Is Offline
Mood: No Mood
|
|
44.77 manager / 44.72 worker issue might be because installer file "GSBSETUP44.77c-betausers" contains:
manager 44.77
standalone 44.77
but not worker 44.77
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by Carl | 44.77 manager / 44.72 worker issue might be because installer file "GSBSETUP44.77c-betausers" contains:
manager 44.77
standalone 44.77
but not worker 44.77 |
Worker is in the gsb/worker folders.
C:\GSB\GSB (Workers)
C:\GSB\GSB (Workers)2ContributeToGSBCloud1
Icons on the desktop.
Regardless the exe are all the same. The filename determines the function of the exe
|
|
|
cyrus68
Member
Posts: 171
Registered: 5-6-2017
Member Is Offline
Mood: No Mood
|
|
I did not mix different different versions. I ran version 77 for both manager and worker. As I said, the manager failed to aggregate all the systems
produced - by a big margin of about 1000. This is not difficult to verify. You just add up the systems produced by the workers and compare with the
manager's total.
This is a serious issue. I don't want to repeat the same analysis on 15 workers. That is why I will revert to version 72 for BOTH manager and worker.
My question was: whether the 72 exe files will be compatible with all the other files of the 77 installation. If not, how do I roll back?
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by cyrus68 | I did not mix different different versions. I ran version 77 for both manager and worker. As I said, the manager failed to aggregate all the systems
produced - by a big margin of about 1000. This is not difficult to verify. You just add up the systems produced by the workers and compare with the
manager's total.
This is a serious issue. I don't want to repeat the same analysis on 15 workers. That is why I will revert to version 72 for BOTH manager and worker.
My question was: whether the 72 exe files will be compatible with all the other files of the 77 installation. If not, how do I roll back?
|
I am waiting for programmer to get back to me if .72 and .77 work the same.
Can you zip up any exceptions in the last few days in the manager and worker folders and send them to me? For now best keep to manager and worker
being the same version.
I am not aware of this issue, but havnt looked for it closely so could miss it. Its possibly a data base error, but I dont know enough yet. I can test
on my local machines to try to replicate the issue.
To roll back, just run the exe version you want to be running.
|
|
|
boosted
Junior Member
Posts: 73
Registered: 16-6-2017
Member Is Offline
Mood: No Mood
|
|
I am not sure if the bug I mentioned about before has been fixed or not in 47.10 but its either back
or still awaiting a fix in a new update.
The issue is as follows:
I am in a Standalone and sorting NP-F column and I have it sorted from neg. to positive. I started clicking on
some of the negative rows and they turn more negative and the positives that I click on turn to negative.
BUT, if you scroll down at least halfway down column and start clicking on positive NP-F numbers they stay same
as they should.
Like I said, not sure this got fixed or if the problem has now been inverted from what it was when I originally found it.
Anyways, just was sitting here and clicked in a few and noticed it.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by boosted | I am not sure if the bug I mentioned about before has been fixed or not in 47.10 but its either back
or still awaiting a fix in a new update.
The issue is as follows:
I am in a Standalone and sorting NP-F column and I have it sorted from neg. to positive. I started clicking on
some of the negative rows and they turn more negative and the positives that I click on turn to negative.
BUT, if you scroll down at least halfway down column and start clicking on positive NP-F numbers they stay same
as they should.
Like I said, not sure this got fixed or if the problem has now been inverted from what it was when I originally found it.
Anyways, just was sitting here and clicked in a few and noticed it. |
send me teamviwer details so I can see this.
also right click and try over ride original settings
|
|
|
emsjoflo
Junior Member
Posts: 39
Registered: 7-7-2017
Member Is Offline
Mood: No Mood
|
|
I noticed the issue boosted mentioned also. And it seems to happen more with certain Custom Indicators. I'll get a bunch of systems with really
great stats, but when I click on them, the graph changes and the statistics get worse.
I have another issue that popped up while using the Custom Indicator. I know Custom Indicators are a low priority for Peter and the development of
GSB so I am not demanding that anything be done about my complaints. Just communicating.
Right now I have two custom indicators that I am evaluating so I only want systems built with these indicators as the primary. Changing the
True/False toggle for "Force Use(in all systems) seems to do nothing so I disabled all the Built-in indicators (by toggling "Enabled" to false). I
ran several batches of systems, exported the CSV data to Excel and analyzed it. Very cool feature, by the way. I discovered that most of the
profitable systems were produced with only 10 or so of the Built-in Indicators as a secondary filter.
To speed up the process, I disabled SF on the built-in indicators that did not get used often ( So I can focus on the ones that do the best in
combination with my Indicator). When i ran GSB restricted like this, about 1/4 of the systems produced had GSB_AverageFC as one or both of the
primary indicators. Even though "Built-in Indicators" is 0(SF:14)/37 indicators.
|
|
|
emsjoflo
Junior Member
Posts: 39
Registered: 7-7-2017
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by boosted | I am not sure if the bug I mentioned about before has been fixed or not in 47.10 but its either back
or still awaiting a fix in a new update.
The issue is as follows:
I am in a Standalone and sorting NP-F column and I have it sorted from neg. to positive. I started clicking on
some of the negative rows and they turn more negative and the positives that I click on turn to negative.
BUT, if you scroll down at least halfway down column and start clicking on positive NP-F numbers they stay same
as they should.
Like I said, not sure this got fixed or if the problem has now been inverted from what it was when I originally found it.
Anyways, just was sitting here and clicked in a few and noticed it. |
boosted, I noticed that the problem seems to be much worse when I run several instances of GSB standalone on the same machine at the same time. And
then if I change parameters and do another batch with different settings it gets worse. I have been in the middle of a WFA when the graph changed.
It seems almost like GSB is overwriting systems with similar serial numbers.
It was getting so bad that I quit running simultaneous standalone GSB on the same machine. and if it starts getting irritating, I will restart GSB
every time I want to run a new batch of systems.
|
|
|
emsjoflo
Junior Member
Posts: 39
Registered: 7-7-2017
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by boosted | I am not sure if the bug I mentioned about before has been fixed or not in 47.10 but its either back
or still awaiting a fix in a new update.
The issue is as follows:
I am in a Standalone and sorting NP-F column and I have it sorted from neg. to positive. I started clicking on
some of the negative rows and they turn more negative and the positives that I click on turn to negative.
BUT, if you scroll down at least halfway down column and start clicking on positive NP-F numbers they stay same
as they should.
Like I said, not sure this got fixed or if the problem has now been inverted from what it was when I originally found it.
Anyways, just was sitting here and clicked in a few and noticed it. |
boosted, I noticed that the problem seems to be much worse when I run several instances of GSB standalone on the same machine at the same time. And
then if I change parameters and do another batch with different settings it gets worse. I have been in the middle of a WFA when the graph changed.
It seems almost like GSB is overwriting systems with similar serial numbers.
It was getting so bad that I quit running simultaneous standalone GSB on the same machine. and if it starts getting irritating, I will restart GSB
every time I want to run a new batch of systems.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by emsjoflo | | Quote: Originally posted by boosted | I am not sure if the bug I mentioned about before has been fixed or not in 47.10 but its either back
or still awaiting a fix in a new update.
The issue is as follows:
I am in a Standalone and sorting NP-F column and I have it sorted from neg. to positive. I started clicking on
some of the negative rows and they turn more negative and the positives that I click on turn to negative.
BUT, if you scroll down at least halfway down column and start clicking on positive NP-F numbers they stay same
as they should.
Like I said, not sure this got fixed or if the problem has now been inverted from what it was when I originally found it.
Anyways, just was sitting here and clicked in a few and noticed it. |
boosted, I noticed that the problem seems to be much worse when I run several instances of GSB standalone on the same machine at the same time. And
then if I change parameters and do another batch with different settings it gets worse. I have been in the middle of a WFA when the graph changed.
It seems almost like GSB is overwriting systems with similar serial numbers.
It was getting so bad that I quit running simultaneous standalone GSB on the same machine. and if it starts getting irritating, I will restart GSB
every time I want to run a new batch of systems. |
Have you tried .17 build? many bugs of .10 were fixed.
Attachment: Login to view the details
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Hi Boothy,
GSB next build will have stats to count systems in workers and managers. Unque systems and worker systems. - There are performance increases too in
the database. I build 2000 systems with 4 workers, and lost 1 system (duplicate I think)
With 20 or so workers, I lost significantly higher amount of systems, which Im still looking into.
Hope to have a count that represents if connection to google, and connection to GSB server fails too.
|
|
|
boosted
Junior Member
Posts: 73
Registered: 16-6-2017
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by emsjoflo | | Quote: Originally posted by boosted | I am not sure if the bug I mentioned about before has been fixed or not in 47.10 but its either back
or still awaiting a fix in a new update.
The issue is as follows:
I am in a Standalone and sorting NP-F column and I have it sorted from neg. to positive. I started clicking on
some of the negative rows and they turn more negative and the positives that I click on turn to negative.
BUT, if you scroll down at least halfway down column and start clicking on positive NP-F numbers they stay same
as they should.
Like I said, not sure this got fixed or if the problem has now been inverted from what it was when I originally found it.
Anyways, just was sitting here and clicked in a few and noticed it. |
boosted, I noticed that the problem seems to be much worse when I run several instances of GSB standalone on the same machine at the same time. And
then if I change parameters and do another batch with different settings it gets worse. I have been in the middle of a WFA when the graph changed.
It seems almost like GSB is overwriting systems with similar serial numbers.
It was getting so bad that I quit running simultaneous standalone GSB on the same machine. and if it starts getting irritating, I will restart GSB
every time I want to run a new batch of systems. |
emsjoflo
Interesting to see someone else have same issue as I had. Good to know (I think...lol) I wasn't the only one seeing this issue crop up.
I haven't tried the newest GSB release yet but hoping its resolved. I am hoping any and all bugs are fixed soon before more time and effort is spent
improving GSB. I think GSB has made more than enough progress at this point since its inception and happy to see Peter continue its evolution. Like
I said it would be nice to slow the progress train down for a bit until any and all bugs are worked out, then resume GSB progress. Peter is doing
great work with GSB which we can all appreciate.
|
|
|
| Pages:
1
..
6
7
8
9
10
..
19 |
![[*]](images/davis/default_icon.gif){kind=icon}
