Could not start NowSMS service on windows XP SP3 | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 23, 2009 ⬆ |
◄ ► |
Author | Message | |||
Saxon Hsih New member Username: Mysaxon Post Number: 1 Registered: 09-2009 |
Dears, The O/S of my pc is windows XP with SP3, and I install the trial version, when I startup the NowSMS service, got an error code 1067 from windows, what should I do? Mysaxon | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1195 Registered: 08-2008 |
> I do not recall seeing this error before. It could be a rights > issue with the localsystem account unable to access the program > files directory. As a first suggestion...remove the service (uncheck run as service), then add again. Make sure you are logged in with admin rights before re-adding. -- Des | |||
Michael Vandervloet New member Username: Mrvdv Post Number: 2 Registered: 09-2009 |
I have no problems running this on my Windows XP Sp3 | |||
Saxon Hsih New member Username: Mysaxon Post Number: 2 Registered: 09-2009 |
I uninstall NowSMS and re-install it, I'm sure that I login windows with the role "administrator", but still got same result, what issue that I missed? Thanks for any suggession! | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1260 Registered: 08-2008 |
Hi Saxson, I've never encountered this problem before, so I've been searching the web for 1067 errors related to other products that run as a Windows service. Are you installing NowSMS into its default directory? (program files\NowSMS) If you are not, then this could be a problem. When NowSMS runs as a service, it runs under the "localsystem" account, which may not have rights to mapped drives. Try un-installing, and then when you re-install, rather than installing in program files\nowsms, try installing to just a directory named nowsms in the root of one of your drives. See if that makes a difference. -- Des NowSMS Support | |||
Saxon Hsih New member Username: Mysaxon Post Number: 3 Registered: 09-2009 |
Dear Des, I have fixed my problem, The steps that I did : 1. un-install NowSMS 2. un-install Sun java WTK3.0 (wireless develop tool) 3. re-install NowSMS (c:\NowSMS) It's work! I don't know that if NowSMS install conflict with WTK 3.0 ? but anyway, many thanks for your help! -- Saxon | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1279 Registered: 08-2008 |
Hi Saxon, We don't use any Java, so I'm not sure what the conflict could be. I think it may have been a path issue, but I don't understand. I was able to recreate a 1067 error. But I could only create it by deleting one of our files. NowSMS installs SMSGWNT.EXE as the service process for NowSMS. SMSGWNT.EXE tries to run SMSGWS.EXE from the same directory. If SMSGWS.EXE cannot start, the service process aborts, and this causes the 1067 error. That is why I suggested a simpler directory structure of just c:\NowSMS. I do not know why this would be a problem, as I cannot find any past incidents of the 1067 error. -- Des NowSMS Support | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7861 Registered: 10-2002 |
Follow-up information on this 1067 error ... This 1067 error appears to be a problem with a virus scanner reporting false positives against the MMSC.EXE file. A 1067 error will occur if either the SMSGWS.EXE or MMSC.EXE file is missing. The ESET NOD32 virus scanner is reporting a false positive for infection of the MMSC.EXE file across multiple versions of NowSMS. (The text from the virus scanner says that it is "probably" a virus, but it quarantines or deletes this executable, even though it isn't sure that it is infected.) We have submitted a report to ESET so that they can fix their virus signature database. (BTW, one useful tool for analysing files for which a virus scanner is reporting a potential infection is http://www.virustotal.com.) -bn | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1375 Registered: 08-2008 |
More follow-up. ESET has confirmed that it is a false positive. The next update for the ESET signatures is supposed to resolve this problem. I tested it via www.virustotal.com, and the 2009.10.23 virus signature database for NOD32 is no longer reporting a problem with MMSC.EXE. -- Des NowSMS Support |