Tuesday, December 22, 2009

How do I manually include the users or groups for access to the Search and Discovery web page of Instant Archive Viewer for OCS?

It is possible to manually enter users and groups for access to use the Discovery section of Instant Archive Viewer for OCS which serves as an alternative to using the Directory picker shown below in ...itimarchiview/admin/index.aspx

Here is a the Directory picker to choose the Users or Groups in the Active Directory. We will be manually configuring this instead.

To manually configure these users for access to Discovery section...

1. First navigate to ...:\Inetpub\wwwroot\ITIMArchiveViews\Admin folder.2. Open DiscoveryConfig.xml in notepad:

The format for entering the user or group names is:

Domain Name\Display Name



Example:







Note: Be sure the "Domain Name\Display Name" is within "" start tag /GroupOrUser> end tag

Follow the instructions above to manually configure The extended search section for complete Archive Access as an Alternative to the AD Directory picker:



The location of the extended search configuration file is:
C:\Inetpub\wwwroot\ITIMArchiveViews\Admin\ExtendedConfig.xml

Here is an example:



For The Managers and Access groups section shown below:

Use Admanager.config located in the same directory: wwwroot.itimarchiveviews/admin/admanager.config. Open and edit in notepad.


Here are the tags, their format and uses:

1. AdGroups = Contains the GroupName,Managers, ManageUri, Members Uri and Members Tags

2. GroupName= The Group to Manage
Format: Domain name\Display name

3. ManageUri= the URI of the Manager
Format: 'user@domainname.com'

4. MembersUri = the member's Uri that will be managed
Format: 'user@domainname.com'

5. Members = the Display Name of the members of the group to be managed
Format: 'Display name'

How to enable SQL Server 2005 Express to allow remote connections for Instant Archive Viewer for OCS configuration

By default, SQL Server 2005 doesn’t allow remote connection so you have to enable it manually. If you try to connect to remote SQL Server without enable remote connection first, you’ll see one of these error messages.
“An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connection. ….
SQL Server does not allow remote connection
“Login failed for user ‘sa’. The user is not associated with a trusted SQL Server connection.
Login failed for 'sa'
To resolve these problems, you have 2 majors task. One is to enable both SQL Server and Windows authentication mode on SQL Server and the other is to allow remote connection and SQL Server Browser.
  • Check that you have allowed both SQL Server and Windows Authentication mode (If you’re not use Windows Authentication mode). For instance, user ‘sa’.
    1. Login to SQL Server using SQL Server Management Studio Express on local SQL Server with Windows Authentication user. This will use Windows account to authenticate to SQL Server.
      Login using Windows authentication mode on local
    2. In Object Explorer, right click on the instance name and select Properties.
      Open SQL Server Properties
    3. On the left, select Security and change Server authentication to SQL Server and Windows Authentication mode. If the choice is already selected, that means you have already allowed SQL Server authentication.
      Change SQL Server authentication mode
    4. There’ll be an information window shows that you need to restart SQL Server to takes effect of the changes.
      SQL Server need restart
    5. Right-click on the instance name again, select Restart to restart SQL Server service.
      Restart SQL Server Service
    6. Select Yes.
      Confirmation
    7. Wait for service stop and start.
      Restarting SQL Server Service
    8. That’s it. You have enabled both SQL Server and Windows authentication so now you can login to SQL Server with your current Windows account or your created account.
  • Check that you have enabled remote connection on SQL Server Surface Area Configuration
    1. Open SQL Server Surface Area Configuration.
      Open SQL Server Surface Area Configuration
    2. Select Surface Area Configuration for Services and Connections.
      Open Surface Area Configuration for Services and Connections
    3. On the left side, expand your SQL Server instance -> Database Engine -> Remote Connections. On the right side, select Local and remote connections -> using both TCP/IP and named pipes.
      Allow remote connections
    4. On the left side, select SQL Server Browser -> Service.
      On the right side, if the startup type is Disable, you need to change to Automatic and click Apply and click Start button to start the service. Then, click OK.
      Start SQL Server Browser
    5. You have finished configure. Now try to login to your SQL Server from remote computer using SQL Server authentication mode.
      Login to remote SQL Server
    6. Login to SQL Server succeeded.
      Login succeeded
    7. Now try testing the Connection in Instant Archive Viewer for OCS database settings tab on the Admin Page: ...itimarchiveviews/admin/index.asp:

      • Status: Test Connection Succeeded
References:
http://www.linglom.com/2007/08/31/enable-remote-connection-to-sql-server-2005-express/

Configuring OCS Archive Viewer with SQL 2008 Express


Trying to connect to SQL Server 2008 Express remotely without enabling remote connection first, may result in the following warning messages:

“Cannot connect to SQL-Server-Instance-Name
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 28 – Server doesn’t support requested protocol) (Microsoft SQL Server)”
“Cannot connect to SQL-Server-Instance-Name
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQLServer does not allow remote connections.(provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified) (Microsoft SQLServer)”
“Cannot connect to SQL-Server-Instance-Name
Login failed for user
username‘. (Microsoft SQL Server, Error: 18456)”

To enable remote connection on SQL Server 2008 Express, follow steps below:

1. Open SQL Server Configuration Manager. Click Start -> Programs -> Microsoft SQL Server 2008 -> Configuration Tools -> SQL Server Configuration Manager.

2. On SQL Server Configuration Manager, select SQL Server Services on the left window. If the state on SQL Server Browser is not running, you have to configure and start the service. Otherwise, you can skip to step 6.

3. Double-click on SQL Server Browser, the Properties window will show up. Set the account for start SQL Server Browser Service. In this example, I set to Local Service account.

4. On SQL Server Browser Properties, move to Service tab and change Start Mode to Automatic. Therefore, the service will be start automatically when the computer starts. Click OK to apply changes.

5. Back to SQL Server Configuration Manager, right-click on SQL Server Bowser on the right window and select Start to start the service.

6. On the left window, expand SQL Server Network Configuration -> Protocols for SQLEXPRESS. TCP/IP protocol status is disabled.

7. Right-click on TCP/IP and select Enable to enable the protocol.

8. There will be a pop-up message stating that you have to restart the SQL Service to apply changes.

9. On the left window, select SQL Server Services. Select SQL Server (SQLEXPRESS) on the right window -> click Restart.

The SQL Server service will be restarted.

10. Now OCSAV can remotely connect to the SQL Server Express 2008.

11.Test the connection in Database Settings tab on the... itimarchiveviews/Admin/index.aspx Page

and Save.

Thursday, December 3, 2009

Create a rename request in AdminP database and pull the same to BLA

Open Lotus Administrator, open the desired server by using 'File --> Open Server'

Browse to 'People', select the user you want to rename and then click rename on the right navigator.

In the next dialog, click on 'Change Common Name' and provide the servers's certifier ID.

Click 'OK' to the next dialog to confirm the expiration date.

Provide the new details of the user and click 'OK' to create a rename request in the AdminP database.

Provide the command 'Tell Adminp Process All' in the domino server console to immediately process the rename request you had created.
Once the rename request has been executed, a log document will be created under the rename request which will then be imported to the BLA using the action 'Import Requests from AdminP' in the BLA database.

Thursday, November 12, 2009

What are the requirements for installing Instant Archive Viewer?

Instant Archive Viewer Checklist

Domain Controller

Requirements

Yes

No

1

DNS is Configured.

Yes

2

Domain is Accessible on all Domain Users’ Machines.

Yes

3

Active Directory Properly Configured.

Yes

4

IIS Web Server trusted for delegation on Domain Controller.

Yes

6

OCS server 2007/R2 properly Installed .

Yes

7

Fully Qualified Domain name Properly Configured.

Yes

8

Check, if chat Archiving is enabled on Office communication server.

Yes

9

Are you using multi domains? If so, GC will be set in Instant Archive Viewer.

Yes

IIS Web Server –The Instant Archive Viewer host.

Requirements

Yes

No

1

IIS Properly Configured

Yes

2

IIS Server trusted for delegation on the Domain Controller

Yes

3

IIS is Negotiate for Kerberos Authentication, if using Windows Pass Through Authentication.

(Type the following in the Command Prompt to check:

c:\> cscript c:\Inetpub\AdminScripts\ adsutil.vbs setw3svc/WebSite/root/NTAuthenticationProviders "Negotiate,NTLM")

Yes

4

Machine User Must be the Member of the domain Controller

Yes

5

The Fully Qualified Domain Name of the Domain Controller is Accessible

Yes

6

Dot Net Framework 2.0

7

If you are configuring SQL DB connection using sql authentication, SQL user should have execution,select, and update permission on LCSLOG database.

Yes

8

If you are configuring SQL DB connection using windows authentication, give the permission execute, select, update on the lcslog database to the logged in user on sql server.

yes

Check list for Users to Authenticate and Access the Instant Archive Viewer Website from their Work Stations

Requirements

Yes

No

1

The Fully Qualified Domain Name of the Domain Controller is Accessible.

Yes

2

Client must be part of the Domain Controller.

Yes

3

For Windows Authentication, Check the Internet options Advanced Tab for Windows Authentication.

Yes

4

Site added on the local Intranet Zone.

Yes

5

For windows authentication, client machine should be trusted for delegation on the Domain Controller.

Yes

Wednesday, October 28, 2009

"Chat Services are not Available" and "Instant IMtegrity FATAL ERROR: Log file error(s) while starting session...

"We are seeing IMtegrity FATAL errors and users are getting the following prompt:"Chat Services are not Available" and losing their chat services."

The problem is that the core Imtegrity logger is unable to write the XML files.

Please enable debug tracing in the IMtegrity config tool. This will produce a trace\imtegrity.txt file which should have more detailed errors.


1.) This can be enabled by navigating to: Program files\Imtegrity

2.) Check Enable Imtegrity diagnostic output to domino\trace\imtegrity.txt

3.) stop service and start service.

4.) Let that text record grow a little and then disable it to avoid it getting too large and please send the imtegrity.txt to support@instant-tech.com

The “Chat Services are not available” error is due to the chat logging type being set to STRICT on purpose in Imtegrity, for various reasons.
- Most of our customers are REQUIRED to log chats due to regulations like Sarbanes-Oxley
- The only way to immediately detect any issues with logging is via strict logging. In relaxed capture mode, things proceed as if nothing has happened, so you'll potentially NEVER find out that logs are not accurately captured.

Tuesday, October 27, 2009

How can I change the interval setting for uploading chats?

By default, the server add-in task imports chat logs every 60 seconds.

To see the current import interval, enter the following console command:
> tell imtegrity interval

To change the import interval (for example, to 2 minutes = 120 seconds), enter the following console command:

> tell imtegrity INTERVAL 120

This changes the import interval to 120 seconds.


Note: It is not recommend to set the import interval to less than 5 seconds due to the load/overhead
placed on the system.

Available TELL command line options

The server add-in task supports a variety of TELL commands to configure it at run-time:
> tell imtegrity HELP lists the available command line options
> tell imtegrity VERSION shows the current version and build date
> tell imtegrity INTERVAL shows the current import interval
> tell imtegrity INTERVAL n sets the import interval to "n" seconds
> tell imtegrity PAUSE temporarily pauses the importer
> tell imtegrity RESUME resumes previously paused imports
> tell imtegrity IMPORT performs a one time manual import (useful when in PAUSE
mode)

Monday, October 26, 2009

How do I send trace logs for Instant Archive Viewer?

When experiencing issues, a trace file can be created. It can be done by enabling a trace to a text file, reproducing the issues and then sending this file to us.


Steps are below for Versions 3.041 and newer:
1. Enable trace to a text file in the support tab of the .../Admin/index.aspx page.
2. Check "Generate error log in a text file"
3. Save
4. Reproduce the issue and please send to: Support@instant-tech.com



Steps below are for 3.040 and older:

1. Go to the Support tab in the .../Admin/index.aspx page


2. Click on the .../Admin/Trace.axd link

3. Clear current trace

4. Reproduce the issue

5. Go to the "Support" tab again and click on the .../Admin/Trace.axd link

6. Select "View Details"

7. Take a screen shot of all errors in red under "Trace Information" and please send to:

Support@instant-tech.com

Wednesday, October 21, 2009

What is the best way to configure Instant Archive Viewer for OCS?

Install and Configuration

  1. Download IAV from Instant Download site. a. Extract contents of zip, run “InstantArchiveViewerInstaller.msi" b. Click on each link, accept all defaults but select “no” to use default app pool.
  2. Configuring write permissions Remove Read only attribute from c:\Inetpub\wwwroot then right click on ITIMArchiveViews and give IIS worker group; read and execute, list folder contents, read, write permissions.
  3. IIS Configurations

For IIS 6 and older versions:

  1. Open the IIS, select the virtual directory and right click on it and select the properties
  2. Select the directory security
  3. Click on Edit
  4. Uncheck the anonymous access.

For IIS 7:

  1. Open IIS Manager and navigate to the level you want to manage
  2. In Features View, double-click Authentication.
  3. On the Authentication page, select Windows Authentication.
  4. In the Actions pane, click Enable to use Windows authentication and disable Anonymous.
  5. Configure your App pool for Classic mode


4. Admin Connection Settings Navigate to ITIMArchiveViews/Admin/Index.aspx in Default website right click and browse to view the app.

a. Basic Settings Tab:

  1. Add the IP or FQDN and Connect using one username and password that has access to your AD (refer to older web.config, if this is a reinstall)
  2. Uncheck “Enable anonymous users…
  3. Test connection, if succeeds-scroll down and save. If unsuccessful try the IP verify the username and password, different IP or FQDN.

b. Database Settings Tab:

  1. Add the IP or FQDN and Connect using one username and password that has access to your SQL server using SQL Authentication (refer to older web.config, if this is a reinstall)
  2. Test Connection, if success-scroll down, save. If unsuccessful see http://faq.instant-tech.com/2009/03/i-cant-connect-to-sql-server-using-one.html

c. License Tab

  1. Add license key provide by Instant Rep. (You can use the same license key from version

d. Database Settings Tab

  1. Test chat viewing in browser: http://fqdn/itimarchiveviews/index.aspx. (This will work on a machine in which the logged on user has a sip uri only)

e. Extended Search Tab: For Accessing all archives of all users

  1. Click the browse Icon and select and add the user name or group
  2. Click Commit changes, save and Test chat viewing in browser: http://fqdn/itimarchiveviews/index.aspx. (This will work on a machine in which the logged on user has a sip uri only)

f. Discovery Tab: For running, exporting and Saving Queries

  1. Click the browse Icon and select and add the user name or group
  2. Click Commit changes, save and try the Preview URL link to view the project maintenance Page.
  3. All users/Between Users Tab and Add user to query and search

Friday, October 16, 2009

When we try to open the Chat DB, it takes for ever to build the view.

If you need the database to quickly open, you need to make sure that the views are always indexed and up-to-date.
The server discards any view-indexes if they haven't been opened for a while, or it needs to increment updates to them if they haven't been used for a while.

You could create a server PROGRAM document and schedule this task to run:

UPDALL imtchatlog4.nsf -v

(the -v option updates the view indexes). For details on what options are available, type
> load updall /?
on your server console.

If you schedule a program doc to run this task periodically, the views will always be up-to-date and the db opens immediately.

Tuesday, October 13, 2009

SMTP connection fails with a warning

You may receive the following warning, when testing the SMTP connection in the SMTP Tab of the Admin page:



Try the following to fix the issue:
Access the SMTP Tab from a machine in which the logged on user is enabled for communications and save the setting from this machine.

I only see a blank page with icons and no archive history is showing.

Instant Archive Viewer will not work using anonymous authentication.

Please double check if anonymous is unchecked in Directory Security tab after right clicking the ITIMArchiveviews website. You should only have Windows authentication selected in IIS for ITIMarchiveviews.

Monday, October 12, 2009

How do I upgrade Instant IMtegrity Version 4 point release to a newer version 4 point release?

Un-install Instant IMtegrity 4
  • Step 1: Shutdown the Lotus Sametime Server (but leave the Domino server running!)Make sure that there are no chat log XML files in the IMtegrity logs directory anymore:Check the logs directory for any remaining .XML files. If there are any, wait until Domino has imported them into the imtchatlog.nsf database. By default, imports run every 5 minutes.
  • Step 2: Shutdown the Lotus Domino server
  • Step 3: Un-install "Instant IMtegrity 4" using Add/Remove Programs. (When prompted to reboot the system, it is safe to choose "Later". You only need to reboot the system after you finished the upgrade)
Install Instant IMtegrity 4.x upgrade
  • Step 4: Install "Instant IMtegrity 4 upgraded version"
  1. Unpack the IMtegrity 4 ZIP file which contains the installer
  2. Run SETUP.EXE
  3. Click "Next" at the splash screen
  4. Click "Next" at the welcome page
  5. Read the license agreement and click "Next" if you accept it
  6. Select the target installation folder and click "Next"
  7. Click "Next" to start the installation
  8. Click "Close" to exit the installer
  • Step 5: When prompted to reboot the system, click "Yes"
It is required to reboot the system at this time. IM chats will not be logged until the system
has rebooted.

How do I upgrade from Instant IMtegrity Version 3 to Version 4?

Instant IMtegrity 4 must be installed on the same computer also running the IBM Lotus Sametime server software and you must be logged in to Windows with an Administrator account.

Steps to upgrade from Version 3 to Version 4
Un-install Instant IMtegrity 3
  • Step 1: Shutdown the Lotus Sametime Server (but leave the Domino server running!)Make sure that there are no chat log XML files in the IMtegrity logs directory anymore:Check the logs directory for any remaining .XML filesIf there are any, wait until Domino has imported them into the imtchatlog.nsf database. By default, imports run every 5 minutes.
  • Step 2: Shutdown the Lotus Domino server
  • Step 3: Un-install "IMtegrity OS Components for Windows 2000,XP,2003"(When prompted to reboot the system, it is safe to choose "Later". You only need to reboot the system after you finished the upgrade)
  • Step 4: Un-install "Instant IMtegrity 3" Depending on what version of IMtegrity 3 you have currently installed, you might or might not get prompted to reboot. (When prompted to reboot the system, it is safe to choose "Later". You only need to reboot the system after you finished the upgrade)
Install Instant IMtegrity 4
  • Step 5: Install "Instant IMtegrity 4" (Note: There is no "OS Components" installer anymore in version 4. All required files are now integrated into a single installer in version 4) Unpack the IMtegrity 4 ZIP file which contains the installerRun SETUP.EXE
  1. Click "Next" at the splash screen
  2. Click "Next" at the welcome page
  3. Read the license agreement and click "Next" if you accept it
  4. Select the target installation folder and click "Next"
  5. Click "Next" to start the installation
  6. Click "Close" to exit the installer
  • Step 6: When prompted to reboot the system, click "Yes" It is required to reboot the system at this time. IM chats will not be logged until the system has rebooted.

Thursday, October 8, 2009

How do I upgrade to Instant Queue Manager 2.6?

Steps to perform an upgrade are as follows:

1. Take backup of your existing ADF files
2. Stop Instant Agent Framework service from Services Applet in control panel
3. Uninstall existing Queue Manager
4. Install newer release of Queue Manager
5. Restore ADF files which were backed up in Step 1
6. Open Instant Agent Service Manager add ADF files, verify and save settings

Tuesday, October 6, 2009

How do I set up Instant Measurements?

The Instant Measurements Suite is a plugin application that extends the capabilities of Instant Queue Connections, as well as other Instant products. It is a Lotus Domino application, distributed as a template (.ntf) file.
  1. Perform the install of Instant Queue Connections.
  2. Extract the install image for Measurements, if you haven't already done so.
  3. From within Lotus Notes, with administrator privleges on the same server as your Queue Logging database, create an application (database) from the ITMeasure.ntf file. You can put it anywhere you like on the server, but it is recommended to be in the same subdirectory as the Queue Log database, for simplicity.
  4. If you created the Queue Log database using the default name, in the root of the Notes/Domino data directory, then you're done with the install of Instante Measurements, and can skip to step 9.
  5. If you didn't use the default name (QueueLog.nsf), or if you placed it in a different directory than the default data directory's root, then open the ITMeasure.nsf (or whatever you called it) database from a Notes client. You will be presented with a welcome page, which contains a link to the setup profile document.
  6. Click on the link to open the setup profile document. The document is broken into tabs, with the first for Instant Queue Connections. The other tabs are for future use of the plugin with other Instant Technologies' products (such as Instant IMtegrity or Buddy List Administrator).
  7. Select the field for File Path, and enter the path and file name where you installed the Queue Logs database during the install of Instant Queue Connections, relative to the default data directory.

    For example, if your default data directory is on a Windows-based server, in a folder called "C:\Lotus\Domino\Data\", and you installed the Queue Connections databases in a subfolder called "IQConnect", and you used the default name for the Queue Logs database, then you should type "IQConnect\QueueLog.nsf" in this field.
  8. Select the "Save and Close" action button at the top of the form. This completes the installation steps for ITMeasure.nsf. Continue reading for the steps to link IQConnect with ITMeasure...
  9. From the default Instant Queue Connections application, select "Edit Global Settings" at the top of the user interface. The list of queues will be replaced by a global settings document.
  10. In the "General" section, locate the field labeled "Url to the reporting database". Into this field, enter the URL of the ITMeasurements application you just created.

    For example, if the ITMeasurements application were installed using the default name, and in the IQConnect subfolder, as in the example above, you could enter the relative URL, such as the following:
    /IQConnect/ITMeasure.nsf?OpenDatabase&Source=Queue&Hosted=True
    You can also enter the fully qualified URL, if you have a single server setup hosting the web sites, such as www.instant-tech.com, you could enter the following:
    http://www.instant-tech.com/IQConnect/ITMeasure.nsf?OpenDatabase&Source=Queue&Hosted=True

    Note that the items following the ? are required for the user interface to "plug-in" and merge properly with IQConnect.
  11. Select "Update" in the global settings page to save your changes. Setup is complete.

Monday, October 5, 2009

Experiencing Blank Chat Area – when using Instant Web Client

If you see blank chat area while using web client as specified in the following screenshot then you will need to clear temporary internet files (cache) of your browser.



Internet Explorer - delete Temporary Internet Files:
1. Open Internet Explorer.
2. Select the Tools menu.

3. Select Internet Options.
4. Under Browsing History, click the Delete button.

5. In the Delete Browsing History window, click the Delete Files button.
6. When asked if you are sure you want to delete all temporary Internet files, click Yes.

7. To close the windows, click Close, then Ok.

FireFox (Mozilla) - clear cache (Firefox 3.0)
1. Open FireFox (Mozilla).

2. Click the Tools menu.

3. Click Clear Private Data.

4. Check Cache. Note that any other checked items will also be cleared, so un-check any that you do not want to clear.

5. Click the Clear Private Data Now button.


Firefox, older versions
1. Open FireFox (Mozilla).

2. Click the Tools menu.

3. Click Options.

4. Click Privacy.

5. Click the Clear button for Cache.


Safari - clear cache
Safari (3.1.2)
1. Open Safari.

2. Click the Edit menu.

3. Click Empty Cache....
4. When asked if you are sure you want to empty the cache, click the Empty button.

Thursday, October 1, 2009

Requested registry access is not allowed when saving configuration settings

IIS 6 and older versions:
1. Open the IIS, select the virtual directory and right click on it and select the properties.
2. Select the directory security
3. Click on Edit.
4. Uncheck the anonymous access.

IIS 7:
Open IIS Manager and navigate to the level you want to manage.
1. In Features View, double-click Authentication.
2. On the Authentication page, select Windows Authentication.
3. In the Actions pane, click Enable to use Windows authentication.
Note:
If above fails, also check "Windows Impersonation"

Friday, September 11, 2009

Scheduled Instant alerting will not alert users after installing Instant Alert Manager for Microsoft OCS

You may not have the correct permissions for your local Instant Alert Manager for OCS services account. To work around this, you can add your Instant Alert Manager for OCS Logged in account from Services.
1. Go to run... from the start menu and type services.msc
2. Select the Alert Manager service, right click and select properties.
3. Select the log on tab.
4. Select the radio button “this account”.
5. Enter your log in account for Instant Alert Manager for OCS and type the password.
5. Restart the service.

Thursday, September 10, 2009

SQL Express will not accept remote connections. How do I install Archive Viewer with SQL Express?

By default, SQL Server 2005 doesn’t allow remote connection so you have to enable it manually. If you try to connect to remote SQL Server without enable remote connection first, you’ll see one of these error messages.

“An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connection. …

“Login failed for user ‘sa’. The user is not associated with a trusted SQL Server connection.
To resolve these problems, you have 2 majors task. One is to enable both SQL Server and Windows authentication mode on SQL Server and the other is to allow remote connection and SQL Server Browser.

Step-by-step

  • Check that you have allowed both SQL Server and Windows Authentication mode (If you’re not use Windows Authentication mode). For instance, user ‘sa’.
    1. Login to SQL Server using SQL Server Management Studio Express on local SQL Server with Windows Authentication user. This will use Windows account to authenticate to SQL Server.

In Object Explorer, right click on the instance name and select Properties.
Open SQL Server Properties

  1. On the left, select Security and change Server authentication to SQL Server and Windows Authentication mode. If the choice is already selected, that means you have already allowed SQL Server authentication.
    Change SQL Server authentication mode
  2. There’ll be an information window shows that you need to restart SQL Server to takes effect of the changes.
    SQL Server need restart
  3. Right-click on the instance name again, select Restart to restart SQL Server service.
    Restart SQL Server Service
  4. Select Yes.
    Confirmation
  5. Wait for service stop and start.
    Restarting SQL Server Service
  6. That’s it. You have enabled both SQL Server and Windows authentication so now you can login to SQL Server with your current Windows account or your created account.
  • Check that you have enabled remote connection on SQL Server Surface Area Configuration
    1. Open SQL Server Surface Area Configuration.
      Open SQL Server Surface Area Configuration
    2. Select Surface Area Configuration for Services and Connections.
      Open Surface Area Configuration for Services and Connections
    3. On the left side, expand your SQL Server instance -> Database Engine -> Remote Connections. On the right side, select Local and remote connections -> using both TCP/IP and named pipes.
      Allow remote connections
    4. On the left side, select SQL Server Browser -> Service.
      On the right side, if the startup type is Disable, you need to change to Automatic and click Apply and click Start button to start the service. Then, click OK.
      Start SQL Server Browser
    5. You have finished configure. Now try to login to your SQL Server from remote computer using SQL Server authentication mode.
      Login to remote SQL Server
    6. Login to SQL Server succeeded.
      Login succeeded
Reference:
http://www.linglom.com/2007/08/31/enable-remote-connection-to-sql-server-2005-express/

Other Helpful links:
http://www.datamasker.com/SSE2005_NetworkCfg.htm