title: VBA run time '1004' error when connected via VPN
body: <p>I've searched through several forums and have found similar questions, but not my specific problem.</p>
  
  <p>I have a macro that saves the active workbook to the specific user's folder, and saves a dated, xlsx, version in a sub folder. My macro-enable workbook is used by both in-office and remote associates. The in-office associates have no issue using this macro to save &amp; archive the workbook to their folder, and, up until last week, the remote associates using VPN had no issues either. </p>
  
  <p>However, over the past few days the remote associates using VPN have been receiving an error like <code>run time error '1004': The specified dimensions are not valid for the current chart type</code> and the code hangs on the <code>ActiveWorkbook.SaveAs</code> line at the end. Why would this error be coming up for a <code>.SaveAs</code> issue? I'm at a loss.</p>
  
  <pre><code>MainPath = "O:\Revenue Management\Centralized Revenue Management Service\CRMS Hotels\"
  sPathSeek = MainPath &amp; strPropNo &amp; "*"
  sFile = Dir(sPathSeek, vbDirectory)
  sFileCheck = MainPath &amp; sFile &amp; "\Strategy Pack"
  sBuildHist = MainPath &amp; sFile &amp; "\Strategy Pack\" &amp; year1 &amp; "\"
  filePath = MainPath &amp; sFile &amp; "\Strategy Pack\" &amp; propNo &amp; " Strategy Pack.xlsm"
  histPath = MainPath &amp; sFile &amp; "\Strategy Pack\" &amp; year1 &amp; "\" &amp; propNo &amp; " Strategy Pack " &amp; STRdate &amp; ".xlsx"
  iLength = Len(Dir(sFileCheck, vbDirectory))
  iLength2 = Len(Dir(sBuildHist, vbDirectory))
  
  If iLength = 0 Then
  MkDir (sFileCheck)
  End If
  
  If iLength2 = 0 Then
  MkDir (sBuildHist)
  End If
  
  'Save Master Workbook
  Application.DisplayAlerts = False
  ActiveWorkbook.SaveAs FileName:=filePath,
  
  FileFormat:=xlOpenXMLWorkbookMacroEnabled, CreateBackup:=False
  </code></pre>
  
  <p>The file I am trying to save over is also a .xlsm file.
  I've tried removing all charts.
  I've tried re-saving the master file.</p>
  
  <p><sub>It's worth noting that the same day this started happening, my VPN access would not log in until our systems administrator unlocked it (which was a first)</sub></p>