cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to Subscribe - SUP Windows Native Application exceptions

Former Member
0 Kudos

Greetings -

Has anyone experienced the following Subscribe exception in Windows Native (C# - Win32)?  HTTP_BAD_STATUS_CODE - 404

iAnywhere.Data.UltraLite.ULException: MobiLink communication error -- code: 86, parameter: 404, system code: 0

   at iAnywhere.Data.UltraLite.ULConnection.RuntimeErrorCheck()

   at iAnywhere.Data.UltraLite.ULConnection.Synchronize()

   at com.sybase.afx.db.ConnectionUtil.Synchronize(ConnectionWrapper dbConn, SyncStatusListener listener, Connection connection, String[] mboNames, Hashtable tableMBOMap) in u:\codegen\afx\src\cs\com\sybase\afx\db\ConnectionUtil.cs:line 244Details:

StreamErrorCode =HTTP_BAD_STATUS_CODE

StreamErrorSystem = 0

StreamErrorParameters = 404

I have been chasing this issue for some time now.  I receive the MBOs from another developer that creates and publishes the MBO package to me.

Environment - VPN to SCC, SUP 2.1.2, Windows VS2010

Any assistance would be greatly appreicated.  Thank you in advance.

Accepted Solutions (0)

Answers (2)

Answers (2)

hongqiao
Discoverer
0 Kudos

I encoutnered this once. The client e2ee key doesn't match server's. There should be errors in server log like this:

[-10117] Stream Error: Mismatched end-to-end encryption keys

[-10117] Stream Error: Unable to continue unknown HTTP session

I resolved it by removing client e2ee key and sync again.

Hope this helps.

Former Member
0 Kudos

Hi David,

Error 404 usually means "not found". Have you made sure that your MBO is successfully deployed to the server? It sounds like the app cannot find the MBO.

Rocky

Former Member
0 Kudos

Hi Rocky

Thanks for responding so quickly.  I have been assured by my colleague the application and MBOs have been deployed, and the SUP SCC services are running.  The issue throws an exception in Subscribe() and Synchronize().  If you see anything obviously wrong with this flow ... please advise. This is essentially the workflow in my code:

  1. Set Application Identifier: "AppName"
  2. Setup Callback Handler
  3. Set GetSynchronizationProfile().ServerName = HOST + DOMAIN
  4. Create ConnectionProperties cp = app.ConnectionProperties();
  5. cp.ServerName = HOST + DOMAIN
  6. cp.PortNumber = 5001
  7. cp.NetworkProtocol = "http"
  8. cp.ActivationCode = "123"
  9. Create LoginCredentials = new LoginCredentials(UNAME, PW)
  10. if(app.RegistrationStatus != RegistrationStatus.REGISTERED)
  11.     app.RegisterApplication(timeoutvalue)
  12. else
  13.      app.StartConnection(timeoutvalue)
  14. Subscribe()
  15. if(!IsSynchronized("default")
  16.      DisableChangeLog()
  17. Synchronize()
  18.      ISynchronizeGroup sg = GetSynchronizationGroup("default")
  19.      sg.EnableSIS = true
  20.      sg.Save()
  21.      Synchronize()
  22.      EnableChangeLog()
  23. GenericList<ISynchronizationGroup> sgs = new GenericList<ISynchronizationGroup>()
  24. sgs.Add(GetSynchronizationGroup("default"))
  25. BeginSynchronize(sgs, "mycontext")
  26. Ready ....