OfficeDev / teams-toolkit

Developer tools for building Teams apps
Other
434 stars 171 forks source link

bug report: m365.UnhandledError #10614

Closed Ivan-DeePlan closed 6 months ago

Ivan-DeePlan commented 6 months ago

An unexpected error has occurred while performing the M365 task. {"stack":"Error: getaddrinfo ENOTFOUND at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26)\n at GetAddrInfoReqWrap.callbackTrampoline (node::130:17)","message":"getaddrinfo ENOTFOUND titles.prod.mos.microsoft.com","code":"ENOTFOUND","config":{}}

stack: UnhandledError: An unexpected error has occurred while performing the M365 task. {"stack":"Error: getaddrinfo ENOTFOUND at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26)\n at GetAddrInfoReqWrap.callbackTrampoline (node::130:17)","message":"getaddrinfo ENOTFOUND titles.prod.mos.microsoft.com","code":"ENOTFOUND","config":{}} at Object.assembleError (:14:6801865) at PackageService.sideLoading (:14:5921326) at processTicksAndRejections (node::95:5) at PackageService. (:14:6670138) at M365TitleAcquireDriver.handler (:14:6242408) at :14:6241362 at Object.wrapRun (:14:6565429) at M365TitleAcquireDriver.execute (:14:6241315) at M365TitleAcquireDriver. (:14:6245367) at Lifecycle.executeImpl (:14:6005349) at Lifecycle.execute (:14:6002506) at Coordinator.provision (:14:6046302) at Coordinator. (:14:6670138) at FxCore.provisionResources (:14:6599247) at FxCore.exports.EnvWriterMW (:14:6512104) at FxCore.exports.ContextInjectorMW (:14:6673890) at FxCore.exports.ConcurrentLockerMW (:14:6672841) at envLoaderMWImpl (:14:6512051) at FxCore. (:14:6510965) at FxCore.exports.ProjectMigratorMWV3 (:14:6704441) at FxCore.exports.ErrorHandlerMW (:14:6674387) at FxCore. (:14:6670138)

swatDong commented 6 months ago

Hi @Ivan-DeePlan , from your error message "message":"getaddrinfo ENOTFOUND titles.prod.mos.microsoft.com", it failed to connect to the M365 task service titles.prod.mos.microsoft.com.

Could you please try to check the network connection? For example, execute command nslookup titles.prod.mos.microsoft.com to check the DNS. Or, does your dev machine run behind any proxy?

Ivan-DeePlan commented 6 months ago

Hi SwatDong, thank you for the quick reply. The problem that was occurring is no longer present. After refreshing the connection, everything returned to normal.

adashen commented 6 months ago

close as the issue solved