Hey balaji,
>i tried the installation in windows xp service pack 2(installed the file server,dataserver and the client with node locked license file).
Well, if you have Intralink 3.3 datecode M022 you SHOULD have no problem with the client. I personally cannot verify this statement as I only have experience with Intralink 3.3 on Windows 2000 Server. However, according to the link I provided (the Intralink 3.3 platform support PDF), this means that the Intralink 3.3 M022 CLIENT was developed and tested on this platform enough for PTC to support it. My experience with PTC software though shows me that even if it is listed as "supported" on a platform support list, regardless of it being ProE, ProM, Intralink...., you still may have unexplainable problems or it may work flawlessly (as possible). It is worthy to note, that neither the fileserver and dataserver are supported in Windows XP SP2, and you have seemed to got those two working.
>i want to know whether it will work in windows 2000 professional sp-4.
Well, again, I cannot say for sure that (I assume) downgrading your operating system to Windows 2000 SP4 will make your problem with the license go away. I would say if you are using Intralink 3.3 M022 it makes no difference (in terms of success rate) since both operating systems SHOULD support the client equally (per the platform support link provided above). If you are using an older build of Intralink 3.3 (not M022), then your build was not tested with Windows XP SP2, so if a problem did exist, PTC would not have known about it and won't provide a fix for it (or in most cases not even a bug report). Therefore, if you are using an older build, I WOULD recommend Windows 2000 Professional SP4. But there are no absolute guarantees with this. It is also worthy to note that when Intralink 3.3 was installed on our Windows 2000 Server platform, I still was able to use the client on the server even though it is listed as "unsupported".
Also, try to make sure that there are no spaces in the file path to your license file. (i.e. C:\licenses\ILINK\license.dat). PTC software SOMETIMES has a hard time with spaces in path names and may cuase errors. I still cannot believe this is not due to the "time-out" issue assocaited with Intralink 3.3.
Hope this helps.
Edited by: acook