I am running Lync 2013 client on Windows 7, connecting to a Lync 2013 Server.
When attempting to add a participant to a Lync conversation, the invitee is added to the conversation's Participants list, but after a few seconds is removed and I receive the following message:
An error occurred.
When contacting your support team, reference error ID 486 (source ID 239).
Troubleshooting information is available online, including best practices for using Lync.
Learn More
The user I attempted to invite never receives a call.
The "Learn More" text is a link which sends to :
http://r.office.microsoft.com/r/rlidUCErr10?clid=1033&p1=0&p2=29&p3=141&p4=141&p5=141&p6=141
This address is in turn forwarded to:
https://support.office.com/en-us/article/Generic-Error-b5517285-d4e0-4a92-a58b-96a066d9f3c9?ui=en-US&rs=en-US&ad=US
This page is a reference for "Generic Error" in Lync 2010...
I can find no information on this error anywhere... What does this error mean?
Is there a way to solve it?
This error means : "Cannot reach [user name]. Try again later."
When you try add this participant, can you verify is there any local extension or PSTN number associated with him. because some times when you try to call Lync to Lync it gets forward to his extension or PSTN number.
But you could try to get help from your support team.
Related
In moodle I am getting the following error on enrolling the user. But, User get enrolled in course when we check refresh the page but It shows the error on enrolling.
Also I am using role_assigned event in my custom auth block .Whenever I enroll user in course from enrollment methods the event get called succefully but when I try to enroll user in course from enrolled users my event doesnt get called and the error get displayed.
Please help me out.
The most typical reason is that you have debugging messages printed in the response from the server. Open your Web Developer Tools and inspect the request in Network tab. Check that the response from the server is valid JSON.
I received the credentials to start developing with Sabre (IPCC, Password, Sign-in, and TA) but I am unable to create a session.
It gives me the error "ICE security system: 606"
I found this on https://developer.sabre.com/docs/soap_basics/status_codes_and_errors
USG_SECURITY_ICE_ERROR
Internal
The client application needs to stop processing for at least 500
milliseconds before attempting to retry the message.
But there was nothing with "606" beside it, so I don't know if that's the correct message or not. Any thoughts?
USG_SECURITY_ICE_ERROR can occur for a lot of reasons, in particular, for the error code 606 it means that the user you were trying to use has not been provisioned with necessary accesses.
If that user was given by Sabre, I recommend you to contact the help desk so they can engage the corresponding team. If it was created by the agency and you want to use it, please contact your account executive in order for them to request the access.
I am doing some work on Lync/Skype meeting integration. In order to make this work, I need to get hold of the GRUU/SIP information for events/meetings.
Currently I have some success by using EWS against Office365. I query for the OnlineMeetingConfLink extended property, and if the meeting is Skype-enabled, get the SIP.
However, when this meeting is forwarded to our own Exchange (2010 SP2), these properties are not added to the invitation. They are not present in any headers or anything.
The message body contains the Lync URL and Skype Conference ID, but those are not usable/parsable in a reliable way.
Any pointer to documentation or suggestions are welcome.
I've facebook account and a fan page defined within this account.
I'm using XMPP to send private messages using the following Java code
http://yauritux.wordpress.com/2011/09/24/facebook-chat-with-smack-xmpp-api/
I can easily send and receive messages using my user id and password.
However when I try to use my page user ID I'm getting the following error:
SASL authentication PLAIN failed: not-authorized (stack below).
I tried to use pidgin but I'm getting the same error.
Let me know if you've a solution or direction on how to send a message as a page and not as a user.
Thank you in advance,
Moshe
SASL authentication PLAIN failed: not-authorized:
at org.jivesoftware.smack.SASLAuthentication.authenticate(SASLAuthentication.java:337)
at org.jivesoftware.smack.XMPPConnection.login(XMPPConnection.java:203)
at org.jivesoftware.smack.Connection.login(Connection.java:348)
at com.maiff.was.connectors.impl.fb.FBConsoleChatApp.login(FBConsoleChatApp.java:55)
at com.maiff.was.connectors.test.ConnectorTestMain.initFB(ConnectorTestMain.java:55)
at com.maiff.was.connectors.test.ConnectorTestMain.main(ConnectorTestMain.java:18)
Pages can only "reply" to user messages, and i am not sure if it even works with XMPP. Keep in mind that the Chat API is deprecated btw: https://developers.facebook.com/docs/chat/
Meaning, after April 2015 it will not work anymore, not even with users.
For Page conversations, there is a specific API endpoint to reply to messages: https://developers.facebook.com/docs/graph-api/reference/v2.2/conversation/messages
I am facing the same problem as seen in this http://forge.prestashop.com/browse/PNM-1165
It says this following message after I click on 'pay with paypal'
Error occurred:
Please try to contact the merchant:
PayPal response:
->
I don't know what to do T^T
Im using prestashop 1.5.4 and paypal module 3.5
There is one reply suggestion from Francois Gaillard added a comment - 29/Mar/13 9:29 AM
He said that
This issue occurs when your server IP has been blocked by the PayPal's API. If you are running share hosting environment the server can be banned blacklisted by PayPal.
Please, try to contact PayPal support they should be able to help you.
Let us know when you have more details please.
Thank you,
Kind regards.
That answer is incorrect in as much that we do not block IP addresses to our API endpoints without making the merchant aware.
It is correct, from our experience, that the above error occurs in PrestaShop when your server is unable to establish a successful HTTPS connection with our API endpoint.
I suggest you take a look at General troubleshooting - API timeout and run the tests provided in it.
Pay special attention to the AT&T block we mention in there, as we've seen a large number of API callers getting blocked at that level.
Unfortunately that block is beyond our control - but we've heard good reports of merchants getting in touch with AT&T and getting that block lifted (if confirmed to be blocked there).