We were able to determine this is caused by using a .aspx page. If the page is a .asp or other server language, it works correctly. The workaround would be to add Pro Maps to a page that is not a .aspx and then copy the include code to the .aspx page to get the maps applied.