Skip to main content
New Participant
May 24, 2023

P: Session ID: 1000 error using generative fill

  • May 24, 2023
  • 67 replies
  • 19027 views

I've successfully used the generative tool on another machine but my current setup when hitting generate it gives me an get session ID error. Reinstalled, rebooted, same results.

This topic has been closed for replies.

67 replies

New Participant
June 2, 2023

"Bei der Bilderzeugung ist ein Fehler aufgetreten: error response image not found: 1000"

taucht beim "generative fill" auf und generiert kein Ergbenis

JordanAndrian
New Participant
June 2, 2023

An error occurred during image generation: error response image not found: 1000

 

Everytime i try to use the new AI feature I get this  message...

 

I am running Ventura 13.4 on an M2 Macbook Air...

 

Any help would be great!

New Participant
June 2, 2023

VPN Name pls

New Participant
June 2, 2023

here is the error

 

An error occurred during image generation: error response image not found: 1000

LeeATX
New Participant
June 2, 2023

same

New Participant
June 2, 2023

error response image not found: 1000

New Participant
June 2, 2023

Restarted Photoshop, tested with different photos, and different methods. Worked previously, stopped at random.

LeeATX
New Participant
June 2, 2023

This just started happening to me. After a rash of  'violations' everytime I tried to add a leg to a subject.

Participating Frequently
June 2, 2023

Just discovered another anomoly. When I place cursor over the "image" this is what I see:-

New Participant
June 1, 2023

Hello,

 

The Ai is not working on macbook

An error occurred during image generation: error get_session_id session id not found: 1000

Participating Frequently
May 30, 2023

@MichaelG-IS , that was it! Our network admnistrator added sensei-ue1.adobe.io to our SSL decryption exclusion list and it finally works for me - no session ID error. Thank you for posting the fix!

New Participant
May 30, 2023

For my environment our web filter was preventing the session connection.
Whitlisting it alone did not fix it.
We had to add sensei-ue1.adobe.io to our SSL decryption exclusion list in order to get it to work.