SMS USers configuration copy not working

SMS USers configuration copy not working SearchSearch
Author Message
Gilles ziegler
New member
Username: Gziegl

Post Number: 1
Registered: 11-2013
Posted on Tuesday, November 05, 2013 - 08:24 am:   

We want to migrate our NOWSMS infrastructure from Windows 2003 to Windows 2008R2.
I installed NowsSMS 2010.09.02 on the W2k8 server, entered activation key and copied configuration from the W2k3 server.

But the SMSUsers are not retrieved by the application. The SMSUSers Tab stay empty.

How to copy my complete configuration from W2k3 to W2k8?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4721
Registered: 08-2008
Posted on Tuesday, November 05, 2013 - 03:07 pm:   

Hi,

The configuration files that you copied, specifically SMSGW.INI ... what directory were the files in on the W2k3 Server, and what directory are the files in on the W2k8 server?

On W2k3 Server, NowSMS 2010 will store configuration files in the same directory as the program files.

Security enhancements in W2k8 caused many problems for programs that stored configuration files in the same directory as program files. So when running on W2k8 or later (or Vista or later), NowSMS 2010 will store configuration files under the ProgramData\NowSMS directory (the ProgramData directory is usually hidden in Windows explorer, so use the view option to display hidden files).

So I am assuming you copied SMSGW.INI and other configuration files from the program directory on the W2k3 server to ProgramData\NowSMS on the W2k8 server, correct?

(To confuse the issue of directory locations further, NowSMS 2013 no longer defaults to using ProgramData\NowSMS. For upgrading installations, it looks for SMSGW.INI in ProgramData\NowSMS. If it finds it present, all config files are stored relative to that directory. If not present, the program directory is used.)

The "SMS Users" accounts are stored completely in the SMSUsers.D2A and SMSUsers.D2I files. These are expected to be found in the same directory as SMSGW.INI.

If you've copied these files over to the correct location and you don't see the users, then you are probably encountering a file/directory security issue.

Try launching the NowSMS config program with administrator rights...right click and choose "Run as Administrator". If you now see the users, it is likely a file/directory security issue. The server should be working fine (because it runs with administrator access), but the config program is being blocked from seeing the user files for security reasons.

When this happens, Windows fools the config program and creates separate versions of some files that are only seen by the current running user account and not by the NowSMS service.

Open a command prompt window (preferably with right-click "Run as Administrator"), change to the root directory and scan for duplicate versions of these user files:

cd\
dir smsusers.d2? /s

The above should show two copies of smsusers.d2i and smsusers.d2a ... in ProgramData\NowSMS and Users\All Users\NowSMS. That is ok ... as the latter is a system alias for the former. If you see these files in other directories, the other copies should be deleted.

Next use Windows Explorer to view ProgramData\NowSMS ... if you see config files shown with a lock symbol next to their icon, this can cause problems unless the NowSMS config program is always run as admin.

The easiest fix for all this is to upgrade to NowSMS 2013 which fixes common issues with these security attributes when it is installed. (NowSMS 2013 will also let you keep NowSMS config files in whatever directory the program files are installed to ... instead of forcing you into using ProgramData.)

To fix the problem manually, right click on directories or files affected and on the security tab add Everyone or Users with read/write access to the files/directories.

--
Des
NowSMS Support
Gilles ziegler
New member
Username: Gziegl

Post Number: 2
Registered: 11-2013
Posted on Wednesday, November 06, 2013 - 06:11 am:   

HI,

The issue was due to the "application data" folder usage :-)

So i did the following:
- install NOWSMS 2010 in e:\nowsms
- copied configuration from old server to c:\application data\nowsms
- upgraded to NOWSMS 2013.09.26
- moved all files from c:\application data\nowsms to e:\nowsms

Now it's running.

Question: I copied *.ini and *.d2* files from the old server.
Is that enough or is there other files to copy from the old server ?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4725
Registered: 08-2008
Posted on Wednesday, November 06, 2013 - 11:37 am:   

Hi,

I'd include *.DB in a list of essential files, but I believe that applies primarily to "MMSC Users". (Also to tracking of message IDs for delivery reports.)

The last section of the following article has a good overview of the file/directory structure:

http://www.nowsms.com/migrating-to-a-multiple-server-mmsc-wap-gateway-or-nowsms- gateway

The main thing you would be missing would be queued messages.

--
Des
NowSMS Support