-
Brian Schanen joined Autodesk in 2005 as a Product Designer and currently is a Customer Success Engineer for Autodesk’s Data Management products. Brian has taught at Autodesk University numerous times and has authored white papers on Vault and Productstream. He works with customers to implement a complete digital prototyping solution specializing in Autodesk Inventor, Autodesk Vault and Productstream. Brian lives near Detroit, Michigan.
-
Logs, logs, logs
August 28, 2008, 09:24 PM Brian SchanenOne of the most important facets of lodging a data management support case and probably the main delay in diagnosis and resolution is the collection and documentation of error logs. Below is a list of the important logs and locations where they can be found.Supporting your case with these logs goes a long way to identifying and rectifying the problem:
FilesClient / ServerLocationInstallation LogsClient / Server%temp%\Prechecks.xmlPrechecks.xlsAutodesk Productstream 2009 Install.logAutodesk Productstream 2009 Setup.logAutodesk Vault 2009 Install.logAutodesk Vault 2009 Setup.logAutodesk Data Management Server 2009.logAutodesk Productstream Explorer 2009 Install.logAutodesk Productstream Explorer 2009 Setup.log“Logs for additional install components”SQL Installation LogsServerC:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\Vault Error Logs (*.log)(XP, 2000, 2003)ServerXP, 2000, 2003 –C:\Documents and Settings\All Users\Application Data\Autodesk\VaultServer\Filestore\Vista –C:\Program Data\Autodesk\VaultServer\FilestoreSQL Server Log FilesServerC:\Program Files\Microsoft SQL Server\MSSQL$AUTODESKVAULT\LOG\Event Viewer Logs(System & App *.evt)Client / ServerStart > Run > “eventvwr” > OpenRight click Sys & App logs and “Save Log File As”IIS Logs (*.log)Server%systemroot%\System32\logfilesdwg & dwf iFilter Log FilesServerC:\Documents and Settings\<ComputerName>\ ASPNET\Local Settings\Temp\Index Block Attributes (dwg files)ServerC:\Program Files\Autodesk\Data Management Server 2009\Server\Web\Services\FilterConfig.xml-Brian Schanen
You must be logged in to post a comment.