You’re offline. This is a read only version of the page.
I just installed SP2 thinking that it would fix a problem introduced when .net framework 3.5 was installed on my workstation. But now on startup, I get a system.io.pathtoolongexception. Any thoughts?
Thanks.
*This post is locked for comments
I have the same question (0)
Hi Seth
This is Darin and I'll be helping you with this incident.
Subject
========
Getting an error when attempting to login to Dynamics SL.
Error:
-------
CallStack: System.IO.PathTooLongException
Environment
===========
Dynamics SL 7.0 SP2, OS?
ASSESSMENT
=============
We have seen this when a user's Application Data or Temp folder contains a folder with a very long absolute path. Can you check your directories and see if you find a path in the C:\Documents and Settings\<user>\Local Settings\Temp\.. that is over 248 characters? You might try downloanding and install Process Monitor to see what files the system is attempting to open and it which directory. This is really a Windows bug at the root of the issue because the system is allowing a directory structure larger that the system allows. But, you might be able to work around the issue by renaming a path to a shorter name.
Plan
============
1) Determine if the system has a long directory path for the tempory or Application Data folders
2) Try renaming to a shorter path.
3) Use Process Monitor (download from www.sysinternal.com, this will redirect to technet site)
Darin Madsen
Environment and Developer Escalation Engineer
Microsoft Dynamics SL
Share
Report
All responses (
Answers (
