Windows Server 2008?

Report · Jan 22, 2010

FrameMaker 7

Old System:

Windows Server 2003 NAS (32-bit)

New System:

Windows Server 2008 Standard (64-bit)

Transferred all data from old file server to new server. Since then, users trying to open a project up are complaining about how very slow its become. Almost to the point where its unusable. I watch the Resource Monitor while they pull up a project, but nothing is bottlenecked. CPU/Memory/Disk Reads/Disk Writes, are all minimal. Has anyone encountered this? The only thing I could suggest to the users was to try an evaluation copy of FrameMaker (latest version) and see if anything changes. I'm out of options and would appreciate any suggestions.

Thanks much

Report · Jan 21, 2011

I have the exact same problem. Brand new Windows 2008 R2 server connected to an ISCSI NAS. Frame Docs on the NAS Storage - should be blazing fast. Everything else running on it is. Except Framemaker 8 or 7.2.

Speeds are really fast normally on that server but Frame8 files are super slow to open and use. I have tried another 2008 R2 server and I experience the same issue.

Here are some benchmarks for opening a good size Framemaker Doc.

Local Hard Drive - Opening Time Less than 1 Sec

Underpowered/Overworked Windows 2003 32bit Server - Opening Time less than 3 Secs

HighPowered Windows 2003 32bit Server - Opening Time less than 3 Secs

High Powered Windows 2008 R2 Server - Opening Time greater than 1 Min

Medium Powered Windows 2008 R2 Server - Opening Time greater than 1 Min

Anyone see a trend? It must be an issue with 2008 somewhere. Anyone else ever see this? I will post a fix if I find it.

I have since confirmed that this ONLY happens when the Framemaker client is install on XP. If you are running Framemaker from a Win7 PC you do not see this slow down.