cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
258
Views
4
Helpful
5
Replies

CUCM Error Message "Name does not match any filter pattern"

TimEckert
Level 1
Level 1

Hello everyone,

I am encountering the following error message when attempting to install COP files on my Cisco Unified Communications Manager (CUCM) Version 14.0.1.11900-132:

Name does not match any filter pattern

System Environment:

  • CUCM Version: 14.0.1.11900-132
  • Unified OS Version: 7.0.0.0-7.i386

Has anyone experienced this specific error with CUCM Version 14.0.1.11900-132? What steps could be taken to resolve this issue? I have already tried various SFTP servers.

Screen 1.png

 

Screen 2.png

Thank you in advance for your support!

5 Replies 5

Brad Magnani
Cisco Employee
Cisco Employee

14.x already includes the support for sha512 and the new signing key, which is why it's saying that particular COP file doesn't match any filter pattern - you don't need it since anything newer than 12.5.1.12013-1 supports it natively now. 

As far as the locale COP file you're trying to install, sometimes the error can be misleading, the best place to start is pulling the install/upgrade logs from RTMT or file get install * from CLI to see what further details it may provide.

Thanks.

I think you want so see that?

https://tmpfiles.org/dl/22510399/logs.txt

When checking the MD5 value on the portal, it displays a different value (097ecfc8ded9c5923759e544a6fecfdb) than the one shown in your OP image. Please try downloading the files again, upload them to the SFTP, and give it another attempt.

 

NithinEluvathingal_0-1742291337643.png

 



Response Signature


Hello Nithin,

I have sent you a private message regarding this topic.

Best Regards

I forget the exact versions where this happened, but I have had multiple cases where the installation of a small COP file failed when using FTP. You could use the same exact file in the same place on the same server and it would work with SFTP. I have no idea what gremlins cause that issue, but it was definitely a thing.