Announcement

Collapse
No announcement yet.

Odd profile issue

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Odd profile issue

    I have a customer with two MS TS's.

    The first is a Windows 2000 Server - SERVER1
    The second is a new Windows 2003 Server - SERVER2

    They have TS Roaming Profiles.
    The use Sage Line 100 (Windows GUI frontend)

    If I create a new user and that user then logs into SERVER2 they get errors stating that certain files don't exist (and the file really doesn't from what I can see) and cannot access parts of the Sage accounting system.
    Instead of connecting to the new server if a new user connects to the old server and uses Sage they get no issues. This user can also then login to SERVER1 and work OK. This problem only exists if the user profile was created on SERVER2.

    I have seen something simular to this before where Word wouldn't read from the C: drive saying the file doesn't exist yet when you browse to it, it really does exist. The fix for this was to add 'file://servername' under trusted sites in IE.
    I have tried this for this issue but it creates more issues

    Ideas?
    Last edited by ]SK[; 29th July 2008, 16:57.
    Please remember to leave positive reputation points (The Ying Yang Icon) if someone helps you.

  • #2
    Re: Odd profile issue

    The TS Profile for Win2k and Win 2003 isnt 100% the same....
    Best Regards,

    Yuval Sinay

    LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

    Comment


    • #3
      Re: Odd profile issue

      I would have thought that it's obvious profiles change between versions. Im not sure how that is supposed to help?
      Please remember to leave positive reputation points (The Ying Yang Icon) if someone helps you.

      Comment


      • #4
        Re: Odd profile issue

        Try to create a new user with a new profile.
        Logon firest to the Win 2000 and log off. Then logon into the Win 2003.
        Best Regards,

        Yuval Sinay

        LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

        Comment


        • #5
          Re: Odd profile issue

          Originally posted by yuval14 View Post
          Try to create a new user with a new profile.
          Logon firest to the Win 2000 and log off. Then logon into the Win 2003.
          Originally posted by ]SK[ View Post
          Instead of connecting to the new server if a new user connects to the old server and uses Sage they get no issues. This user can also then login to SERVER1 and work OK. This problem only exists if the user profile was created on SERVER2.
          I mean to say SERVER2 not SERVER1. This is what you are asking me to do, I can tell you that yes that works. Which is why I think its permission related.
          Please remember to leave positive reputation points (The Ying Yang Icon) if someone helps you.

          Comment


          • #6
            Re: Odd profile issue

            Originally posted by ]SK[ View Post
            Which is why I think its permission related.
            Not quite.
            It might mean that Windows Server 2003 can cope with a profile created in Windows 2000 Server, But not the other way around ...
            What yuval meant (apologies, Yuval for dubbing you) is that whenever you create a new user, be sure to logon to the Windows 2000 Server first (so the profile is created on it).
            I think it's obvious that this is far from being a favorable set-up, you should consider upgrading the old server.

            Sorin Solomon


            In order to succeed, your desire for success should be greater than your fear of failure.
            -

            Comment


            • #7
              Re: Odd profile issue

              Let me update you as I think you think that the working server is the Windows 2003 server:

              The problem occurs if..

              The user logs onto the Windows 2003 Server first.

              The problem doesn't exist if...

              The user logs onto the Windows 2000 Server first.

              As long as the initial profile was created on the Windows 2000 Server then this issue is not an issue. If however the new user first logs onto the Windows 2003 server then this issue is a problem.

              Should both servers be Windows 2003 then this problem wouldn't have a work around. The reason I cannot update both servers is because of this problem!
              Please remember to leave positive reputation points (The Ying Yang Icon) if someone helps you.

              Comment


              • #8
                Re: Odd profile issue

                Originally posted by ]SK[ View Post
                Let me update you as I think you think that the working server is the Windows 2003 server
                Please tell me what from my previous post got you to this conclusion.
                Anyway, we switched the focus from solving the problem (Sage Line not working on 2003) to solving the workaround's problem (profile created on 2003). So, let's go back to the original.
                Is by any chance Internet Explorer Enhanced Security Configuration enabled on the 2003 server? If not (or if disabling it will not solve the original problem ), I suggest you use Process Monitor, a free tool from Mark Russinovich. By monitoring access attempts to files (disable monitoring Registry and DLLs, otherwise you won't be able to find the needle in the hay stack...) you should be able to see where the failure occurs.
                Good luck and keep the forum posted.

                Sorin Solomon


                In order to succeed, your desire for success should be greater than your fear of failure.
                -

                Comment


                • #9
                  Re: Odd profile issue

                  Originally posted by sorinso View Post
                  Not quite.
                  It might mean that Windows Server 2003 can cope with a profile created in Windows 2000 Server, But not the other way around ...
                  That confuses me. To me your suggesting that the Windows 2003 Server profile is fine.

                  Internet Explorer Enhanced Security Configuration has been uninstalled.

                  I always forget about the sysinternals programs, I will give this a try and let you know if I find anything.
                  Please remember to leave positive reputation points (The Ying Yang Icon) if someone helps you.

                  Comment


                  • #10
                    Re: Odd profile issue

                    Cool, I'm keeping my fingers crossed for you.

                    Sorin Solomon


                    In order to succeed, your desire for success should be greater than your fear of failure.
                    -

                    Comment


                    • #11
                      Re: Odd profile issue

                      Right, found the problem after using process explorer...

                      The program copies a template called SVN4WIN.INI into the users profile folder. This template file had been edited to reflect the correct locations of files that Sage uses on the old Windows 2000 Server. Since the Windows 2003 Server hasn't had these edits made to it it was pointing to folders where these files don't exist.

                      To solve the problem I copied the template from the old server to the new server.

                      I find it impressive that their "Sage Support Specialists" failed to recognise this problem. Thanks for the process explorer tip, it pointed me to the INI file which led me to compair a non-working profile with a working profile.
                      Please remember to leave positive reputation points (The Ying Yang Icon) if someone helps you.

                      Comment


                      • #12
                        Re: Odd profile issue

                        Cooooooooooooooool!! Time for a
                        Thank you for calling Petri.co.il support line
                        Thank you for updating the forum with the solution!

                        Sorin Solomon


                        In order to succeed, your desire for success should be greater than your fear of failure.
                        -

                        Comment

                        Working...
                        X