File Server Resource Manager problems

[Fatboy0341]

Just installed the R2 toolkit on one of my file servers so I can play around with it and see if it will do what we need.

I downloaded the 4 separate components from Microsoft and when trying to install them, I received an error that the version I was installing did not match the version of Windows I was running.

I doing some research online, I found some similar issues that were rectified by running ADPREP to update the domain schema...however - when I ran ADPREP/forestprep etc, those commands had already been run and the schema had already been updated (I knew this already but was following the steps to see if it made any difference in case I missed something).

In doing some more research I found a few articles on installing the entire toolkit from CD...which I did. I installed the toolkit and then had the "Windows 2003 Admin Tookpack Help" option under "Administrative Tools". I then went into Control Panel, Add Remove Components, Windows Components - and under Management Tools - selected the "File Server Resource Manager" and "File Server Manager" tools...and installed both of them. I rebooted the serve last night (this is a production server and I can't reboot it during the day without notice).

So...I come in today and get settled in and open the File Server Resource Manager and I get an error that it can't connect to the FSRM Service on the local computer. I open Services and find the service and see that it's not started so I set it to Automatic and try to start it - and get an error that Windows "Could Not Start The File Server Resource Manager Service On The Local Computer - Error: 0xc1.

I've tried setting it to run using local and domain accounts, manually and automatically and get the same error each time. There's not much online regarding this - anyone using this tool and have you experienced this issue? Any advice? Did my install sound like it was done correctly?

Thanks in advance for any suggestions or advice.


"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[Fatboy0341]

Not much to update here...still can't get this service to run.

I changed the path for this service to reflect that actual path (as opposed to the relative variable path originally set) and now I get a slightly different error to the effect that the service did not respond in a timely fashion. I am also now getting a hit in the System Log with the following:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 7/18/2007
Time: 1:30:20 PM
User: N/A
Computer: MBIFILSRV1
Description:
The File Server Resource Manager service terminated with the following error:
File Server Resource Manager is not a valid Win32 application.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Not a valid Win32 application? That's a good one. Microsoft's link doesn't add much...just the sc query command that provides the following output:


C:\Documents and Settings\excsrvadmin>sc query srmsvc

SERVICE_NAME: srmsvc
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN))

WIN32_EXIT_CODE : 193 (0xc1)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0


I have uninstalled and reinstalled 6 times so far, from 3 different sets of media - all with teh same results.

Anyone have any suggestions...other than to fling myself under a bus?


"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[lpspat]

I have the same problem. I had a 32bit R2 server running quotas with File Reource Manager on an external DAS unit. I reinstalled the O/S to get 64 bit R2 and installed File Resource Manager again. When I try to start it I get the same Error: 0xc1.

I thought it could be corrupt old file info on the drive so I deleted the old files per the Q555941 article (which worked fine). However, I still can't get the FSRM program to run. NOTE: I have also uninstalled and reinstalled FSRM several times.

This is a large productions system housing home folder and I REALLY need a fix. ANYONE??

 

[Fatboy0341]

lpspat - Do you have a link to the Q555941 article? Searching on Microsoft's site doesn't find that article number for some reason.

I have a consultant working on the problem (it's part of a supplemental support contract we have in place) so hopefully she'll hit on something. If she does - I'll be sure to post it.

Glad to know I'm not the only one...this is frustrating.


"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[lpspat]

I have the answer! (Thanks to Eugene on the Techrepublic forum for pointing me in the right direction). There are 2 versions of the dfsext.dll that runs FSRM. The 32bit version is 42KB and the 64bit version is 62KB, both have the same file date of 11/23/05.

Somehow (I think I had the wrong version of the R2 disk #2), I got the 32 bit version of dfsext.dll installed on a 64 bit system. Uninstalling and reinstalling FSRM without deleting the bad file doesn't correct it. I manually removed the dfsext.dll file from C:\windows\system32, rebooted, reinstalled FSRM, rebooted, and all is OK now.

 

[Fatboy0341]

Well - I went in and looked at my system32 directory and sure enough, I had the 62KB version of the dfsext.dll file.

Now - I went ahead (Making sure to use the Server 2003 R2 Standard Edition Disc 2) and reinstalled FSRM.

First thing I notice is that there is no new dfsext.dll file in the system32 directory. Second - when I search the disc for that file, it only comes back finding the file "dfsext.DL_" and it's 22KB (Thinking maybe it's unpacked or compressed probably).

The only thing I can come up with is that I won't see the new 42KB file until I reboot?


"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[Fatboy0341]

OK - I got the .ini swapped out and the services no start with no errors now.

However:

When I open the File Server Resource Manager, I still get the error that it can't connect to the local server and that the service is either not started or encountered a problem.


"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[lpspat]

Make sure that the dfsext.dll file is gone (manually delete it), reboot, then reinstall the whole R2 disk (Select the 1st item on the second O/S install disk and choose to reinstall R2), then go to the Add additional components choice on the R2 disk and select FSRM and install it again. Reboot and you should have all the correct files.