Are there any known issues with using a UDF .dll for dimension
security on Windows 2003 Server?

I was using a UDF contained in a VB .dll to implement dimension
security on a windows 2000 advanced server (AS 2000 SP3 + the UDF
hotfix, SQL 2K SP3) and everything worked perfectly.

We changed ONLY the OS to windows server 2003 and now the .dll has to
be manually re-registered in each cube periodically.

The .dll is registered via the cube editor's Calculated Member Builder
so it should work just like it did on Windows 2000 Advanced Server but
when I test it using the "Test Role" button in the Role Manager I get
a
"Error in the definition of the dimension security for the dimension X
and role X. Cannot evaluate the expression X." message.

When I script the cubes using the MetaDataScripter tool from the SQL
Resource Kit all of the code that references the library is written to
the script even though I get the error that above.

If I open the Calculated Member Builder, remove the reference, save
the cube, open the Calculated Member Builder, add the reference, save
the cube and test the role in the Role manager everything works fine
again.

If I rescript the cube that is now working the script looks identical
to the script created when the error was occurring...

How does changing the OS affect the registered library in AS???

Thanks,
Stewart