Grab our RSS feeds Follow us on Twitter Join our Facebook Group Connect with us on LinkedIn
myITforum.com, Powered by You.
you are not logged in

Articles

Newslinks

Links

Downloads

Site Services

Community Forums

Discussion Lists

Article Search

Newsletter

Web Blogs

FAQs

Live Support

myITforum TV

Take a Poll

Monthly Drawing

myITforum Network

User Group Directory

Our Partners

About Us

Register

Login

BRONZE PARTNER:

BRONZE PARTNER:



Industry News:




  Home : Articles : SMS 2.x print | email | | Forums |   print | email | | Blogs |   print | email | | Wiki |   print | email | | FAQs |   print | email | Article Search  
SMS FAQ: Problem using LOCALSVR from the Resource Kit


Bookmark and Share

By: Cliff Hobbs
Posted On: 10/21/2001

Problem:
I'm experiencing a problem running LOCALSVR.EXE from the Resource Kit in that whenever I run it on the SMS Site Server (happens on two different site systems) as:

F:\SMSUtils\PrefServ Script>LOCALSVR WHQ NALPATH.INI

I get:

LOCALSVR.EXE will produce data for site code "WHQ".
LOCALSVR.EXE will store the data in file "nalpath.ini".
LOCALSVR.EXE failed to connect to database "SMS" on SQL server "CVSSMS020".
Please verify that the SQL server is accessible on the network and functioning properly.
LOCALSVR.EXE created status mif LOCALSVR.MIF.
LOCALSVR.EXE is exiting with error code 1, indicating failure.
FYI, "CVSSMS020" is a resource server dedicated to SMS/SQL Primary site server role running Win2000 and SQL Server2000. SQL uses the default database name SMS. The server's folder F:\SMSUtils\PrefServ Script holds all the files from the Prefserv folder in the ResKit installation.

FYI: Local Server queries the SMS site database for the NAL paths of all SMS site systems. These paths can then be used with SetSMSSvr.exe to specify DP groups and CAPs for a client to use, rather than having SMS assign them randomly.

Contributed by Ed Aldrich:
To overcome my original problem (above) I manually created the data file that the tool is intended to generate.

Very tedious but effective. It essentially creates a separate line for each subnet that specifies the NAL path to that subnet's preferred CAP, then a separate line for the preferred DP if needed, all CAPs listed first followed by all DPs.

It takes the form of:

[SMS Site Systems]
NumberOfSystems=4
System1Role=SMS Client Access Point
System1IPAddress=10.156.0.0
System1IPSubnetMask=255.252.0.0
System1NALPath=MSWNET:["SMS_SITE=WHQ","PREFERRED"]\\<server>\CAP_<site_code>
System2Role=SMS Client Access Point
System2IPAddress=10.164.0.0
System2IPSubnetMask=255.252.0.0
System2NALPath=MSWNET:["SMS_SITE=WHQ","PREFERRED"]\\<server>\<site_code>
System3Role=SMS Distribution PointSystem3IPAddress=10.156.0.0
System3IPSubnetMask=255.252.0.0
System3NALPath=MSWNET:["SMS_SITE=WHQ"]\\<server>\SMSPKGD$
System4Role=SMS Distribution PointSystem4IPAddress=10.164.0.0
System4IPSubnetMask=255.252.0.0
System4NALPath=MSWNET:["SMS_SITE=WHQ"]\\<server>\SMSPKGD$

In this example I've specified a preferred CAP (System1 and System2) and DP (System3 and System4) for the subnets 10.156.0.0 and 10.164.0.0, for a total of 4 systems (the value passed to the 2nd line, NumberOfSystems=4).

Note that the syntax of these differs slightly from the documentation that describes the tool and this process.

  myITforum.com ©2010 | Legal | Privacy