Skip to main content

Hi,

 

I have signed the application and c an see that the manifest file updates. If I click the application directly in D:\IFS\IFSExt\IFST\repository\client\runtime File name: IFS.FND.EXPLORER it works fine. If I click the link on the splash page I receive the below error. The Deployment Provider url  looks like the link is incorrect but the Deployment url has the correct link. Would be great if someone knew where to update the link. 

 

PLATFORM VERSION INFO
    Windows             : 6.1.7601.65536 (Win32NT)
    Common Language Runtime     : 4.0.30319.36627
    System.Deployment.dll         : 4.0.30319.36415 built by: FX452RTMLDR
    clr.dll             : 4.0.30319.36627 built by: FX452RTMLDR_B
    dfdll.dll             : 4.0.30319.36415 built by: FX452RTMLDR
    dfshim.dll             : 4.0.41209.0 (Main.041209-0000)

SOURCES
    Deployment url            : http://server New link correct
                        Server        : Apache-Coyote/1.1
                        X-Powered-By    : Servlet 2.5; JBoss-5.0/JBossWeb-2.1
    Deployment Provider url        : http://server - link not correct

ERROR SUMMARY
    Below is a summary of the errors, details of these errors are listed later in the log.
    * Activation of http:server/client/runtime/Ifs.Fnd.Explorer.application resulted in exception. Following failure messages were detected:
        + Downloading http: server did not succeed.
        + The remote name could not be resolved: 'pre-lgpdcvifs01.londongateway.net'

COMPONENT STORE TRANSACTION FAILURE SUMMARY
    No transaction error was detected.

WARNINGS
    There were no warnings during this operation.

OPERATION PROGRESS STATUS
    * b13/01/2021 12:21:52] : Activation of http:gateway.net:62080/client/runtime/Ifs.Fnd.Explorer.application has started.

ERROR DETAILS
    Following errors were detected during this operation.
    * e13/01/2021 12:21:53] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
        - Downloading http://pre-client/runtime/Ifs.Fnd.Explorer.application did not succeed.
        - Source: System.Deployment
        - Stack trace:
            at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
            at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
            at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
            at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
            at System.Deployment.Application.DownloadManager.DownloadManifest(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ManifestType manifestType, ServerInformation& serverInformation)
            at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirect(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
            at System.Deployment.Application.DownloadManager.FollowDeploymentProviderUri(SubscriptionStore subStore, AssemblyManifest& deployment, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options)
            at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
            at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
            at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
        --- Inner Exception ---
        System.Net.WebException
        - The remote name could not be resolved: 'pre-'
        - Source: System
        - Stack trace:
            at System.Net.HttpWebRequest.GetResponse()
            at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

COMPONENT STORE TRANSACTION DETAILS
    No transaction information is available.

 

Regards

Gary

Assuming this is for Apps 8, have you tried a reconfiguration of the Application and sign the application using F1Mage?


Assuming this is for Apps 8, have you tried a reconfiguration of the Application and sign the application using F1Mage?

Hi Srikanth,

 

that is correct. Yes I ran a reconfiguration without any issues then signed the application using F1MAGE. 

Regards

Gary 


Can you please check the host name in your error details for any typos: 

pre-lgpdcvifs01.londongateway.net

See if you can ping the host name from another box.


Can you please check the host name in your error details for any typos: 

pre-lgpdcvifs01.londongateway.net

See if you can ping the host name from another box.

Hi 

the host name is wrong. Do you know of a way to update this? 

Regards

Gary 


Do you know where the incorrect name is getting picked up?

IFS Configuration or F1Mage?


Hi @crpgaryw ,

 

You can edit the name that is picked out by the F1 mage by making changing the URL’s in the “server.xml” file that is available in the client runtime folder (same location as F1mage). While this should work as a quick fix, to make this persistent you would need to manually update the <instance_name>_configuration.xml in IFS_HOME\instance\<instance_name> and reconfigure the application server instance. 

 

Cheers.


Hi There

the Server.xml and the configuration file already have the correct url’s in them. 

Regards

Gary 


Hi There

the Server.xml and the configuration file already have the correct url’s in them. 

Regards

Gary 

and I have ran a reconfiguration without any errors. 


Have you tried installing ".NET Framework 4.5.2" or "ClickOnce plugin for Firefox"?

 

 IFS Enterprise Explorer:

  • To run IFS Enterprise Explorer you need Microsoft .Net 4.5.2 or higher runtime.
    If you don't have it on your machine you need to download it from Microsoft or install it using Windows Update.
  • IFS Enterprise Explorer uses ClickOnce technology. To be able to start it from FireFox you need to install a ClickOnce plugin.