This is a known bug in the 2.0.0.0.9.4 software. We are working to resolve this. There is no known work around at this time.