"Absolute path information is required" bug.

"Absolute path information is required" bug.

• Swati Sucharita

  Hi, all logs in Event viewer don't contain useful information. I cleared all logs and repeated error and all logs were empty.
  
  Regards,
  Bozydar
  
  PS. Error string "Absolute path information is required." is olny in the mscorlib.dll (system partition) .
  
  
  

• CoolMax

  bozydar wrote:

  My logs are empty and I have proper value ('D:') in ProgramFilesDir (HKLM/Software/Microsoft/Windows/CurrentVersion).

  
  try D:\
  
  i bet it will work...
  
  
  

• software786

  hi,
  
  i have the same problem, with this event-log message:
  "One or more Visual Studio templates is invalid and will not be displayed."
  
  But now, i discovered the problem:
  I changed my ProgramFilesDir (HKLM/Software/Microsoft/Windows/CurrentVersion) to d:
  
  If you change your ProgramFilesDir back to c:\Program Files it should work (it worked an my machine ;)
  
  But indeed, imo it's a bug...
  
  Witi
  
  

• Alagappapillai

  OK. I have got these dumps. Where should I send these dumps (email, please)
  
  Regards,
  Bozydar
  
  

• Don Stuber

  I have the same problem.
  
  

• SlideGuitarist

  If you are seeing the error msg that the Visual Studio Template files are invalid, you should see the reason logged in your application event vwr. Can you check your application event viewer to see if there are any VSTemplate related error messages To open the event viewer go to the control panel->Administrative tools->Event viewer and click on the 'Application' node.
  
  Thanks,
  -Prasadi
  
  

• curtmack

  Hi, can you check your application event viewer to see if there are any VSTemplate related error messages To open the event viewer go to the control panel->Administrative tools->Event viewer and click on the 'Application' node.
  
  Let us know what errors you see there.
  
  Thanks,
  -Prasadi
  
  

• kabuki

  The application event log contains the details about what went wrong (in 99% of the cases).  These detailed events are added to the log when Visual Studio is installed.  You may have to scroll down if it's been a while since you installed the product.  Also, you can force these events to be logged again by running 'Devenv /installvstemplates' from a command prompt.
  
  It doesn't sound like this is the kind of problem that the template logging system is going to be able to provide much detail.  The only real solution will be found by identifying the source of the error.  The message comes from an exception in the CLR, I need a call stack at the point the problem occurs.
  
  Below is a set of instructions for how to collect this dump.  Anyone able to collect a dump can email it to me directly.
  
  1.  Install Debugging Tools for Windows.  You can install them from http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx (assuming you're running on an x86 machine; other platforms are also supported).
  2.  Create a text file with the following lines in it -- call it dump.scr:

  sxe -c ".dump /u /o c:\dump.dmp ; g" clr
  g

  3.  Open a command prompt
  4.  Change to the directory where you installed Debugging Tools for Windows
  5.  Type in the following command: 

  windbg -G -c "$<dump.scr" <full_path_to_devenv.exe (in quotes if necessary -- omit the angle brackets>

  This will run Visual Studio under WinDbg, which is a low-level debugger that can be easily programmed to gather minidumps.  The dump.scr file which you have written in Step 2 instructs WinDbg to gather a minidump on all access violations, and place the minidump at c:\dump.dmp.  Basically, the idea is this:  the error you are seeing resulted from a Common Language Runtime exception.  What we want to do is catch the exception at the point it is thrown, and have you mail us the minidump (c:\dump.dmp) files (note:  there may be multiple files (e.g., dump1, dump2, etc.); we need all of them).  That way we can take a look at the callstack in the dump files to see what might be happening. 

  6.  When VS starts, run through the scenario that makes the problem happen. 
  7.  At the point that you see the error message box, copy the c:\dump.dmp file somewhere and email it to us.  Please don't attach the minidump to the bug report, as it may contain information about your machine, directory structure, etc. 
  
  
  -Stephen
  VSCore Development

  
  
  

• Sianoosh

  Sorry, there is no reason. Only the description.
  I've uploaded a screenshot: http://img90.imageshack.us/my.php image=vcs20055sn.png (Warning: German ;))
  
  But the reason must be the changed Program-Files-Directory
  
  

• BG77

  Send dumps to stephenr@microsoft.com
  
  -Stephen
  VSCore Development
  
  

• intech27508

  Hi again, I did some research in our list of known issues and it looks like we have seen this issue one time before. That issue was caused by a setup error and was resolved by reinstalling the CLR. Could you please try doing that and see if the problem goes away
  
  You can install the 2.0 framework from here: http://msdn.microsoft.com/netframework/downloads/updates/default.aspx
  
  I apologise for the inconvenience this is causing you. If my suggestion does not resolve the issue, I will forward this onto the CLR team for investigation.
  
  Thanks,
  Prasadi
  
  

• Feffi

  Hi, I tried to reinstall 2.0 framework - not SDK (also repair, uninstall and install, etc.) I didn't resolve the issue.
  
  Same happens to VB projects, but as I wrote before, C++ "Win-Forms" projects works ok.
  
  I also tried to play with Windows registry and change some Visual Studio directories by hand, but it also didn't help.
  
  Thanks,
  Bozydar
  
  

• BPMIlls2001

  My logs are empty and I have proper value ('D:') in ProgramFilesDir (HKLM/Software/Microsoft/Windows/CurrentVersion).
  
  

• John Moore999

  Witi wrote:

  hi, i have the same problem, with this event-log message: "One or more Visual Studio templates is invalid and will not be displayed." But now, i discovered the problem: I changed my ProgramFilesDir (HKLM/Software/Microsoft/Windows/CurrentVersion) to d: If you change your ProgramFilesDir back to c:\Program Files it should work (it worked an my machine ;) But indeed, imo it's a bug... Witi

  
  
  I changed ProgramFilesDir (HKLM/Software/Microsoft/Windows/CurrentVersion) to
  c:\Program Files.
  now it works.
  that's great!
  thank you very much!
  
  
  
• "Absolute path information is required" bug.