|
Installation
|
| Q. |
If I have multiple instances of MSDE, how do I determine the Instance Name for SMOP Installation?
|
| A. |
Please see instructions for determining MSDE Instance Name
|
| Q. |
If I have multiple instances of SQL Server 2005 Express Edition, how do I determine the Instance Name for SMOP Installation?
|
| A. |
Please see instructions for determining SQL Server 2005 Express Edition Instance Name
|
| Q. |
During Setup, you get a 'Error 27502.' Could not connect to Microsoft SQL Server 'localhost\......Specified SQL server not found?
|
| A. |
The SQL Server Instance Name may be wrong. Make sure you are using the correct named Instance. See the following links to determine Instance Name.
Determine MSDE Instance Name
Determine SQL Server 2005 Express Edition Instance Name
|
| Q. |
During Setup, you get a 'Error 27552. Error creating database SMOP....'?
|
| A. |
This probably means that you already have an existing SMOP database file. Please remove the physical files named SMOP.mdf and SMOP_log.ldf and re-run SMOP setup.
|
| |
|
System Requirements
|
| Q. |
Does SMOP require any Active Directory schema changes?
|
| A. |
No. SMOP does not change the Active Directory schema or make any Active Directory schema extensions.
|
| Q. |
Does SMOP support Windows Server 2008?
|
| A. |
SMOP offers full support for Windows 2008 Server environments. SMOP supports all of the following scenarios that involve Windows 2008 Server:
- Windows 2008 IIS Server running SMOP with Windows 2003/2000 Active Directory domain
- Windows 2003 IIS Server running SMOP with Windows 2008 Active Directory domain
- Windows 2008 IIS Server running SMOP with Windows 2008 Active Directory domain
|
| |
|
Running SMOP and SMOP Administration
|
| Q. |
Can you specify a Fully Qualified Domain Name (FQDN) in the Domain Section?
|
| A. |
Yes. Either a NETBIOS type domain name can be used or a Fully Qualified Domain Name can be used. You need to ensure that your DNS servers can resolve the FQDN.
|
| Q. |
I have the option for 'User must change password at next logon' turned on, but some users do not get this set. Why?
|
| A. |
One common cause of this error is incorrect DNS configuration on the SMOP Server. Please ensure that the SMOP server can reach an Active Directory domain controller and can resolve DNS queries for domain and other service DNS queries.
|
| Q. |
When logging in you get 'Login failed. Please try again.'?
|
| A. |
If the 'Password never expires' checkbox is checked for a user, the checkbox for 'User must change password at next logon' will not be activated because the two settings conflict with each other. This will affect only those users who have the 'Password never expires' checkbox checked. This is normal Active Directory behavior.
|
| Q. |
After entering licensing key information, the license shows my company's name, but after a while (after IIS is restarted), the licensing reverts back to 10 users or back to evaluation mode.
|
| A. |
This problem is specific to Windows 2008. If you encounter this problem, please do the following:
- On the Server where SMOP is installed, launch IIS Manager.
- Select the SMOP Virtual Directory, and click on Basic Settings under Actions in the right hand pane.
- In the Edict Application window, in the Application pool area, click Select.
- Select "Classic .NET AppPool"
- Click OK to close dialog box
- Click OK to exit Edit Application
- Restart IIS Services
Your licensing information should now show up properly.
|
Goto FAQ Main Page |
