SQL Server Replication Re Design

I changed the design of the replication. Before this changed the setup was, both, backup terminal server, Cargo Database, the Distribution database for the replication are on one machine.

This setup is not recommended. The ideal setup should be that each services must be housed on a separate machine, this way, if work is needed on each server, other services can continue their function normally.

Zero Space Available on Cargo Data Device.

Recently we have encountered a problem with the Cargo Data Device. When I look at the properties of the Database from Enterprise Manager, It shows Size: xxxxx mb and space available: 0.00 . It shouldn't be zero since the database is set to autogrow at least xx mb. Apprently the sysindexes table is out of sync. Running " DBCC UPDATEUSAGE (0) " or " sp_spaceused @updateusage = true " fixed the problem.

With the later option it actually executes " DBCC UPDATEUSAGE (0) " within it.

Turned off Replication

Today Nov. 27, replication of data to FCPHIL Server will be temporarily disable, to allow remote users to work on remit2. Cargo data is temporarily moved to another server. We will temporarily dedicate this server as the distributor and as a Backup Terminal Server.

Remit 2 -Terminal Server slow

One reason why users encounter slow perfomance on the remit2 terminal server is because, it is transferring cargo data in manila. Hopefully next year we can be able to add a new server dedicated to this task. This server is also the Distributor for data transfer.

Workaround for Printers that are not Redirected in a Remote Desktop Session

This article is from Microsoft Knowledgebase. It was forwarded to me by Chit De Jesus. Like other remote users she cannot print on the all in one wireless HP printer. This workaround requires you to go under the hood and get your hands dirty by going into your Windows XP registry. She tweak the Registry setting of her workstation and now the walla, the problem is gone.

I have to warn you, editing the registry of your pc might render your perfectly working windows xp unusable.

Ok here we go:
Printers That Use Ports That Do Not Begin With COM, LPT, or USB Are Not Redirected in a Remote Desktop or Terminal Services Session.

To resolve this problem on a computer that is not running Windows Server 2003, force all ports (including DOT4) on the client computer to be filtered for redirection. To do this, add a DWORD value named FilterQueueType to HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR and set its value data to FFFFFFFF.

Follow these steps, and then quit Registry Editor:

1.	Click Start, click Run, type regedit, and then click OK.
2.	Locate and then click the following key in the registry: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR
3.	On the Edit menu, point to New, and then click DWORD Value.
4.	Type FilterQueueType, and then press ENTER.
5.	On the Edit menu, click Modify.
6.	Type FFFFFFFF, and then click OK.

This enables all ports on the client to be redirected.

To work around this problem on a client computer that has a multifunction print device, change the port that the multifunction print device uses from DOT4 to an LPT port.

For example, to configure a multifunction print device to use an LPT port on a Windows XP-based computer, follow these steps:

1.	InControl Panel, openPrinters and Faxes.
2.	Right-click the local printer that is not redirected, and then click Properties.
3.	Click the Ports tab, click an LPT port, and then click Apply. The printer should now appear next to that port.
4.	Close the Printer Properties window, and then reconnect by using Remote Desktop.

Important When a multifunction printer is using a standard LPT port instead of the DOT4 port, it loses its multifunction capabilities, such as scanning, faxing, or copying. To regain the multifunction capabilities, the print device must use the DOT4 port.
To read the complete article please go to microsoft.com. Here is the complete link:
http://support.microsoft.com/kb/302361/en-us

Cannot Find Printer in the Printer List

There are times, remote users can't find their printer in the printer list, this is one of the most common problem encountered by remote users. First thing you need to do is to log off the server.

1. Close the system that you are using, (Remittance or Cargo).
2. Log off the server in a proper way. Don't just disconnect from your session. There is a big difference between logging off and disconnecting from the server.
• If you disconnect, and don't log off, you will go back on the same session or scenario where you left off. Nothing has change, the problem will be there waiting for you when you log back the server. Whereas
• If you log off, all open programs and printers created for your session are cleared. When you log back in the server, the terminal server will create a new session, for you together with a new printer for that session.

It is not recommended for users to disconnect from their session. Please make it a practice to always log off the server to minimize printing problem and to consume server resources.

Replication Problem

Main problem with replication on our setup is the reliability of internet connection. Most of the time, data in the U.S are not replicated on the server in FCPhil because their internet connection is down. We have a dedicated server here in the U.S that process the replication, this server often cannot to connect to the server in FCPhil.