dbTalk Databases Forums  

SP2 on a new node

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering


Discuss SP2 on a new node in the microsoft.public.sqlserver.clustering forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Andrea Gallazzi
 
Posts: n/a

Default SP2 on a new node - 12-20-2007 , 04:41 AM






Hello,

I cannot install SP2 on a new node that was added after SP2 applied to the
primary.
We had the following scenarios. Node A SP2, node B RTM.

Scenario 1) Resources moved to node A (also MSDTC and Cluster group). Setup
running on node A.
Setup warns (even in log) "The product instance XXX been patched with more
recent updates."
Since it sees that local instance is patched, setup don't go on. I cannot
select any clusterized instance.

Scenario 2) Resources moved to node B (also MSDTC and Cluster group). Setup
running on node B.

Setup logs:
12/18/2007 13:13:55.175 Exit code for passive node: XXXXA = 11203
12/18/2007 13:13:56.972 The following exception occurred: No passive nodes
were successfully patched Date: 12/18/2007 13:13:56.972 File:
\depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line:
3422
12/18/2007 13:13:57.440 Watson: Param1 = Unknown
12/18/2007 13:13:57.440 Watson: Param2 = 0x2b01
12/18/2007 13:13:57.440 Watson: Param3 = Unknown
12/18/2007 13:13:57.440 Watson: Param4 = 0x0
12/18/2007 13:13:57.440 Watson: Param5 = instance.cpp@3422
12/18/2007 13:13:57.440 Watson: Param6 = Unknown
12/18/2007 13:13:57.440 Watson: Param7 = SQL9
12/18/2007 13:13:57.440 Watson: Param8 = Hotfix@
12/18/2007 13:13:57.440 Watson: Param9 = x64
12/18/2007 13:13:57.440 Watson: Param10 = 3042

I undertstand, he cannot patch an already patched node (A). Setup stops
ignoring local node. So... how can I just patch a single node (B)?

I read uninstalling Setup Support Files and reinstalling them will help
faking an RTM node to the setup, but during uninstall I got the following
warning "Warning 26002: The following product(s) is dependent on Microsoft
SQL Server Setup Support Files (English), the key will be broken…" and it
lists one of our instances (just one). We will test it virtually, we cannot
afford loosing that instance.
Thank you!

Andrea

Reply With Quote
  #2  
Old   
RichardT
 
Posts: n/a

Default RE: SP2 on a new node - 01-04-2008 , 12:14 AM






Hi,

The error 'No passive nodes were successfully patched' is talked about in
the kb below:

http://support.microsoft.com/kb/929151



"Andrea Gallazzi" wrote:

Quote:
Hello,

I cannot install SP2 on a new node that was added after SP2 applied to the
primary.
We had the following scenarios. Node A SP2, node B RTM.

Scenario 1) Resources moved to node A (also MSDTC and Cluster group). Setup
running on node A.
Setup warns (even in log) "The product instance XXX been patched with more
recent updates."
Since it sees that local instance is patched, setup don't go on. I cannot
select any clusterized instance.

Scenario 2) Resources moved to node B (also MSDTC and Cluster group). Setup
running on node B.

Setup logs:
12/18/2007 13:13:55.175 Exit code for passive node: XXXXA = 11203
12/18/2007 13:13:56.972 The following exception occurred: No passive nodes
were successfully patched Date: 12/18/2007 13:13:56.972 File:
\depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line:
3422
12/18/2007 13:13:57.440 Watson: Param1 = Unknown
12/18/2007 13:13:57.440 Watson: Param2 = 0x2b01
12/18/2007 13:13:57.440 Watson: Param3 = Unknown
12/18/2007 13:13:57.440 Watson: Param4 = 0x0
12/18/2007 13:13:57.440 Watson: Param5 = instance.cpp@3422
12/18/2007 13:13:57.440 Watson: Param6 = Unknown
12/18/2007 13:13:57.440 Watson: Param7 = SQL9
12/18/2007 13:13:57.440 Watson: Param8 = Hotfix@
12/18/2007 13:13:57.440 Watson: Param9 = x64
12/18/2007 13:13:57.440 Watson: Param10 = 3042

I undertstand, he cannot patch an already patched node (A). Setup stops
ignoring local node. So... how can I just patch a single node (B)?

I read uninstalling Setup Support Files and reinstalling them will help
faking an RTM node to the setup, but during uninstall I got the following
warning "Warning 26002: The following product(s) is dependent on Microsoft
SQL Server Setup Support Files (English), the key will be broken…" and it
lists one of our instances (just one). We will test it virtually, we cannot
afford loosing that instance.
Thank you!

Andrea

Reply With Quote
  #3  
Old   
RichardT
 
Posts: n/a

Default RE: SP2 on a new node - 01-04-2008 , 10:01 PM



Hi Andrea,

Tried the fix below and it made no difference. Have you made any progress.

Thanks, Richard

"RichardT" wrote:

Quote:
Hi,

The error 'No passive nodes were successfully patched' is talked about in
the kb below:

http://support.microsoft.com/kb/929151



"Andrea Gallazzi" wrote:

Hello,

I cannot install SP2 on a new node that was added after SP2 applied to the
primary.
We had the following scenarios. Node A SP2, node B RTM.

Scenario 1) Resources moved to node A (also MSDTC and Cluster group). Setup
running on node A.
Setup warns (even in log) "The product instance XXX been patched with more
recent updates."
Since it sees that local instance is patched, setup don't go on. I cannot
select any clusterized instance.

Scenario 2) Resources moved to node B (also MSDTC and Cluster group). Setup
running on node B.

Setup logs:
12/18/2007 13:13:55.175 Exit code for passive node: XXXXA = 11203
12/18/2007 13:13:56.972 The following exception occurred: No passive nodes
were successfully patched Date: 12/18/2007 13:13:56.972 File:
\depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line:
3422
12/18/2007 13:13:57.440 Watson: Param1 = Unknown
12/18/2007 13:13:57.440 Watson: Param2 = 0x2b01
12/18/2007 13:13:57.440 Watson: Param3 = Unknown
12/18/2007 13:13:57.440 Watson: Param4 = 0x0
12/18/2007 13:13:57.440 Watson: Param5 = instance.cpp@3422
12/18/2007 13:13:57.440 Watson: Param6 = Unknown
12/18/2007 13:13:57.440 Watson: Param7 = SQL9
12/18/2007 13:13:57.440 Watson: Param8 = Hotfix@
12/18/2007 13:13:57.440 Watson: Param9 = x64
12/18/2007 13:13:57.440 Watson: Param10 = 3042

I undertstand, he cannot patch an already patched node (A). Setup stops
ignoring local node. So... how can I just patch a single node (B)?

I read uninstalling Setup Support Files and reinstalling them will help
faking an RTM node to the setup, but during uninstall I got the following
warning "Warning 26002: The following product(s) is dependent on Microsoft
SQL Server Setup Support Files (English), the key will be broken…" and it
lists one of our instances (just one). We will test it virtually, we cannot
afford loosing that instance.
Thank you!

Andrea

Reply With Quote
  #4  
Old   
RichardT
 
Posts: n/a

Default RE: SP2 on a new node - 01-04-2008 , 10:01 PM



Hi Andrea,

Tried the fix below and it made no difference. Have you made any progress.

Thanks, Richard

"RichardT" wrote:

Quote:
Hi,

The error 'No passive nodes were successfully patched' is talked about in
the kb below:

http://support.microsoft.com/kb/929151



"Andrea Gallazzi" wrote:

Hello,

I cannot install SP2 on a new node that was added after SP2 applied to the
primary.
We had the following scenarios. Node A SP2, node B RTM.

Scenario 1) Resources moved to node A (also MSDTC and Cluster group). Setup
running on node A.
Setup warns (even in log) "The product instance XXX been patched with more
recent updates."
Since it sees that local instance is patched, setup don't go on. I cannot
select any clusterized instance.

Scenario 2) Resources moved to node B (also MSDTC and Cluster group). Setup
running on node B.

Setup logs:
12/18/2007 13:13:55.175 Exit code for passive node: XXXXA = 11203
12/18/2007 13:13:56.972 The following exception occurred: No passive nodes
were successfully patched Date: 12/18/2007 13:13:56.972 File:
\depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line:
3422
12/18/2007 13:13:57.440 Watson: Param1 = Unknown
12/18/2007 13:13:57.440 Watson: Param2 = 0x2b01
12/18/2007 13:13:57.440 Watson: Param3 = Unknown
12/18/2007 13:13:57.440 Watson: Param4 = 0x0
12/18/2007 13:13:57.440 Watson: Param5 = instance.cpp@3422
12/18/2007 13:13:57.440 Watson: Param6 = Unknown
12/18/2007 13:13:57.440 Watson: Param7 = SQL9
12/18/2007 13:13:57.440 Watson: Param8 = Hotfix@
12/18/2007 13:13:57.440 Watson: Param9 = x64
12/18/2007 13:13:57.440 Watson: Param10 = 3042

I undertstand, he cannot patch an already patched node (A). Setup stops
ignoring local node. So... how can I just patch a single node (B)?

I read uninstalling Setup Support Files and reinstalling them will help
faking an RTM node to the setup, but during uninstall I got the following
warning "Warning 26002: The following product(s) is dependent on Microsoft
SQL Server Setup Support Files (English), the key will be broken…" and it
lists one of our instances (just one). We will test it virtually, we cannot
afford loosing that instance.
Thank you!

Andrea

Reply With Quote
  #5  
Old   
RichardT
 
Posts: n/a

Default RE: SP2 on a new node - 01-04-2008 , 10:01 PM



Hi Andrea,

Tried the fix below and it made no difference. Have you made any progress.

Thanks, Richard

"RichardT" wrote:

Quote:
Hi,

The error 'No passive nodes were successfully patched' is talked about in
the kb below:

http://support.microsoft.com/kb/929151



"Andrea Gallazzi" wrote:

Hello,

I cannot install SP2 on a new node that was added after SP2 applied to the
primary.
We had the following scenarios. Node A SP2, node B RTM.

Scenario 1) Resources moved to node A (also MSDTC and Cluster group). Setup
running on node A.
Setup warns (even in log) "The product instance XXX been patched with more
recent updates."
Since it sees that local instance is patched, setup don't go on. I cannot
select any clusterized instance.

Scenario 2) Resources moved to node B (also MSDTC and Cluster group). Setup
running on node B.

Setup logs:
12/18/2007 13:13:55.175 Exit code for passive node: XXXXA = 11203
12/18/2007 13:13:56.972 The following exception occurred: No passive nodes
were successfully patched Date: 12/18/2007 13:13:56.972 File:
\depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line:
3422
12/18/2007 13:13:57.440 Watson: Param1 = Unknown
12/18/2007 13:13:57.440 Watson: Param2 = 0x2b01
12/18/2007 13:13:57.440 Watson: Param3 = Unknown
12/18/2007 13:13:57.440 Watson: Param4 = 0x0
12/18/2007 13:13:57.440 Watson: Param5 = instance.cpp@3422
12/18/2007 13:13:57.440 Watson: Param6 = Unknown
12/18/2007 13:13:57.440 Watson: Param7 = SQL9
12/18/2007 13:13:57.440 Watson: Param8 = Hotfix@
12/18/2007 13:13:57.440 Watson: Param9 = x64
12/18/2007 13:13:57.440 Watson: Param10 = 3042

I undertstand, he cannot patch an already patched node (A). Setup stops
ignoring local node. So... how can I just patch a single node (B)?

I read uninstalling Setup Support Files and reinstalling them will help
faking an RTM node to the setup, but during uninstall I got the following
warning "Warning 26002: The following product(s) is dependent on Microsoft
SQL Server Setup Support Files (English), the key will be broken…" and it
lists one of our instances (just one). We will test it virtually, we cannot
afford loosing that instance.
Thank you!

Andrea

Reply With Quote
  #6  
Old   
RichardT
 
Posts: n/a

Default RE: SP2 on a new node - 01-04-2008 , 10:01 PM



Hi Andrea,

Tried the fix below and it made no difference. Have you made any progress.

Thanks, Richard

"RichardT" wrote:

Quote:
Hi,

The error 'No passive nodes were successfully patched' is talked about in
the kb below:

http://support.microsoft.com/kb/929151



"Andrea Gallazzi" wrote:

Hello,

I cannot install SP2 on a new node that was added after SP2 applied to the
primary.
We had the following scenarios. Node A SP2, node B RTM.

Scenario 1) Resources moved to node A (also MSDTC and Cluster group). Setup
running on node A.
Setup warns (even in log) "The product instance XXX been patched with more
recent updates."
Since it sees that local instance is patched, setup don't go on. I cannot
select any clusterized instance.

Scenario 2) Resources moved to node B (also MSDTC and Cluster group). Setup
running on node B.

Setup logs:
12/18/2007 13:13:55.175 Exit code for passive node: XXXXA = 11203
12/18/2007 13:13:56.972 The following exception occurred: No passive nodes
were successfully patched Date: 12/18/2007 13:13:56.972 File:
\depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line:
3422
12/18/2007 13:13:57.440 Watson: Param1 = Unknown
12/18/2007 13:13:57.440 Watson: Param2 = 0x2b01
12/18/2007 13:13:57.440 Watson: Param3 = Unknown
12/18/2007 13:13:57.440 Watson: Param4 = 0x0
12/18/2007 13:13:57.440 Watson: Param5 = instance.cpp@3422
12/18/2007 13:13:57.440 Watson: Param6 = Unknown
12/18/2007 13:13:57.440 Watson: Param7 = SQL9
12/18/2007 13:13:57.440 Watson: Param8 = Hotfix@
12/18/2007 13:13:57.440 Watson: Param9 = x64
12/18/2007 13:13:57.440 Watson: Param10 = 3042

I undertstand, he cannot patch an already patched node (A). Setup stops
ignoring local node. So... how can I just patch a single node (B)?

I read uninstalling Setup Support Files and reinstalling them will help
faking an RTM node to the setup, but during uninstall I got the following
warning "Warning 26002: The following product(s) is dependent on Microsoft
SQL Server Setup Support Files (English), the key will be broken…" and it
lists one of our instances (just one). We will test it virtually, we cannot
afford loosing that instance.
Thank you!

Andrea

Reply With Quote
  #7  
Old   
RichardT
 
Posts: n/a

Default RE: SP2 on a new node - 01-04-2008 , 10:01 PM



Hi Andrea,

Tried the fix below and it made no difference. Have you made any progress.

Thanks, Richard

"RichardT" wrote:

Quote:
Hi,

The error 'No passive nodes were successfully patched' is talked about in
the kb below:

http://support.microsoft.com/kb/929151



"Andrea Gallazzi" wrote:

Hello,

I cannot install SP2 on a new node that was added after SP2 applied to the
primary.
We had the following scenarios. Node A SP2, node B RTM.

Scenario 1) Resources moved to node A (also MSDTC and Cluster group). Setup
running on node A.
Setup warns (even in log) "The product instance XXX been patched with more
recent updates."
Since it sees that local instance is patched, setup don't go on. I cannot
select any clusterized instance.

Scenario 2) Resources moved to node B (also MSDTC and Cluster group). Setup
running on node B.

Setup logs:
12/18/2007 13:13:55.175 Exit code for passive node: XXXXA = 11203
12/18/2007 13:13:56.972 The following exception occurred: No passive nodes
were successfully patched Date: 12/18/2007 13:13:56.972 File:
\depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line:
3422
12/18/2007 13:13:57.440 Watson: Param1 = Unknown
12/18/2007 13:13:57.440 Watson: Param2 = 0x2b01
12/18/2007 13:13:57.440 Watson: Param3 = Unknown
12/18/2007 13:13:57.440 Watson: Param4 = 0x0
12/18/2007 13:13:57.440 Watson: Param5 = instance.cpp@3422
12/18/2007 13:13:57.440 Watson: Param6 = Unknown
12/18/2007 13:13:57.440 Watson: Param7 = SQL9
12/18/2007 13:13:57.440 Watson: Param8 = Hotfix@
12/18/2007 13:13:57.440 Watson: Param9 = x64
12/18/2007 13:13:57.440 Watson: Param10 = 3042

I undertstand, he cannot patch an already patched node (A). Setup stops
ignoring local node. So... how can I just patch a single node (B)?

I read uninstalling Setup Support Files and reinstalling them will help
faking an RTM node to the setup, but during uninstall I got the following
warning "Warning 26002: The following product(s) is dependent on Microsoft
SQL Server Setup Support Files (English), the key will be broken…" and it
lists one of our instances (just one). We will test it virtually, we cannot
afford loosing that instance.
Thank you!

Andrea

Reply With Quote
  #8  
Old   
RichardT
 
Posts: n/a

Default RE: SP2 on a new node - 01-04-2008 , 10:01 PM



Hi Andrea,

Tried the fix below and it made no difference. Have you made any progress.

Thanks, Richard

"RichardT" wrote:

Quote:
Hi,

The error 'No passive nodes were successfully patched' is talked about in
the kb below:

http://support.microsoft.com/kb/929151



"Andrea Gallazzi" wrote:

Hello,

I cannot install SP2 on a new node that was added after SP2 applied to the
primary.
We had the following scenarios. Node A SP2, node B RTM.

Scenario 1) Resources moved to node A (also MSDTC and Cluster group). Setup
running on node A.
Setup warns (even in log) "The product instance XXX been patched with more
recent updates."
Since it sees that local instance is patched, setup don't go on. I cannot
select any clusterized instance.

Scenario 2) Resources moved to node B (also MSDTC and Cluster group). Setup
running on node B.

Setup logs:
12/18/2007 13:13:55.175 Exit code for passive node: XXXXA = 11203
12/18/2007 13:13:56.972 The following exception occurred: No passive nodes
were successfully patched Date: 12/18/2007 13:13:56.972 File:
\depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line:
3422
12/18/2007 13:13:57.440 Watson: Param1 = Unknown
12/18/2007 13:13:57.440 Watson: Param2 = 0x2b01
12/18/2007 13:13:57.440 Watson: Param3 = Unknown
12/18/2007 13:13:57.440 Watson: Param4 = 0x0
12/18/2007 13:13:57.440 Watson: Param5 = instance.cpp@3422
12/18/2007 13:13:57.440 Watson: Param6 = Unknown
12/18/2007 13:13:57.440 Watson: Param7 = SQL9
12/18/2007 13:13:57.440 Watson: Param8 = Hotfix@
12/18/2007 13:13:57.440 Watson: Param9 = x64
12/18/2007 13:13:57.440 Watson: Param10 = 3042

I undertstand, he cannot patch an already patched node (A). Setup stops
ignoring local node. So... how can I just patch a single node (B)?

I read uninstalling Setup Support Files and reinstalling them will help
faking an RTM node to the setup, but during uninstall I got the following
warning "Warning 26002: The following product(s) is dependent on Microsoft
SQL Server Setup Support Files (English), the key will be broken…" and it
lists one of our instances (just one). We will test it virtually, we cannot
afford loosing that instance.
Thank you!

Andrea

Reply With Quote
  #9  
Old   
RichardT
 
Posts: n/a

Default RE: SP2 on a new node - 01-04-2008 , 10:01 PM



Hi Andrea,

Tried the fix below and it made no difference. Have you made any progress.

Thanks, Richard

"RichardT" wrote:

Quote:
Hi,

The error 'No passive nodes were successfully patched' is talked about in
the kb below:

http://support.microsoft.com/kb/929151



"Andrea Gallazzi" wrote:

Hello,

I cannot install SP2 on a new node that was added after SP2 applied to the
primary.
We had the following scenarios. Node A SP2, node B RTM.

Scenario 1) Resources moved to node A (also MSDTC and Cluster group). Setup
running on node A.
Setup warns (even in log) "The product instance XXX been patched with more
recent updates."
Since it sees that local instance is patched, setup don't go on. I cannot
select any clusterized instance.

Scenario 2) Resources moved to node B (also MSDTC and Cluster group). Setup
running on node B.

Setup logs:
12/18/2007 13:13:55.175 Exit code for passive node: XXXXA = 11203
12/18/2007 13:13:56.972 The following exception occurred: No passive nodes
were successfully patched Date: 12/18/2007 13:13:56.972 File:
\depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line:
3422
12/18/2007 13:13:57.440 Watson: Param1 = Unknown
12/18/2007 13:13:57.440 Watson: Param2 = 0x2b01
12/18/2007 13:13:57.440 Watson: Param3 = Unknown
12/18/2007 13:13:57.440 Watson: Param4 = 0x0
12/18/2007 13:13:57.440 Watson: Param5 = instance.cpp@3422
12/18/2007 13:13:57.440 Watson: Param6 = Unknown
12/18/2007 13:13:57.440 Watson: Param7 = SQL9
12/18/2007 13:13:57.440 Watson: Param8 = Hotfix@
12/18/2007 13:13:57.440 Watson: Param9 = x64
12/18/2007 13:13:57.440 Watson: Param10 = 3042

I undertstand, he cannot patch an already patched node (A). Setup stops
ignoring local node. So... how can I just patch a single node (B)?

I read uninstalling Setup Support Files and reinstalling them will help
faking an RTM node to the setup, but during uninstall I got the following
warning "Warning 26002: The following product(s) is dependent on Microsoft
SQL Server Setup Support Files (English), the key will be broken…" and it
lists one of our instances (just one). We will test it virtually, we cannot
afford loosing that instance.
Thank you!

Andrea

Reply With Quote
  #10  
Old   
RichardT
 
Posts: n/a

Default RE: SP2 on a new node - 01-04-2008 , 10:01 PM



Hi Andrea,

Tried the fix below and it made no difference. Have you made any progress.

Thanks, Richard

"RichardT" wrote:

Quote:
Hi,

The error 'No passive nodes were successfully patched' is talked about in
the kb below:

http://support.microsoft.com/kb/929151



"Andrea Gallazzi" wrote:

Hello,

I cannot install SP2 on a new node that was added after SP2 applied to the
primary.
We had the following scenarios. Node A SP2, node B RTM.

Scenario 1) Resources moved to node A (also MSDTC and Cluster group). Setup
running on node A.
Setup warns (even in log) "The product instance XXX been patched with more
recent updates."
Since it sees that local instance is patched, setup don't go on. I cannot
select any clusterized instance.

Scenario 2) Resources moved to node B (also MSDTC and Cluster group). Setup
running on node B.

Setup logs:
12/18/2007 13:13:55.175 Exit code for passive node: XXXXA = 11203
12/18/2007 13:13:56.972 The following exception occurred: No passive nodes
were successfully patched Date: 12/18/2007 13:13:56.972 File:
\depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line:
3422
12/18/2007 13:13:57.440 Watson: Param1 = Unknown
12/18/2007 13:13:57.440 Watson: Param2 = 0x2b01
12/18/2007 13:13:57.440 Watson: Param3 = Unknown
12/18/2007 13:13:57.440 Watson: Param4 = 0x0
12/18/2007 13:13:57.440 Watson: Param5 = instance.cpp@3422
12/18/2007 13:13:57.440 Watson: Param6 = Unknown
12/18/2007 13:13:57.440 Watson: Param7 = SQL9
12/18/2007 13:13:57.440 Watson: Param8 = Hotfix@
12/18/2007 13:13:57.440 Watson: Param9 = x64
12/18/2007 13:13:57.440 Watson: Param10 = 3042

I undertstand, he cannot patch an already patched node (A). Setup stops
ignoring local node. So... how can I just patch a single node (B)?

I read uninstalling Setup Support Files and reinstalling them will help
faking an RTM node to the setup, but during uninstall I got the following
warning "Warning 26002: The following product(s) is dependent on Microsoft
SQL Server Setup Support Files (English), the key will be broken…" and it
lists one of our instances (just one). We will test it virtually, we cannot
afford loosing that instance.
Thank you!

Andrea

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.