Forum Discussion
Looks like your instance is different, previously it works for different instance https://community.softwaregrp.com/
Now the api you are using to target is different which points to https://community.microfocus.com/
Thanks Parshant , that's just because old example I selected was before we changed our domain name. My bad. community.softwaregrp.com now redirects to community.microfocus.com and I did run some instances on my Win7 OS after the change that worked so that's probably not the issue.
EDIT: I looked at some of the more recent run logs and they do list it as softwaregrp.com so I'll look more closely at that and see why it's different.
2nd EDIT: Nope. I found a run previous to my OS move that uses the microfocus.com domain and it worked:
I, [2019-05-14T13:49:53.623195 #14628] INFO -- : STARTING THE PROCESS
I, [2019-05-14T13:49:53.623195 #14628] INFO -- : INSTANCE: <a href="https://community.microfocus.com" target="_blank">https://community.microfocus.com</a>
I, [2019-05-14T13:49:53.624195 #14628] INFO -- : SESSIONID: 38C778CF132D39FF53B10439FA07A4A9
I, [2019-05-14T13:49:53.624195 #14628] INFO -- : SOURCE FILE: ITSMblog/finished.csv
I, [2019-05-14T13:49:54.571290 #14628] INFO -- : Authentication success.
- Parshant6 years agoBoss
Can you check the file structure of your working files is same on both of the OS.
Looks like session id not created during the process run. Which results in failure.
- kgroneman6 years agoBoss
Yea, the file structure is exactly the same. I'm running it from the same location as before.
Related Content
- 9 years ago
- 2 years ago
- 15 years ago