Follow by Email

Tuesday, July 26, 2016

Exchange 2013 DAG Database SEED ERROR / ADD ERROR

Hi,

For some reason My DAG database copies started to FAIL,

Error: Failed to open a log truncation context to source server ‘Ex2013_01.Mail.Com’. Hresult: 0xc7ff1004. Error: Error returned from an ESE function call (-1305).

Resolution:

Source Server : Ex2013_01.Mail.Com
Target/failing server :  Ex2013_02.Mail.Com
Database name: DB2
DB location :  D:/Database
Logs Location: D:/Database/Logs

on the target Server where the Database is Failing/ or being Added to...

1) Delete the Failing Database
2) Add the database copy : Add-MailboxDatabaseCopy -Identity DB2 -MailboxServer Ex2013_02 -ActivationPreference 2
3) You will see same ERROR: no worries
4) Go to the Database Folder location :  D:/Database/Logs
5) Move all the log files to another location
6) Open Exchange Management shell and run: Update-MailboxDatabaseCopy "DB2\Ex2013_02" -SourceServer Ex2013_01  -Verbose

and your database will start seeding...

Remember not to Logoff or Close the Shell else it will stop seeding...

Thanks


Tuesday, March 18, 2014

Outlook 2007 keeps on disconnecting from Exchange


One of our user was having issue of frequent disconnection and reconnection to exchange server

Now... the issue is not with Exchange, Internet, VPN tunnel etc. etc.... as suggested all around the internet...

Its with regestry settings on Client side, for connection timeout... Dont know how it got messed up....

Following steps require you to edit registry. PLEASE TAKE A BACKUP BEFORE GOING AHEAD..

Right clkick on the Key and Select EXPORT.... Save it... as backup... Create a Double Backup Just In case.. (JIC)

1) Click Start, click Run, type regedit and then click OK.
2) Browse to following registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
3) In the right side pane, Select "autodisconnect", Right click and select "Modify"
4) Now what ever the value is there type "fffffff" click OK


If the "autodisconnect" entry is not there then follow the below steps to create one

1) Browse to the folowing regestry location : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
2) In the right side pane, Right click and select "New" and then click DWORD (32 Bit for 64 Bit OS)
3) Type "autodisconnect", and press ENTER. (without the " ")
4) Select "autodisconnect", Right click and select "Modify"
5) Click Hexadecimal.
6) And type "ffffffff" (8 times f), and click OK. (without the " ")

Next

1) Now browse to following Registry location : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service\lanmanworkstation\parameters
2) In the right side pane, Right click and select "New" and then click DWORD (32 Bit for 64 Bit OS)
3) Type "KeepConn" (without the " ")
4) Select "KeepConn", Right click and select "Modify"
5) Type : 1 to 65535 (time in sec) so if you wish to keep the connection for 20 min type in (1200), I used 1800 (30 Min) 60*Minutes are seconds which you would like to enter so 60*30 = 1800

Next

1) Now browse to following Registry location : HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\RPC
2) In the right side pane, Right click and select "New" and then click DWORD (32 Bit for 64 Bit OS)
3) Type "DefConnectOpts" and press ENTER. (without the " ")
4) Select "DefConnectOpts", Right click and select "Modify"
5) And type "0", and click OK.

If the RPC key is missing no issues, create it by follow the steps to create it

1) Browse to following Registry location : HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\
2) In the right side pane, Right click and select "New" and then click "Key"
3) Type in RPC and press Enter



Now Reboot the PC and check... No more Outlook Disconnections..

Location for Different office version.

office 2007 : HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\RPC
office 2010 : HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\RPC
office 2013 : HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\RPC

hummm.... HKEY_CURRENT_USER\Software\Microsoft\Office\13.0\Outlook\RPC the 13 doesnot exist... seems Microsoft too thinks its JINXED

Friday, February 28, 2014

Intel Pro 1000 LAN Drivers for Server 2003/2008/2008 R2

Today I had a wearied problem...

Was installing Server 2008 R2 on Intel 61WW... all got installed well... but was not able to install LAN drivers..

No matter from where ever I download it from... didnt installed.. I tried on different Motherboard suspecting that the NIC might have got faulty...  even tried with Intel 61CR motherboard... Nope it refused to install

Tried Windows 7 64 bit drivers... hummm... nope that to didn't work... 

Because...  Intel & ofcourse Micro$oft thought that no one should be allowed to install Server class OS on Desktop Systems... Bad business Ethics... MONOPOLY.... again happy to SAY I LOVE... AMD and LINUX...  therefore they omitted the settings from where Server OS will not be able to recognize the Hardware and will not install the drivers..... and they never realized that some people who have test labs and dont have server class machines at their disposal to do R&D and testing.... will be using desktops as servers for testing so don't be greedy and release for all...

So finally I did what I use to do when Windows 7 came and  again manufacturers & Micro$oft refused to provide XP drivers with Laptops... Tweak driver Inf files with respective Hardware ID's and create a INF file which is recognized by the OS... here is what I did and it worked...

Download Intel 1000 Pro LAN drivers and Extract it...

Go to drictory where you extracted it... PRO1000\Winx64\NDIS62\  directory

make a copy of e1c62x64.inf file to any other folder.... In case you want to revert back to original state.

Open the following INF file in Notepad... and you will see....



[Intel]

[Intel.NTamd64.6.1.1]
; DisplayName                   Section              DeviceID
; -----------                   -------              --------
%E1502NC.DeviceDesc%            = E1502.6.1.1,       PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc%            = E1502.6.1.1,       PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc%            = E1502.6.1.1,       PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc%            = E1502.6.1.1,       PCI\VEN_8086&DEV_1502&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_04911025

[Intel.NTamd64.6.1]
; DisplayName                   Section        DeviceID
; -----------                   -------        --------
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_80001025


Change it to.....

[Intel.NTamd64.6.1.1]
; DisplayName                   Section              DeviceID
; -----------                   -------              --------
%E1502NC.DeviceDesc%            = E1502.6.1.1,       PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc%            = E1502.6.1.1,       PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc%            = E1502.6.1.1,       PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc%            = E1502.6.1.1,       PCI\VEN_8086&DEV_1502&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_04911025

[Intel.NTamd64.6.1]
; DisplayName                   Section        DeviceID
; -----------                   -------        --------
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_04911025



What we just did is that... Under section [Intel.NTamd64.6.1] we added the Hardware ID of the NIC which Server 2008 R2 can compare to Installed NIC ID... and accordingly Install the drivers..



%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_04911025


No clich Update driver in Device manager and browse to the Extracted location where we have just updated the INF file and... See the magic... the drivers wil install... and you will have working Desktop and Server 2008 R2 .....

The same can be done dor Server 2003 and Server 2008..

For Server 2003

\NDIS5x\e1c51x64.inf


[Intel]

[Intel.NTamd64.5.2]
; DisplayName                   Section        DeviceID
; -----------                   -------        --------
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503&SUBSYS_04911025

[Intel.NTamd64.5.2.1]
; DisplayName                   Section        DeviceID
; -----------                   -------        --------
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503&SUBSYS_04911025


For Server 2008

\NDIS61\e1c60x64.inf

[Intel]

[Intel.NTamd64.6.0.1]
; DisplayName                   Section              DeviceID
; -----------                   -------              --------
%E1502NC.DeviceDesc%            = E1502.6.0.1,       PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc%            = E1502.6.0.1,       PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc%            = E1502.6.0.1,       PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc%            = E1502.6.0.1,       PCI\VEN_8086&DEV_1502&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503&SUBSYS_04911025

[Intel.NTamd64.6.0]
; DisplayName                   Section        DeviceID
; -----------                   -------        --------
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503&SUBSYS_04911025


Hope that These GIANTS one day learn to behave and value the needs of all not just their own.....




Tuesday, February 18, 2014

MySQL error mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

I recently upgraded MySQL 5.1 to 5.5.36 on CENTOS 6.5 64 bit

upgrade went well but MySQL won't start...

only one line logged under /var/log/mysqlerror.log

mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

hummm.... so PID error

tried many things... Google search for PID issues...but...

boy.... no matter what I tried...... I was not able to make mysql service start... then...


I ran command  mysql_safe ....

Voila... it gave me another log entry...

InnoDB: Error: log file ./ib_logfile0 is of different size 0 20356374 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!




the error was because the size of innoDB logfile mention didnt match the size of logfile on the server...


so the solution was...

moving the current ib_logfiles to another location

cd ..

mkdir innodblog

mv /var/lib/mysql/ib_logfile* /var/lib/innodblog

service mysqld start

and finally it started...


Thanks

Friday, June 21, 2013

Upgrade MySQL 5.1 to 5.6 on Centos 6.4

Date: 21 June 2013

Yesterday I had to upgrade MySQL 5.1 on one of my Clients server, its pretty simple.... At least  after going through many poets and links.... breaking few things and make them work again... Really after I did it... it was pretty simple.. Ok... so u don't trust me... You be the judge here...

here we go...

First we we need to add EPEL Repos
Then we need to run Yum

and Voila its done

1) mkdir downloads -- create a directory to download the files

2) cd downloads -- go into the created directory

3) wget http://ftp.jaist.ac.jp/pub/Linux/Fedora//epel/6/x86_64/epel-release-6-8.noarch.rpm -- download the EPEL repo release installer

4) rpm -Uvh epel-release-6-8.noarch.rpm -- Upgrade it else replace -Uvh with  -ivh to Install it.

5) if  MySQL is already installed then stop the service -- command to stop the service: service mysqld stop

6) yum --enablerepo=remi,remi-test upgrade mysql mysql-server  --skipp-broken -- this will only install/upgrade all the dependencies and will avoid breaking any thing else which is working, playing save eah..

7) after checking the list what is being upgraded if all green pres Y to continue

8) wait for 10-30 minutes depending on your machine config & network usage

9) when completed run the command: service mysqld start

10) now your mysql is upgraded from 5.1 to 5.6

Done...

Told ya..... it was simple.. Happy Querying...




Wednesday, January 9, 2013

Dlink DCS 930L IP Camera and Recording with ISPY


Everybody now a days are looking forward to cheap surveillance & recording option... Dlink fits the bill

But along comes the pathetic DView recording and viewing software... being proprietary software... if you record with DView you will have to view in DView... and boy.... what a pain is it to view in it and play in it...

So my hunt for a solution which is easy & again... fits the bill.. starts..

Tried many Paid and Free but.... boy... its difficult to get anything work with it properly...

Finally.... Opensource and free came to rescue... ISpy

FREE AND FREE AND EASY... :) Surly fits the $$$ Bill $$$

Ok... Now lets start Installing it...

Download the software http://www.ispyconnect.com/download.aspx


Wait.... you have to download more... 

DOTNET 4

Full Download 32&64Bit
http://download.microsoft.com/download/9/5/A/95A9616B-7A37-4AF6-BC36-D6EA96C8DAAE/dotNetFx40_Full_x86_x64.exe

From FileHippo
Microsoft Link

VLC Player
You you require this... for Sound...


Now... lets start...

1) Install Dotnet 4
2) Install VLC Player
3) Install ISPY Connect software
4) Start ISPY
5) Click ADD
6) Select IP Camera with Wizard
7) Select Camera Model - Dlink
8) Model - DCS-930L
9) Click Next
10) Type in the user credentials for logging into the camera
11) Click Next
12) Type in you camera IP address, Select the Adapter if you have multiple adapters and Port if any customized.
13) Click Next
14) Select the URL which says http://User:Password@192.192.168.168:80/video/mjpg.cgi (this URL will reflect the IP of your camera I have entered dummy test)
15) Click Next
16) Edit the Camera Name, Directory (for recording) etc.
17)Click Finish
WE are Still not finished yet..... Close ISPY
18) Camera is installed and it will Record Video but NO Audio Recording... Grrr... Houston!!... We have a problem!!! and we have the solution too.. :) 
19)  Download the Firmware update of camera or from DLINK Site
20) Extract the downloaded firmware zip file to a folder
21) Log into the camera http://192.192.168.168
22) Type in you user credentials to login into the camera webapp
23) Click on Maintainance
24) Select  Firmware Upgrade from left side menu
25)  Click browse and browse to folder where Firmware was extracted in step 20
26) Click Upload and it will take 140 sec to complete the Upgrade
Nope it wont still record the Audio yet....
27) Now Open ISPY
28) Right click on the Video running of the added camera (Step 15) select Edit
29) Now Click on .... dotted browse button next to Microphone.
30) Select New and click on  >> button
31) Select the VLC tab
32) and enter the following in it http://User:Password@192.192.168.168/audio.cgi (Change the IP & Login details according to your setup)
33) Below there is Reconnect every.... type in 30 there ( if you dont do this the recording auto stops after 32 seconds) ..... another issue resolved.
34) Type in the Name for Microphone and Folder for recording to mark the devices for future reference.
35) Click Alerts tab, Uncheck  Alerts Enable ( to prevent alerts when ever it records anything)
36) Click the Recording Tab and Select NO Recording (Yup no Recording... else it will auto record when ever it senses any sound)
37) Click Finish...

Now you will see MIC bar under the Video streamed of the camera. 

  OK... We are done now... right click and record not it will record record both Video and Sound that too in MP4 format, better quality, playable in Many many media players

Soooo long... DVIEW.....

Wednesday, May 16, 2012

T-Mobile WRTU54G-TM @HOME network Outage

HI,

From past few days we were having issues with our T-Mobile WRTU54G-TM routers suddenly  they stopped working, SIM was not getting registered, Opened a ticket with T-Mobile support but they didnt bother to resolve it, I found that this was occuring accross the world and many  many users were facing issues.

T-Mobile reply was that we are having Outage with @HOME network  this is confirmed but there is not ETA for it.

As this was having huge impact on our business therefore I tried to find the solution and here is the solution


After doing much R&D with the settings and the T-mobile routers here are my findings and solution....

  1. The issue is not with any particular number series.
  2. The issue is not with the DNS settings.
  3. The issue is not with the Location of the Routers
  4. The issue is not with any ISP
  5. The issue is with the firmware of the T-Mobile router.
  6. The Firmware with V1.00.21 is not working
  7. I downgraded it to V1.00.04 and the lines have started working.

Please downgrade the firmware of the T-Mobile routers which are not working to the attached Firmware V1.00.04.

To downgrade the Firmware please follow the following steps

  1. Make directory c:\TmobileFW
  2. Download the firmware from the below link to c:\TmobileFW
  3. Extract the compressed file and you will get the firmware file “WRTU54G-TM_v1.00.04.bin
  4. Attach the T-mobile router to LAN ports (1-4) to your PC
  5. Set the IP of the computer to 192.168.0.10
  6. Log into the T-mobile router ( http://192.168.0.1 default IP) (admin/admin default)
  7. Click Administration in the menu
  8. Click Firmware Upgrade in the Sub menu
  9. Click browse & browse to c:\TmobileFW & Select WRTU54G-TM_v1.00.04.bin
  10. Click Upgrade
  11. Then let the Router reboot itself (the process will take approx 2 Min)
  12. After the reboot the Lines will be working  


http://download.modem-help.co.uk/mfcs-L/LinkSys/WRTU54G-TM/Firmware/v1/r1-00-04/WRTU54G-TM-v1.00.04.bin.7z.php?showFile=

direct download link

http://download.modem-help.co.uk/mfcs-L/LinkSys/WRTU54G-TM/Firmware/v1/r1-00-04/WRTU54G-TM-v1.00.04.bin.7z



Also posted in T-Mobile Forum

http://support.t-mobile.com/message/136687#136687
http://support.t-mobile.com/thread/25533 

Hope this helps someone and their issues are resolved.

REQUEST : if you had any Issues and have resolved them please always SHARE them

Thanks,


UPDATE

for my one office V1.00.04 worked but first I had tried the other versions of Firmwares too.... to find the right firmware to work...

Below are is the link for other version of firmwares. try others as on my second office firmware V1.00.15 worked and not the V1.00.04

http://download.modem-help.co.uk/mfcs-L/LinkSys/WRTU54G-TM/Firmware/v1/



Monday, January 2, 2012

Nokia N72 OFFLINE Mode

Today my Sony cell battery died therefore for emergency usage I had top revert back to my OLD Nokia N72, So I inserted the SIM and switched on the phone only to get another annoyance from the Dumb software makers...

No matter what I do, change profile, change SIM, restart many times but always greeted with "Insert SIM" can not change from Offline mode to Normal mode....

So I came to Google Genie for answer to my queries...

Got many replies and tried many options... here is what worked

1) Takeout the SIM
2) Takeout the Media Card
3) Put the battery in and switch on the phone again
4) dial the following numbers *#7370# This will reset the Phone ( This might Delete all the data so back it first) 
5) Now reinsert the SIM and Media Card and switch on the phone.
6) Phone will ask to whether to continue in Offline mode or Not, Select NO
7) if this also doesn't work then try *#7780#  for HARD reset of the phone ( This might Delete all the data so back it first) 
8) Now reinsert the SIM and Media Card and switch on the phone

Hope this helps some one out there.....




Tuesday, August 9, 2011

Failed to switch Terminal Server to INSTALL mode while installing Peachtree via Remote desktop

I had some issues with Peachtree.... (never ming Peachtree in inself is an HUGE ISSUE...  A pathetic peace of software anywhere) my company uses it for Accounts.


so I thought of installing it on a test server and I did a remote into it, when i ran the Autorun.exe it gave me the error...


Failed to switch Terminal Server to INSTALL mode ... BLA BLA bla....!!!!


I closed the error and ran setup.exe.... again the same error !!!!


tried many things but nothing did resolve my issue...

was it someting to be set on server  or some config issue....  didnt get anything and  no matter what iI did i couldnt get it to work ...

Just as I was browsing the Install folders I found another setup.exe when I execuited it Peachtree... (the junk) installed successfully..

Path to the file is 


Disk1\peachw\install\_setup.exe


mine was peachtree2010 just search for all .exe files and check yours.


I wonder if its Coders issues or the Company's issues to mislead others or blame other if their crap piece of code dosent work...


the blame was on remote desktop login I dont know WHY? and why it go installed from same CD but another location.

One more Microsoft in the making...


Thanks,

Friday, September 10, 2010

Windows 2008 Storage Server Defalut Password

Boy.......

I installed windows 2008 storage server for testing... like all installations... there were no errors or issues.. hummm... uummmm till the time it rebooted after finishing the setup.

Bang came the screen where it was asking the password to logon...?????

I started to remember whether I had configured one during the install or not... typed in few of my default password but none worked..... phew!!

so i tried searching the new. guess what???? (no point for guessing this one ;) ) I was not alone as usual with all M$ products.... everyone who had installed this storage server 2008 edition was wondering and looking for the default password.

it is in the Tools CD which is available from MSDN downloads...

so here is the pass so that many poor soles can be spared from more torture...

wSS2008! is the Default password for Storage server 2008

I wonder why to create a default password as anyhow this will be going to be public.