Message-ID: <8016161.1075852361306.JavaMail.evans@thyme>
Date: Fri, 19 Oct 2001 04:49:00 -0700 (PDT)
From: d.alexander@enron.com
To: d.alexander@enron.com, justin.o'malley@enron.com, chris.gaskill@enron.com, 
	jay.reitmeyer@enron.com, sheila.chang@enron.com, 
	adam.bayer@enron.com, aaron.berutti@enron.com, 
	milen.kurdov@enron.com
Subject: Reporting Status
Cc: david.dronet@enron.com, yan.wang@enron.com, rishi.mehta@enron.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Bcc: david.dronet@enron.com, yan.wang@enron.com, rishi.mehta@enron.com
X-From: Alexander, Kim D </O=ENRON/OU=NA/CN=RECIPIENTS/CN=KALEXAN2>
X-To: Alexander, Kim D </O=ENRON/OU=NA/CN=RECIPIENTS/CN=Kalexan2>, O'Malley, Justin </O=ENRON/OU=NA/CN=RECIPIENTS/CN=Jomalley>, Gaskill, Chris </O=ENRON/OU=NA/CN=RECIPIENTS/CN=Cgaskill>, Reitmeyer, Jay </O=ENRON/OU=NA/CN=RECIPIENTS/CN=Jreitme>, Chang, Sheila </O=ENRON/OU=NA/CN=RECIPIENTS/CN=Schang2>, Bayer, Adam </O=ENRON/OU=NA/CN=RECIPIENTS/CN=Abayer>, Berutti, Aaron </O=ENRON/OU=NA/CN=RECIPIENTS/CN=Aberutti>, Kurdov, Milen </O=ENRON/OU=NA/CN=RECIPIENTS/CN=Mkurdov>
X-cc: Dronet, David </O=ENRON/OU=NA/CN=RECIPIENTS/CN=Ddronet>, Wang, Yan </O=ENRON/OU=NA/CN=RECIPIENTS/CN=Ywang>, Mehta, Rishi </O=ENRON/OU=NA/CN=RECIPIENTS/CN=Rmehta2>
X-bcc: 
X-Folder: \JREITME (Non-Privileged)\Inbox
X-Origin: REITMEYER-J
X-FileName: JREITME (Non-Privileged).pst

All Reports are running this morning without incident.

Kim

>  -----Original Message-----
> From: 	Alexander, Kim D  
> Sent:	Thursday, October 18, 2001 5:00 PM
> To:	Alexander, Kim D; O'Malley, Justin; Gaskill, Chris; 
> Reitmeyer, Jay; Chang, Sheila; Bayer, Adam; Berutti, Aaron; 
> Kurdov, Milen
> Cc:	Dronet, David; Wang, Yan; Mehta, Rishi
> Subject:	Tomorrow Reports
> 
> We've identified the cause of the reporting failures on the 
> analysts PCs this morning 
> to be Cube Security related.  During the migration we'd 
> checked the Cube Admin
> console to ensure all users were migrated successfully.
> 
> Although all users were displayed, we found this morning that 
>  only IT accounts  still had 
> access to the cube.  We've since refreshed and update the 
> cube user list and the analyst
> accounts are now again able to run reports without incident. 
> 
> To be sure check the status tonight and come in prior to 7am 
> if there are any problems.
> 
> thanks, 
> Kim