Microsoft Forms - "Something went wrong" Error

%3CLINGO-SUB%20id%3D%22lingo-sub-151661%22%20slang%3D%22en-US%22%3EMicrosoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151661%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20would%20like%20to%20acknowledge%20that%20we're%20actively%20working%20on%20investigating%20a%20service%20reliability%20issue.%20We%20will%20use%20this%20discussion%20thread%20to%20keep%20our%20customer%20updated.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ESummary%20of%20impact%3A%3C%2FSTRONG%3E%20Starting%2001%3A00%20UTC%20a%20significant%20number%20of%20users%20encountered%20%22Something%20went%20wrong%22%20errors.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EPreliminary%20root%20cause%3C%2FSTRONG%3E%3A%20Under%20investigation.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EMitigation%3A%3C%2FSTRONG%3E%26nbsp%3BWe've%20made%20progress%20narrowing%20down%20the%20problem%20and%20are%20in%20the%20process%20to%20identify%20a%20proper%20mitigation%20to%20restore%20the%20service.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you%20for%20your%20patience%20as%20we%20work%20to%20restore%26nbsp%3Bthe%20Microsoft%20Forms%20service.%20It's%20our%20top%20priority%20to%20get%20this%20issue%20addressed%20as%20quickly%20as%20possible.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F27900iBBB0AF8FDACA9FE0%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22error.PNG%22%20title%3D%22error.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYour%20Microsoft%20Forms%20Team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-151661%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EForms%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297732%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297732%22%20slang%3D%22en-US%22%3EThanks%20for%20reporting%20this%20issue%20and%20sorry%20for%20all%20your%20inconvenience.%20This%20issue%20has%20been%20mitigated%20now%20and%20we%20are%20still%20monitoring%20to%20make%20sure%20the%20service%20stability.%20Please%20try%20again%20and%20let%20me%20know%20if%20you%20still%20encounter%20this%20problem.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297731%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297731%22%20slang%3D%22en-US%22%3EReally%20sorry%20for%20all%20your%20inconvenience.%20This%20issue%20has%20been%20mitigated%20now%20and%20we%20are%20still%20monitoring%20to%20make%20sure%20the%20service%20stability.%20Please%20try%20again%20and%20let%20me%20know%20if%20you%20still%20encounter%20this%20problem.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297730%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297730%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EThanks%20for%20reporting%20this%20issue%20and%20sorry%20for%20all%20your%20inconvenience.%20This%20issue%20has%20been%20mitigated%20now%20and%20we%20are%20still%20monitoring%20to%20make%20sure%20the%20service%20stability.%20Please%20try%20again%20and%20let%20me%20know%20if%20you%20still%20encounter%20this%20problem.%20%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297589%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297589%22%20slang%3D%22en-US%22%3E%3CP%3EEveryone%20in%20my%20organization%20is%20having%20the%20same%20problem%20at%20the%20moment%2C%20feel%20like%20something%20broke%20or%20there's%20an%20update%20going%20on%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297580%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297580%22%20slang%3D%22en-US%22%3E%3CP%3EAlso%20having%20this%20problem.%20Tried%20different%20browsers%20and%20still%20in%20load%20forever%20and%20then%20error%20message.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297537%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297537%22%20slang%3D%22en-US%22%3E%3CP%3EExperiencing%20the%20same%20problem%2C%20cannot%20access%20any%20of%20my%20Forms.%20Screenshots%20below.%20Please%20resolve%20this%20issue.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F62139i8598F77DC8DDED96%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Microsoft%20forms%20screenshot%201.png%22%20title%3D%22Microsoft%20forms%20screenshot%201.png%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F62140i67756C09BF8BBF19%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Microsoft%20forms%20screenshot%202.png%22%20title%3D%22Microsoft%20forms%20screenshot%202.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297536%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297536%22%20slang%3D%22en-US%22%3E%3CP%3ESeveral%20folks%20in%20my%20organization%20are%20experiencing%20this%20problem%20today.%20We've%20tried%20accessing%20one%20of%20our%20forms%20multiple%20times%20unsuccessfully.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20advise.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%2C%3CBR%20%2F%3EMaggie%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297531%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297531%22%20slang%3D%22en-US%22%3E%3CP%3EAll%20my%20forms%20(15)%20have%20disappeared%20and%20I'm%20getting%20the%20same%20error%20message.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297529%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297529%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20getting%20the%20same%20error%20that%20people%20have%20mentioned%20before.%20I%20can't%20access%20any%20of%20my%20forms%20or%20create%20new%20ones%2C%20and%20I%20get%20the%20error%2C%20%22Sorry%2C%20something%20went%20wrong.%22%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297524%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297524%22%20slang%3D%22en-US%22%3E%3CP%3EGot%20the%20same%20error%20today.%20Can%20someone%20please%20help.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F62136iFE57DBD847130AA3%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Forms%20error.png%22%20title%3D%22Forms%20error.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-283735%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283735%22%20slang%3D%22en-US%22%3E%3CP%3EGetting%20a%20new%20error%20with%20a%20form%20this%20evening.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20682px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F59273i21BC1AA7C78AD818%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.PNG%22%20title%3D%22Capture.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20advise%20how%20to%20correct%20the%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3CBR%20%2F%3ESean%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-241780%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-241780%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I%20am%20using%20a%20Microsoft%20Form%20on%20Sharepoint%20and%20have%20started%20getting%20this%20same%20error%20message%20as%20of%20this%20morning%20on%20Sept%204%2C%202018.%26nbsp%3B%3CSPAN%3EPlease%20try%20again.%20Error%20code%3A%20631%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20status%20update%20on%20a%20fix%20for%20this%3F%20I%20appreciate%20your%20help.%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-182982%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-182982%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Kathy%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20experiencing%20this%20error.%20Could%20you%20help%20me%20look%20into%20it%3F%20Thank%20you%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20284px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F32280iB045C41F3500CFE6%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.PNG%22%20title%3D%22Capture.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-157176%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-157176%22%20slang%3D%22en-US%22%3E%3CP%3Ewe%20have%20experienced%20the%20problem%20with%20the%20error%20code%20631%2C%20with%20an%20important%20form%20we%20needed%20our%20insurance%20companies%20to%20fill%20out.%20We%20need%20your%20help%20and%20steps%20that%20we%20must%20follow%20to%20resolve%20the%20issue.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-156841%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-156841%22%20slang%3D%22en-US%22%3E%3CP%3EI%2C%20and%20all%20my%20users%2C%20are%20actively%20getting%20the%20same%20error%20again%20today%20(earliest%20noted%20was%207%3A20am%20(EST)%26nbsp%3Bthis%20morning).%20Issue%20persists.%20Can%20we%20please%20reopen%20this%3F%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-152062%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-152062%22%20slang%3D%22en-US%22%3EWe%20introduced%20another%20fix%206%20hours%20ago.%20The%20service%20has%20been%20running%20with%20health%20status%20in%20last%206%20hours.%20The%20issue%20has%20been%20resolved%20and%20we%20are%20closing%20this%20discussion.%20Thank%20you.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151858%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151858%22%20slang%3D%22en-US%22%3E%3CP%3EForms%20users%20run%20into%20the%20similar%20errors.%20We%20acknowledge%20that%20we%20are%20investigating%20the%20issue%20and%20will%20use%20this%20thread%20to%20post%20updates.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EApologize%20and%20thank%20you%20for%20your%20patience.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYour%20Microsoft%20Forms%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151847%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151847%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22office-form-info-title%22%20data-reactid%3D%22.0.3.2.0.0%22%3ELooks%20like%20a%20new%20bug%20has%20appeared.%3C%2FDIV%3E%0A%3CDIV%20class%3D%22office-form-info-title%22%20data-reactid%3D%22.0.3.2.0.0%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22office-form-info-title%22%20data-reactid%3D%22.0.3.2.0.0%22%3E-----------------%3C%2FDIV%3E%0A%3CDIV%20class%3D%22office-form-info-title%22%20data-reactid%3D%22.0.3.2.0.0%22%3ED%C3%A9sol%C3%A9...%20Nous%20avons%20rencontr%C3%A9%20un%20probl%C3%A8me%3C%2FDIV%3E%0A%3CDIV%20class%3D%22office-form-info-subtitle%22%20data-reactid%3D%22.0.3.2.0.1%22%3EVeuillez%20r%C3%A9essayer.%20Code%20d%E2%80%99erreur%26nbsp%3B%3A%201003%3C%2FDIV%3E%0A%3CDIV%20class%3D%22office-form-info-error-detail-container%22%20data-reactid%3D%22.0.3.2.0.3%22%3E%0A%3CDIV%20class%3D%22button-content%22%20data-reactid%3D%22.0.3.2.0.3.0.0%22%3E%26nbsp%3B%3C%2FDIV%3E%3CSPAN%20class%3D%22office-form-info-error-children%20office-form-info-children%22%20data-reactid%3D%22.0.3.2.0.3.1%22%3ED%C3%A9tails%20techniques%3C%2FSPAN%3E%3CDIV%20class%3D%22office-form-info-error-detail%22%20data-reactid%3D%22.0.3.2.0.3.2%22%3EID%20de%20session%26nbsp%3B%3A%2066b21879-c807-40f1-a4aa-7f20f351da73%2C%20ID%20de%20corr%C3%A9lation%26nbsp%3B%3A%20c4b63811-c999-41ee-8c81-9fb7e6e007dd%3C%2FDIV%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151836%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151836%22%20slang%3D%22en-US%22%3E%3CP%3Eit%20worked%20until%20one%20hour%20ago%20for%20me.%20%26nbsp%3BNow%20it's%20impossible%20to%20edit%20or%20answer%20my%20form.%20%26nbsp%3B%20hope%20we%20will%20not%20loose%20the%20information%20previously%20registered.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151833%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151833%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Kathy%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20see%20screenshot%20for%20the%20latest%20error%20code.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151832%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151832%22%20slang%3D%22en-US%22%3ENot%20working%20again%3CBR%20%2F%3EAhrrr.%20%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151829%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151829%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20hate%20to%20be%20the%20bearer%20of%20bad%20news%2C%20but%20having%20had%20my%20forms%20restored%2C%20the%20same%20fault%20has%20now%20started%20all%20over%20again!%3C%2FP%3E%0A%3CP%3ENow%20cannot%20access%20the%20forms%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151827%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151827%22%20slang%3D%22en-US%22%3ENow%20I%20got%20Something%20went%20wrong%20again.%20Just%20with%20another%20error%2C%201003.%20Is%20it%20just%20me%20or%20%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151780%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151780%22%20slang%3D%22en-US%22%3EKathy.%20I%20would%20like%20to%20thank%20you%20and%20the%20team%20for%20jumping%20on%20this%20and%20communicating%20it.%20%3CBR%20%2F%3E%3CBR%20%2F%3EIt%20is%20an%20example%20to%20others%20inside%20Microsoft%20that%20we%20need%20timely%20info%20when%20a%20service%20is%20impacted.%20Primarily%20to%20let%20our%20users%20know.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151770%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151770%22%20slang%3D%22en-US%22%3E%3CP%3EWe%3C!--%20%5BEnd%5D%20JSLL%20script%20includes%20--%3E%3C!--%20Facebook%20Pixel%20Code%20--%3E%3C!--%20DO%20NOT%20MODIFY%20--%3E%3C!--%20End%20Facebook%20Pixel%20Code%20--%3E've%20fully%20restored%20the%20service%20for%20all%20Forms%20users%20and%20will%20close%20this%20discussion.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3C!--%20%3Clink%20rel%3D%22stylesheet%22%20type%3D%22text%2Fcss%22%20href%3D%22%2Fhtml%2Fassets%2FContent%2Fpicchu2.css%22%20%2F%3E%20--%3E%3C!--%20%20%5BBegin%5D%20%20JSLL%20%20script%20%20includes%20%20--%3E%3C!--%20%5BEnd%5D%20JSLL%20script%20includes%20--%3E%3C!--%20Facebook%20Pixel%20Code%20--%3E%3C!--%20DO%20NOT%20MODIFY%20--%3E%3C!--%20End%20Facebook%20Pixel%20Code%20--%3E%3CSTRONG%3ESummary%20of%20impact%3C%2FSTRONG%3E%3A%20Between%2000%3A50%20GMT%20and%2011%3A15%20GMT%2C%20a%20significant%20number%20of%20users%20encountered%20%22Something%20went%20wrong%22%20errors.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ERoot%20cause%3C%2FSTRONG%3E%3A%20Architectural%20change%20to%20switch%20Forms'%20connection%20to%20SQL%20Azure.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EMitigation%3C%2FSTRONG%3E%3A%20Engineers%20checked%20in%20a%20fix%20to%20revert%20the%20code%20change%20and%20flushed%20impacted%20caches.%3C!--%20%5Bif%20lt%20IE%209%5D%3E%0A%20%20%20%20%20%20%20%20%3Cscript%20src%3D%22%2F%2Fazurecomcdn.azureedge.net%2Fcvt-20e11ce61890c08c0529911822233c9023ebc367df6c1050dec105e2b9628104%2Fscripts%2Fsundog%2Flib%2Fjquery-1.11.3.min.js%22%3E%3C%2Fscript%3E%0A%20%20%20%20%20%20%20%20%3Cscript%20src%3D%22%2F%2Fazurecomcdn.azureedge.net%2Fcvt-39b48b865ac33fd836f7810c7bc2f51100de219a0dd8d16e1d7dbb1c13eafef4%2Fscripts%2Fsundog%2Flib%2Frespond.min.js%22%3E%3C%2Fscript%3E%0A%20%20%20%20%20%20%20%20%3Cscript%20src%3D%22%2F%2Fazurecomcdn.azureedge.net%2Fcvt-b7b30007b93b2dbe40f31f11acc0f4962af6571c4aa2aa173f2a428c83e0b5d9%2Fbundles%2Fheader.js%22%20crossorigin%3D%22anonymous%22%20onerror%3D%22cdnfallback()%22%3E%3C%2Fscript%3E%0A%0A%20%20%20%20%3C!%5Bendif%5D--%3E%3C!--%20%5Bif%20gte%20IE%209%5D%3E%3C!--%3E%3C!--%3C!%5Bendif%5D--%3E%3C%2FP%3E%0A%3CSECTION%20class%3D%22section%22%3E%0A%3CDIV%20class%3D%22row%20row-size3%20column%22%20id%3D%22history-results-container%22%3E%0A%3CDIV%20class%3D%22row%22%3E%0A%3CDIV%20class%3D%22column%20small-11%22%3E%0A%3CP%3E%3CSTRONG%3ENext%20steps%3A%3C%2FSTRONG%3E%20Engineers%20will%20continue%20to%20investigate%20and%20prevent%20future%20occurrences.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3C%2FSECTION%3E%0A%3CP%3EThank%20you%20for%20your%20understanding%20and%20participating%20in%20this%20discussion.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYour%20Microsoft%20Forms%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CDIV%20class%3D%22lia-page%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20let%20us%20know%20if%20you%20still%20meet%20the%20issue.%20Thank%20you%20for%20your%20feedbacks%20and%20patience.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYour%20Microsoft%20Forms%20Team%3C%2FP%3E%0A%3CDIV%20class%3D%22lia-page%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151763%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151763%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20update%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151737%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151737%22%20slang%3D%22en-US%22%3E%3CP%3E%3C!--%20%3Clink%20rel%3D%22stylesheet%22%20type%3D%22text%2Fcss%22%20href%3D%22%2Fhtml%2Fassets%2FContent%2Fpicchu2.css%22%20%2F%3E%20--%3E%3C!--%20%20%5BBegin%5D%20%20JSLL%20%20script%20%20includes%20%20--%3E%3C!--%20%5BEnd%5D%20JSLL%20script%20includes%20--%3E%3C!--%20Facebook%20Pixel%20Code%20--%3E%3C!--%20DO%20NOT%20MODIFY%20--%3E%3C!--%20End%20Facebook%20Pixel%20Code%20--%3EWe%20would%20like%20to%20provide%20a%20quick%20update%3A%20we've%20identified%20the%20cause%20of%20this%20issue%20and%20have%20restored%20the%20service%20for%20the%20majority%20of%20Forms%20users.%20We%20will%20provide%20a%20further%20update%20once%20the%20service%20is%20fully%20back%20to%20normal.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you%20for%20your%20patience.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYour%20Microsoft%20Forms%20Team%3C%2FP%3E%0A%3CDIV%20class%3D%22lia-page%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151733%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151733%22%20slang%3D%22en-US%22%3EYes%2C%20seems%20to.%20But%20as%20a%20school%20%2F%20company%20I%20cannot%20rely%20on%20%22seems%20to%22.%20I%20need%20this%20to%20be%20officially%20fixed.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151729%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151729%22%20slang%3D%22en-US%22%3EWe%20got%20access%20as%20well..%20But%20for%20how%20long%3F%20What's%20the%20status%3F%20Has%20the%20issue%20been%20marked%20as%20fixed%20or%20how%20far%20are%20you%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151728%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151728%22%20slang%3D%22en-US%22%3E%3CP%3ESeems%20like%20the%20issue%20has%20been%20resolved.%20Thx%20a%20lot!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151718%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151718%22%20slang%3D%22en-US%22%3E%3CP%3EI%20got%20now%20access%20to%20my%20forms.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151715%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151715%22%20slang%3D%22en-US%22%3EHi%20Kathy%3CBR%20%2F%3ECould%20you%20give%20us%20a%20sense%20of%20how%20long%20do%20you%20think%20it%20will%20take%20to%20resolve%20this.%20I%20have%20some%20urgent%20deadlines%20related%20to%20the%20survey%2Fvotes%20that%20I%20was%20carrying%20out.%20I%20will%20have%20to%20work%20over%20the%20weekend%20to%20process%20them%20to%20release%20the%20results%20on%20Monday.%20And%20this%20is%20related%20to%20the%20whole%20terms%20teaching%20plans.%20So%20if%20this%20is%20Not%20likely%20to%20resolve%20quickly%20I%20will%20have%20to%20put%20alternate%20process%20%2F%20forms%20in%20place%20to%20avoid%20issues%20and%20complaints.%20If%20I%20can%E2%80%99t%20realise%20results%20by%20Monday%20it%20will%20have%20major%20implications%20on%20course%20delivery.%20Kind%20regards%20S%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151713%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151713%22%20slang%3D%22en-US%22%3EHi%20Kathy%3CBR%20%2F%3ECould%20you%20give%20us%20a%20sense%20of%20how%20long%20do%20you%20think%20it%20will%20take%20to%20resolve%20this.%20I%20have%20some%20urgent%20deadlines%20related%20to%20the%20survey%2Fvotes%20that%20I%20was%20carrying%20out.%20I%20will%20have%20to%20work%20over%20the%20weekend%20to%20process%20them%20to%20release%20the%20results%20on%20Monday.%20And%20this%20is%20related%20to%20the%20whole%20terms%20teaching%20plans.%20So%20if%20this%20is%20Not%20likely%20to%20resolve%20quickly%20I%20will%20have%20to%20put%20alternate%20process%20%2F%20forms%20in%20place%20to%20avoid%20issues%20and%20complaints.%20If%20I%20can%E2%80%99t%20realise%20results%20by%20Monday%20it%20will%20have%20major%20implications%20on%20course%20delivery.%20Kind%20regards%20S%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151706%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151706%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151696%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151696%22%20slang%3D%22en-US%22%3ECould%20you%20maybe%20pin%2Fstick%20this%20thread%20on%20top%20%3F%20I%20see%20loads%20of%20customers%20with%20the%20same%20error.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151691%22%20slang%3D%22en-US%22%3ERE%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151691%22%20slang%3D%22en-US%22%3EApologize%20for%20the%20service%20reliability%20issue%20.%20Microsoft%20Forms%20team%20is%20actively%20working%20on%20investigating%20this%20and%20in%20the%20process%20to%20identify%20a%20proper%20mitigation%20plan.%20We%20have%20created%20a%20discussion%20thread%20(Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error)%20to%20keep%20you%20updated.%20Thank%20you%20for%20your%20patience%20as%20we%20work%20to%20restore%20the%20Microsoft%20Forms%20service.%20It's%20our%20top%20priority%20to%20get%20this%20issue%20addressed%20as%20quickly%20as%20possible.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151682%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151682%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20letting%20us%20know.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1430378%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1430378%22%20slang%3D%22en-US%22%3EHi%2C%20I%20have%20encountered%20this%20problem%20again.%3CBR%20%2F%3EIt%20has%20been%20showing%20this%20error%20message%20for%20over%2024%20hours%20now.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1519153%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Forms%20-%20%22Something%20went%20wrong%22%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1519153%22%20slang%3D%22en-US%22%3EHello!%20I'm%20copying%20forms%20from%20my%20school%20account%20and%20ran%20into%20this%20same%20message.%20After%20several%20hours%20the%20situation%20is%20still%20the%20same.%20Have%20any%20ideas%3F%20Thanks!%3C%2FLINGO-BODY%3E
Highlighted
Microsoft

We would like to acknowledge that we're actively working on investigating a service reliability issue. We will use this discussion thread to keep our customer updated.

 

Summary of impact: Starting 01:00 UTC a significant number of users encountered "Something went wrong" errors. 

Preliminary root cause: Under investigation.

Mitigation: We've made progress narrowing down the problem and are in the process to identify a proper mitigation to restore the service. 

 

Thank you for your patience as we work to restore the Microsoft Forms service. It's our top priority to get this issue addressed as quickly as possible.

error.PNG

 

Your Microsoft Forms Team

39 Replies
Highlighted

Thanks for letting us know.

Highlighted
Apologize for the service reliability issue . Microsoft Forms team is actively working on investigating this and in the process to identify a proper mitigation plan. We have created a discussion thread (Microsoft Forms - "Something went wrong" Error) to keep you updated. Thank you for your patience as we work to restore the Microsoft Forms service. It's our top priority to get this issue addressed as quickly as possible.
Highlighted
Could you maybe pin/stick this thread on top ? I see loads of customers with the same error.
Highlighted
Highlighted
Hi Kathy
Could you give us a sense of how long do you think it will take to resolve this. I have some urgent deadlines related to the survey/votes that I was carrying out. I will have to work over the weekend to process them to release the results on Monday. And this is related to the whole terms teaching plans. So if this is Not likely to resolve quickly I will have to put alternate process / forms in place to avoid issues and complaints. If I can’t realise results by Monday it will have major implications on course delivery. Kind regards S
Highlighted
Hi Kathy
Could you give us a sense of how long do you think it will take to resolve this. I have some urgent deadlines related to the survey/votes that I was carrying out. I will have to work over the weekend to process them to release the results on Monday. And this is related to the whole terms teaching plans. So if this is Not likely to resolve quickly I will have to put alternate process / forms in place to avoid issues and complaints. If I can’t realise results by Monday it will have major implications on course delivery. Kind regards S
Highlighted

I got now access to my forms.

Highlighted

Seems like the issue has been resolved. Thx a lot!

Highlighted
We got access as well.. But for how long? What's the status? Has the issue been marked as fixed or how far are you?
Highlighted
Yes, seems to. But as a school / company I cannot rely on "seems to". I need this to be officially fixed.
Highlighted

We would like to provide a quick update: we've identified the cause of this issue and have restored the service for the majority of Forms users. We will provide a further update once the service is fully back to normal. 

 

Thank you for your patience.

 

Your Microsoft Forms Team

 
Highlighted

Any update?

Highlighted

We've fully restored the service for all Forms users and will close this discussion.

 

Summary of impact: Between 00:50 GMT and 11:15 GMT, a significant number of users encountered "Something went wrong" errors.

Root cause: Architectural change to switch Forms' connection to SQL Azure.

Mitigation: Engineers checked in a fix to revert the code change and flushed impacted caches.

Next steps: Engineers will continue to investigate and prevent future occurrences.

 

Thank you for your understanding and participating in this discussion. 

 

Your Microsoft Forms

 

 

 

 

 

Please let us know if you still meet the issue. Thank you for your feedbacks and patience.

 

Your Microsoft Forms Team

 
Highlighted
Kathy. I would like to thank you and the team for jumping on this and communicating it.

It is an example to others inside Microsoft that we need timely info when a service is impacted. Primarily to let our users know.
Highlighted
Now I got Something went wrong again. Just with another error, 1003. Is it just me or ?
Highlighted

Hi,

 

I hate to be the bearer of bad news, but having had my forms restored, the same fault has now started all over again!

Now cannot access the forms again.

Highlighted
Not working again
Ahrrr.
Highlighted

Hi Kathy,

 

Please see screenshot for the latest error code.

Highlighted

it worked until one hour ago for me.  Now it's impossible to edit or answer my form.   hope we will not loose the information previously registered.