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.

Printing error or printing redirects to other branches

This topic has already been discussed, please read the previous post about this problem. Or go to Tags and click on Printing Problem, there are 4 post about this issue.

Contingency Plan - Early Announcement

To all users. The DC has a contingency plan scheduled on the 6th of December. All DC employees will be working from home remotely. This is a part of their yearly contingency plan.

More update on this on upcoming posts

Cargo System

Timeout Expired Reported by users on the Cargo System Program. Most users encounter this erorr on the login screen, right after they click on the login button. The cargo database data is getting really big especially with the tracking information. It has been reported to person in-charge and they are already working on the optimizing the system.

Also, please be reminded that when a user encounter slow response from the server, it doesn't mean that the problem is in the server. There are a number of reasons why this can happen:

• Internet connection. It is possible that your internet connection is slow, maybe because there is a problem on your ISP's backbone. If your internet connection is slow, you can greatly affect the performance of other users. Please try to log off the server and check your Internect Connection Speed.
  
• It is also possible that the DC Internet connection is having some problem, there are times that because of certain circumstances that are beyond our control, the Internet Connection at the DC Office may slow down, maybe the ISP has an outage. If this is the case, we will report it to our ISP, so they can check on the problem
  

Updates.

• Yesterday, there was a problem with the internet connection on remit2 and there were a lot of users using the cargo system, that is the reason for the system lag encountered by all users.
  
• The timeout expired problem encountered by users when logging in to the cargo program was already reported to the developer. We are waiting for the program update.
• Users on some users on remit2 encountered "RPC server is unavailable" . Also we later found out that there were no printers in the print list. The RPC Server might have crashed. The remit2 server hasn't been restarted for weeks now until yesterday afternoon.
  

iPaq 5550

The iPaq 5550. For those branches that are using iPaq for scanning boxes this article is for you.

Your iPaq 5550 runs under the Pocket PC 2003 or what we now know as the Windows Mobile 2003 operating system. It has a buit-in wifi compatible with wireless b and wireless g, and it has a bluetooth. It also has the expasion pack with a second battery and a compact flash module were you insert the compact flash adaptor of your socket scan scanner.

Most complain I received from users about the iPaq is it's wireless connection. Sometimes when a users starts to use it, they just notice that they cannot login to PPC Forex. Why is that? It's because you don't have an internet connection. Now, the first thing you need to do is verify the wifi signal strength. There is an icon on top that will tell you the signal strenght. If there is no connection, try to reset the iPaq. If you have done all the basic troubleshooting and still no success. Take off the expansion pack, now for no more that 10 seconds, take the main battery off the iPaq and put it back in. Turn it back on and you will notice that you can now connect to your wireless router. Just put everyting back in place and you're good to go.

Understanding Printing Problems

1. Printer drivers are not written to be used on Terminal Servers
   
   Finally, though, a lot of printer manufacturers see the necessity of developing their drivers to be used on Terminal Servers. But there are still printer drivers which are written for usage on a workstation by one user at the time. Printer drivers not written for Terminal Servers are, most of the time, not capable of handling so many printing jobs. When the driver becomes overwhelmed, this can cause the spooler services to crash, or even worse the operating system will blue screen.
   
2. Printjobs use a lot of bandwidth
   
   Printjobs normally consume a large amount of bandwidth. This is not specifically related to Terminal Server environments, but most times it is a bigger issue when using Terminal Services. Because Terminal Services are used a lot when users need access from co-locations, home locations or supplier/customer offices where the bandwidth is limited to the location where the Terminal Servers are. Within environments with a small amount of bandwidth and lots of printjobs these jobs can use the full amount of bandwidth. This actually means that users are not able to work anymore because Terminal Server related traffic is brought to a stand still by the printer traffic.
   
3. Version conflicts by third party drivers
   
   Often (especially with new printers) the Windows operating system doesn’t have the driver for that printer. To use all the functionality of that printer the driver made by the manufacturer must be used. It may happen that one new driver overwrites a DLL also used by another driver. It may also happen that the printers using the pre-existing DLL do not function anymore. Therefore every new printer driver must be tested extensively before using it in a production environment.
   
4. All printer drivers need to be available on all Terminal Servers
   
   The most important rule in the Terminal Server world is that all servers hosting the same applications must be 100% identical. This rule also applies to the printer drivers. It is a difficult job to keep all related files to printer drivers identical on all servers especially if you have lots of printer drivers.

Taken from MSterminalservices.org

Please Install Yahoo Messenger

All FOREX users are encourage to install and use yahoo messenger on their local machine(PC). To all those users who are not yet using Yahoo Messenger, please download and install yahoo messenger. You can download the messenger at messenger.yahoo.com or click here. For installation instruction please follow the one provided by Yahoo.

After you have installed and you have created your own account on yahoo, it's time to add these yahoo id to your yahoo buddy list, for support:

My yahoo id : Tenshinshoden
Edetera : Eggsdetera

You can use yahoo to send quick notes, question and request support.

You can still call me for support anytime on the same phone no. that you have.

How do I know which printer drivers work with Terminal Services?

All of the Microsoft-supplied printer drivers are tested with Terminal Services and guaranteed to work. Before using a third-party printer driver, make sure it has been certified for Terminal Services. There is a Windows Hardware Quality Labs (WHQL) program for getting third-party printer drivers certified on Terminal Services. Please ask your printer driver vendor to secure such certification.

Now, in the Forex Cargo domain, we have noticed that the most compatible printer brand is the

1. Epson
2. Canon
3. HP

THE LIST IS ORDERED BY COMPATIBILITY.

Note: If you are going to get a new printer for use with remote desktop, get a regular printer, don't get the All in Ones. If you already have a All In One printer, there is a work around, but you have to do the adjustments manually on your end. Meaning you have to change some settings on your pc's registry which we don't recommend.

I will post the registry settings soon.