Path for script-only application did not contain a script-only application. Path: %1 Cause: Powershell cmdlets do not parse ...

Path for script-only application did not contain a script-only application.

Path: %1
Cause: Powershell cmdlets do not parse the contents of the path so they can't detect if it is a valid, script-only application until the Lync Server Script-Only Application service tries to load it. When it does, if it is not marked as a script-only application, this event will appear.
Resolution:
Either fix the path using the Set-CSServerApplication cmdlet or fix the script to include a  node.

Only one loose routing endpoint can be specified. To change the endpoint, configure the others as non-loose routing or terminate ... Open an existing Topology Builder file. Use this option if you have work in progress or if you have exported a topology from ... Operation failed, but rollback succeeded (that is, no data was modified). Correct any errors and try to perform the operation ... Partner discovery is not available with the Default Route routing method. To change to DNS SRV routing, use Lync Server Management ... Path for script-only application did not contain a script-only application. Path: %1 Cause: Powershell cmdlets do not parse ... Peer-to-peer sessions where the user sees an error that is not expected to happen in a well configured system (for example, ... Peer-to-peer sessions where the user sees an error that might be expected to happen in a well configured system (for example, ... Per-second rate of conferences automatically deactivated by the Focus. It does not include conferences deactivated by the ... Per-second rate of conferences that could not be automatically deactivated by the Focus. It does not include conferences ...