The application is SAS. Specifically, the spawner feature of
SAS/Connect. This is basically a telnet server to which the user can submit
SAS programs for processing and retrieve the results on their workstation.
The server a more powerful platform and the large datasets reside on the
server. Processing the data on the server in this way increases the speed
of the apps over 10 times.
The problem arises when trying to secure the account under which the
spawner service runs. It runs correctly with no security, which means the
user isn't prompted for a userid/password to access files. However, that
means that anybody that can access the server can start processing and,
since the service runs as SYSTEM, it totally bypasses the NTFS security
applied to the data.
SAS TS was as surprised as we were that this doesn't work. The
issue is specific to the situation of Win2K Pro users submitting jobs to a
Win2K Server using SAS/Connect with the spawner running with pass through to
Windows security. Apparently, from their talks with M$, the fix is not
trivial. If you've ever worked with SAS you should know that their tech
support, if not expedient, is very thourough and knowledgeble.
We have a M$ site license on this campus, so the cost of the
software for the upgrade is trivial. The problem is that I'm doing this to
help another department and I don't have 2 days to spend backing up,
rebuilding, reinstalling software, and resecuring the system.
>
> What is the application?
>
> Somebody is deflecting a tech support call hoping you will go away.
>
> Did they tell you specifically why it wouldn't work on Win2K
> server? Was
> it the max # of processors or the max memory limitation?
> Either way you
> need to add hardware to your server, right?
>
> I think you'll be building from scratch to get to Win2k Adv Server. I
> don't know of any upgrade path.
>
> I'd duke it out with their tech support first. Let them know your
> billing rate and your downtime rate that you will charge them if the
> problem doesn't immediately go away. Make sure you get names of who to
> send the bill to. Get them to put in writing why you need Adv Server
> instead of Server.
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> [EMAIL PROTECTED]
> Sent: Monday, August 20, 2001 2:58 PM
> To: NT 2000 Discussions
> Subject: Upgrade to 2000 Advanced Server
>
>
> We have an application that does not run correctly on Windows
> 2000
> Server. After talking to the application's tech support they have
> determined that, while it works correctly using Windows NT Server, it
> does
> not run correctly on either Windows 2000 Server or Windows 2000 Data
> Center.
> It does run correctly on Windows 2000 Advanced Server.
> I want to upgrade the existing server from 2KServer to
> 2KAdvanced
> Server. Poking through Technet and the Win2K web site this does not
> appear
> to be a supported upgrade path.
> I don't want to have to rebuild the server if I don't have to.
> Has
> anyone tried to upgrade from 2KS to 2KAS? Any ideas why this wouldn't
> work?
> todddddddddddd
>
> _VT_VT_VT_VT_VT_VT_VT_VT_VT_VT_VT_VT_VT_VT_VT_VT_VT_
>
> Todd Pukanecz
> Virginia Tech, AHNR IT
> Blacksburg, Virginia
> ---
> "It is not the function of our Government to keep the citizen from
> falling into error; it is the function of the citizen to keep the
> Government from falling into error."
> - U.S. Supreme Court in American Communications Association v. Douds,
> 339 U.S. 382,442
------
You are subscribed as [email protected]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to [EMAIL PROTECTED]
