Hi Marcel,

I also getting same error message again and again what to do.

Thank you,

Alolika

please reply urgently. I have to give Demo to Client.

Hi Marcel,
This happens when you call external html page (asp.net on iis or such) inside SB1 app. This is a bug that is happening for us as well. We use SB1 OS 31.

If your html stays inside SB1 userdrive folder then it should work fine.
Best option is to use HTML/JS/CSS inside your sb1 app and call your IIS resources using RESTFul services.

Vinothini B
Spritle Software

SOLVED!

The sui.apps.js file expects a parameter from the webpage when it loads… and if you do not pass the parameter this message pops on the screen

   /*     * When we start application, we start a countdown for the app to load,     * if the app loads, we receive a hiAcceped message and remove the timer,     * otherwise, create a notification to inform the user, and give him two chices: Wait and Quit      */    app.loadTimeoutHandler = function() {  var notificationMessage = 'Application ' + app.name + ' is busy or not responding!';  if(!sui.apps.signal){   notificationMessage = 'Application ' + app.name + ' cannot load due to lost connectivity!';   }    sys.fn.notify({             type: sys.notifications.system,             priority: sys.priority.high,             title: 'System Message',             message: notificationMessage,             buttons: ['Wait', 'Quit'],             actions: [function() {                 if(app.loadTimeout){      clearTimeout(app.loadTimeout);      delete app.loadTimeout;        app.loadTimeout = window.setTimeout(app.loadTimeoutHandler, config.waitForResponseTimeout);     }             }, function() {     clearTimeout(app.loadTimeout);     delete app.loadTimeout;     var id = app.id;     sys.mi.kill(id);          sui.apps.startedApps[id] = null;     delete sui.apps.startedApps[id];
     sys.apps.running[id] = null;     delete sys.apps.running[id];
                 sui.apps.showLauncher();             }]     });    };    app.loadTimeout = window.setTimeout(app.loadTimeoutHandler, config.waitForResponseTimeout);