MID server Script File sync issue

[chadlockwood]

I am creating MID Server script files for all of my PowerShell activities because they are supposed to automatically sync between all MID servers. I create the script file in the Dev instance, in an update set, and it is automatically synced to all my MID servers. However, when I push the update set to the test environment, the script file is not synced automatically. I thought at one time restarting the MID servers after pushing the update set caused the automatic sync, but that doesn't appear to be the case. I now have to set the script file to inactive, save, set to active, save to get the sync to happen.

Does anyone know if this sync is supposed to be automatic based on updates in an update set? If so, how often does it happen and what triggers it? If not, what would be the best way to cause this sync to happen?

Regards,

Chad

[staceyrocheleau]

It should be automatically synced and I usually do updates between environments through an update set without issue. I create a separate folder and put my scripts in there and it's always worked.

[chadlockwood · Accepted solution]

Turns out it was one of the script files that was causing the issue. The file was exported, deleted, and reimported and all is well.

[bennyphipps]

Hi,

I had exactly the same issue and I think I managed to find out specifically what the problem was...   If you have a special character in the script files name it causes all kind of trouble.   I had a file Office365_get_O365_SM_name&owner.ps1 and the & was causing all files in the script folder on local MID host to be removed.   most likely cos the XML payload was getting disrupted somehow.

Ben

[SNowUser11]

Hi,

Please guide is the script custom one or do we have any feature in ServiceNow to autosync which is applicable to all MidServers to be in sync.  

Thanks