May 30, 2005 at 2:01 am
Running SQL Server Reporting Services SP2, SQL Server Standard SP3, Windows
2003 Standard (No SP)
When I try to bring up report manager (http://myserver/reports ) I get the
following error,
"File or assembly name xxxxxxxx.dll, or one of its dependencies, was not
found."
The xxxxxxxx.dll seems to be a randomly generated string of characters as it
changes whenever I refresh the page.
I've checked the permissioning. No errors are evident in the logs. Currently
scheduled subscriptions run without problems.
--------------------
Colt 45 - the original point and click interface
May 30, 2005 at 9:05 pm
This won't help much, but we used to get similar errors when developing .net web apps. For us, the randomly generated dll was the dll created on the JIT compile by .Net. We had this type of issue when the read perms on the .net directory within the windows dir were not correct.
Steve.
May 30, 2005 at 9:53 pm
I checked the permissions against another machine that's working and the permissions look fine. The only difference between them is one is Windows Server 2003 (not working) the other is Windows XP (working).
I know it was working last week. Is there anything "special" to check on Windows Server 2003??
--------------------
Colt 45 - the original point and click interface
May 30, 2005 at 10:13 pm
So what happened between last week and this?
Is this one of your prod boxes? ie you didn't load another framework (2 beta?), no other apps loaded?
Steve.
May 30, 2005 at 10:43 pm
This the "soon to be" production box. No changes that I know of where made on the box. The network guys are starting to act a bit cagy though. The words "group policy change" seem to draw sheepish looks.
--------------------
Colt 45 - the original point and click interface
May 30, 2005 at 10:46 pm
Uh-huh..... and that could definitely explain a loss of access over the .net temp dir/s.... It's all fun and games 'til someone looses an eye.
Steve.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply