Novell Home

My Favorites

Close

Please to see your favorites.

Novell Vibe Add-In and "Edit this file" feature stopped working

This document (7013252) is provided subject to the disclaimer at the end of this document.

Environment

Vibe 3.0
Vibe 3.1
Vibe 3.2
Vibe 3.3

Situation

Edit in place feature gives an invalid username and password error, but the credentials are correct.
The remote server returned an error: (401) Unauthorized.

Resolution

  1. Go to the patch finder website
  2. Under the Select a Product drop down menu, choose Vibe
  3. Expand Vibe 3.3
  4. Click on Vibe - Updated Java Applets x86-64 x86
  5. Download the zip file that is appropriate for the Vibe version running
  6. Follow the instructions from the readme file to apply the patch

Additional Information

The following error is returned by the system event log from the workstation:

ERROR 2013-09-09 07:56:31,547 Novell.Collaboration.Vibe.VibeProvider [5] - Basic Auth failed while connecting to: https://vibesite.com
System.ServiceModel.Security.MessageSecurityException: The HTTP request is unauthorized with client authentication scheme 'Basic'. The authentication header received from the server was 'Basic realm="Teaming"'. ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized.
   at System.Net.HttpWebRequest.GetResponse()
   at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   --- End of inner exception stack trace ---
 
Server stack trace:
   at System.ServiceModel.Channels.HttpChannelUtilities.ValidateAuthentication(HttpWebRequest request, HttpWebResponse response, WebException responseException, HttpChannelFactory factory)
   at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory factory, WebException responseException, ChannelBinding channelBinding)
   at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
 
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Novell.Collaboration.Vibe.Service.TeamingServiceSoap.admin_getReleaseInfo(String accessToken)
   at Novell.Collaboration.Vibe.VibeProvider.<>c__DisplayClass2.<ValidateClient>b__0()
   at Novell.Collaboration.Vibe.VibeProvider.<>c__DisplayClass5`1.<ServiceCall>b__4()
   at Novell.Collaboration.Vibe.VibeProvider.WrapServiceCall(TeamingServiceSoapClient vibe, Action command)

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7013252
  • Creation Date:11-SEP-13
  • Modified Date:11-SEP-13
    • NovellVibe

Did this document solve your problem? Provide Feedback