"we couldn't send this message" - Microsoft Community

-

hi, i'm using microsoft lumia 640, upgraded windows 10, when i'm trying send text message showing "we couldn't send message" few days back.

hi,

this possible software issue. isolate case, please answer following questions:

  • which operating system (os) build using? check, go settings > system > about > more info.
  • what troubleshooting steps have done far?

we're looking forward reply.

regards.



Mobile Devices / Microsoft Lumia and Nokia Lumia / Settings / 600-series



Comments

Post a Comment

Popular posts from this blog

Known solutions for hybrid migrations errors - Microsoft Community

-
technical level : intermediate summary this article documents of common errors related failed hybrid migrations, along steps resolve them or fix suggestions, there multiple root causes. in case need guidance extracting detailed migration errors or analyzing migration report powershell, please consult our below article, step step instructions: how extract , analyze errors hybrid migration report using powershell if had experienced new error missing list , found solution, more welcome share here, because consolidate initiative , other persons fix migration issues faster. details 1) migrationpermanentexception: must specify primaryonly parameter. error can occur when attempt migrate cloud on-prem mailbox via migration batch eac, online archive exists user. fix: in order migrate primary mailbox office 365, need start mailbox move following command, exchange online powershell: new-moverequest – identity <user > -remotec...
Read more

Deploying Office 365 is failing to write "updatepath" to the - Microsoft Community

-
i've been having problems getting office 365 deployed way want. what i'm trying deploy "clicktorun" version network file share (unc path) , configure future updates unc path on network file share (different subdirectory). if read deployment documentation if download updated versions of office via odt , put on "updatepath" installer should pull there it's updates. as mentioned, first problem getting deployment work add updatepath registry keys. this setup configuration file using. <configuration>   <add version="16.0.7766.2099" officeclientedition="64" channel="deferred">     <product id="o365proplusretail">       <language id="en-us" />     <excludeapp id= "access" />     </product>   </add>   <updates enabled="true" updatepath="\\server\share$\microsoft\office\office365proplus...
Read more

Microsoft Office 2013 reset rearm count - Microsoft Community

-
microsoft office 2013 rearm count has reached 0.  have tried uninstall microsoft office 2013 using add/remove programs, fixtool, , microsoft's vbs script.  have searched registry *0ff1ce , *office delete remaining registry keys.  unfortunately, when reinstall microsoft office 2013 on vmware windows 7 master image, rearm count not reset , continue receive error message "there error when trying rearm office.  can try passing sku id parameter.  passing sku id necessary if relying on activation to permit , additional rearm. error: 0xc004d307 on computer running microsoft windows non-core edition, run 'slui.exe 0x2a 0xc004d307 display the error text".   hi joe, there few ways have activation of office program rearmed through server or using command prompt commands. since you've performed few troubleshooting steps suggested on thread, best have raised on our technet foru...
Read more