Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
prompt I:
sqlservr.exe -s development\mysql2k5 -T 1400
(also tried /T 1400)
and I get:
Application popup: SQL Server : Your SQL Server installation is either
corrupt or has been tampered with (Error: Instance name exceeds maximum
length.). Please uninstall then re-run setup to correct this problem
I've been trying lots of variations of this, as well as adding the -T to the
end of the startup parameters in the Config Manager. I know that the message
is bogus because I can run this instance of SQL from the Config Manager
without the -T.
Any ideas?
TIA, ChrisRSpecify only the instance name on the command prompt parameter:
sqlservr.exe -s mysql2k5 -T 1400
Also, you don't need trace flag 1400 once you install SQL 2005 SP1.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"ChrisR" <ChrisR@.noEmail.com> wrote in message
news:%235OcHtmkGHA.4044@.TK2MSFTNGP03.phx.gbl...
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to
> the
> end of the startup parameters in the Config Manager. I know that the
> message
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>|||Hi,
Do you need to enable trace flag 1400 to turn on Database Mirroring? That is
no longer needed if you apply Service Pack 1. I would recommend to try SP1
instead.
Ben Nevarez, MCDBA, OCP
Database Administrator
"ChrisR" wrote:
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to the
> end of the startup parameters in the Config Manager. I know that the message
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>
>|||Thank you both.
"ChrisR" <ChrisR@.noEmail.com> wrote in message
news:%235OcHtmkGHA.4044@.TK2MSFTNGP03.phx.gbl...
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to
the
> end of the startup parameters in the Config Manager. I know that the
message
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>
Showing posts with label howdy. Show all posts
Showing posts with label howdy. Show all posts
Tuesday, March 27, 2012
Cant start SQL 2005 with /T 1400.
Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
prompt I:
sqlservr.exe -s development\mysql2k5 -T 1400
(also tried /T 1400)
and I get:
Application popup: SQL Server : Your SQL Server installation is either
corrupt or has been tampered with (Error: Instance name exceeds maximum
length.). Please uninstall then re-run setup to correct this problem
I've been trying lots of variations of this, as well as adding the -T to the
end of the startup parameters in the Config Manager. I know that the message
is bogus because I can run this instance of SQL from the Config Manager
without the -T.
Any ideas?
TIA, ChrisRSpecify only the instance name on the command prompt parameter:
sqlservr.exe -s mysql2k5 -T 1400
Also, you don't need trace flag 1400 once you install SQL 2005 SP1.
Hope this helps.
Dan Guzman
SQL Server MVP
"ChrisR" <ChrisR@.noEmail.com> wrote in message
news:%235OcHtmkGHA.4044@.TK2MSFTNGP03.phx.gbl...
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to
> the
> end of the startup parameters in the Config Manager. I know that the
> message
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>|||Hi,
Do you need to enable trace flag 1400 to turn on Database Mirroring? That is
no longer needed if you apply Service Pack 1. I would recommend to try SP1
instead.
Ben Nevarez, MCDBA, OCP
Database Administrator
"ChrisR" wrote:
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to t
he
> end of the startup parameters in the Config Manager. I know that the messa
ge
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>
>|||Thank you both.
"ChrisR" <ChrisR@.noEmail.com> wrote in message
news:%235OcHtmkGHA.4044@.TK2MSFTNGP03.phx.gbl...
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to
the
> end of the startup parameters in the Config Manager. I know that the
message
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>|||Specify only the instance name on the command prompt parameter:
sqlservr.exe -s mysql2k5 -T 1400
Also, you don't need trace flag 1400 once you install SQL 2005 SP1.
Hope this helps.
Dan Guzman
SQL Server MVP
"ChrisR" <ChrisR@.noEmail.com> wrote in message
news:%235OcHtmkGHA.4044@.TK2MSFTNGP03.phx.gbl...
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to
> the
> end of the startup parameters in the Config Manager. I know that the
> message
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>|||Hi,
Do you need to enable trace flag 1400 to turn on Database Mirroring? That is
no longer needed if you apply Service Pack 1. I would recommend to try SP1
instead.
Ben Nevarez, MCDBA, OCP
Database Administrator
"ChrisR" wrote:
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to t
he
> end of the startup parameters in the Config Manager. I know that the messa
ge
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>
>|||Thank you both.
"ChrisR" <ChrisR@.noEmail.com> wrote in message
news:%235OcHtmkGHA.4044@.TK2MSFTNGP03.phx.gbl...
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to
the
> end of the startup parameters in the Config Manager. I know that the
message
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>sql
prompt I:
sqlservr.exe -s development\mysql2k5 -T 1400
(also tried /T 1400)
and I get:
Application popup: SQL Server : Your SQL Server installation is either
corrupt or has been tampered with (Error: Instance name exceeds maximum
length.). Please uninstall then re-run setup to correct this problem
I've been trying lots of variations of this, as well as adding the -T to the
end of the startup parameters in the Config Manager. I know that the message
is bogus because I can run this instance of SQL from the Config Manager
without the -T.
Any ideas?
TIA, ChrisRSpecify only the instance name on the command prompt parameter:
sqlservr.exe -s mysql2k5 -T 1400
Also, you don't need trace flag 1400 once you install SQL 2005 SP1.
Hope this helps.
Dan Guzman
SQL Server MVP
"ChrisR" <ChrisR@.noEmail.com> wrote in message
news:%235OcHtmkGHA.4044@.TK2MSFTNGP03.phx.gbl...
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to
> the
> end of the startup parameters in the Config Manager. I know that the
> message
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>|||Hi,
Do you need to enable trace flag 1400 to turn on Database Mirroring? That is
no longer needed if you apply Service Pack 1. I would recommend to try SP1
instead.
Ben Nevarez, MCDBA, OCP
Database Administrator
"ChrisR" wrote:
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to t
he
> end of the startup parameters in the Config Manager. I know that the messa
ge
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>
>|||Thank you both.
"ChrisR" <ChrisR@.noEmail.com> wrote in message
news:%235OcHtmkGHA.4044@.TK2MSFTNGP03.phx.gbl...
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to
the
> end of the startup parameters in the Config Manager. I know that the
message
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>|||Specify only the instance name on the command prompt parameter:
sqlservr.exe -s mysql2k5 -T 1400
Also, you don't need trace flag 1400 once you install SQL 2005 SP1.
Hope this helps.
Dan Guzman
SQL Server MVP
"ChrisR" <ChrisR@.noEmail.com> wrote in message
news:%235OcHtmkGHA.4044@.TK2MSFTNGP03.phx.gbl...
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to
> the
> end of the startup parameters in the Config Manager. I know that the
> message
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>|||Hi,
Do you need to enable trace flag 1400 to turn on Database Mirroring? That is
no longer needed if you apply Service Pack 1. I would recommend to try SP1
instead.
Ben Nevarez, MCDBA, OCP
Database Administrator
"ChrisR" wrote:
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to t
he
> end of the startup parameters in the Config Manager. I know that the messa
ge
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>
>|||Thank you both.
"ChrisR" <ChrisR@.noEmail.com> wrote in message
news:%235OcHtmkGHA.4044@.TK2MSFTNGP03.phx.gbl...
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to
the
> end of the startup parameters in the Config Manager. I know that the
message
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>sql
Friday, February 24, 2012
Cant make alert job work.
sql2k
sp4
Howdy all. I set up an Alert for deadlocks (# 1205) and have the checkbox
checked to fire off a job when it occurs. I then generate a deadlock, but the
job never gets fired off. Some important fun facts:
1; I ran dbcc traceon with 1204 and 1205 to log deadlocks.
2; I've tried running different jobs manually. They both work.
On the advice I got last week, I have verified that the Event Log service
and SQL Server Agent are both running. Its probably worth noting though that
while I do see the deadlock in the SQL Error Log, it doesnnt show up in the
Event Viewer.
Any ideas?
TIA, ChrisRYou need to configure 1205 so it is written to the eventlog. In EM, right-click the server, Manage
Messages. Here you search for 1205 and check to write to eventlog. In 2005, you cannot customize
system messages this way, though.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:EA439440-08D7-4BBA-8EA5-E69C4DEC6C44@.microsoft.com...
> sql2k
> sp4
> Howdy all. I set up an Alert for deadlocks (# 1205) and have the checkbox
> checked to fire off a job when it occurs. I then generate a deadlock, but the
> job never gets fired off. Some important fun facts:
> 1; I ran dbcc traceon with 1204 and 1205 to log deadlocks.
> 2; I've tried running different jobs manually. They both work.
> On the advice I got last week, I have verified that the Event Log service
> and SQL Server Agent are both running. Its probably worth noting though that
> while I do see the deadlock in the SQL Error Log, it doesnnt show up in the
> Event Viewer.
> Any ideas?
> TIA, ChrisR
>|||I keep trying to add this but it doesnt save it. I add it, hit OK, reopen and
its gone. Im logged in as local admin so I know thats not it. Any ideas?
"Tibor Karaszi" wrote:
> You need to configure 1205 so it is written to the eventlog. In EM, right-click the server, Manage
> Messages. Here you search for 1205 and check to write to eventlog. In 2005, you cannot customize
> system messages this way, though.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:EA439440-08D7-4BBA-8EA5-E69C4DEC6C44@.microsoft.com...
> > sql2k
> > sp4
> >
> > Howdy all. I set up an Alert for deadlocks (# 1205) and have the checkbox
> > checked to fire off a job when it occurs. I then generate a deadlock, but the
> > job never gets fired off. Some important fun facts:
> >
> > 1; I ran dbcc traceon with 1204 and 1205 to log deadlocks.
> > 2; I've tried running different jobs manually. They both work.
> >
> > On the advice I got last week, I have verified that the Event Log service
> > and SQL Server Agent are both running. Its probably worth noting though that
> > while I do see the deadlock in the SQL Error Log, it doesnnt show up in the
> > Event Viewer.
> >
> > Any ideas?
> >
> > TIA, ChrisR
> >
>|||Tibor I just realized this is more of a "not write to error log" issue, so I
reposted accordingly, thanks.
"Tibor Karaszi" wrote:
> You need to configure 1205 so it is written to the eventlog. In EM, right-click the server, Manage
> Messages. Here you search for 1205 and check to write to eventlog. In 2005, you cannot customize
> system messages this way, though.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:EA439440-08D7-4BBA-8EA5-E69C4DEC6C44@.microsoft.com...
> > sql2k
> > sp4
> >
> > Howdy all. I set up an Alert for deadlocks (# 1205) and have the checkbox
> > checked to fire off a job when it occurs. I then generate a deadlock, but the
> > job never gets fired off. Some important fun facts:
> >
> > 1; I ran dbcc traceon with 1204 and 1205 to log deadlocks.
> > 2; I've tried running different jobs manually. They both work.
> >
> > On the advice I got last week, I have verified that the Event Log service
> > and SQL Server Agent are both running. Its probably worth noting though that
> > while I do see the deadlock in the SQL Error Log, it doesnnt show up in the
> > Event Viewer.
> >
> > Any ideas?
> >
> > TIA, ChrisR
> >
>
sp4
Howdy all. I set up an Alert for deadlocks (# 1205) and have the checkbox
checked to fire off a job when it occurs. I then generate a deadlock, but the
job never gets fired off. Some important fun facts:
1; I ran dbcc traceon with 1204 and 1205 to log deadlocks.
2; I've tried running different jobs manually. They both work.
On the advice I got last week, I have verified that the Event Log service
and SQL Server Agent are both running. Its probably worth noting though that
while I do see the deadlock in the SQL Error Log, it doesnnt show up in the
Event Viewer.
Any ideas?
TIA, ChrisRYou need to configure 1205 so it is written to the eventlog. In EM, right-click the server, Manage
Messages. Here you search for 1205 and check to write to eventlog. In 2005, you cannot customize
system messages this way, though.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:EA439440-08D7-4BBA-8EA5-E69C4DEC6C44@.microsoft.com...
> sql2k
> sp4
> Howdy all. I set up an Alert for deadlocks (# 1205) and have the checkbox
> checked to fire off a job when it occurs. I then generate a deadlock, but the
> job never gets fired off. Some important fun facts:
> 1; I ran dbcc traceon with 1204 and 1205 to log deadlocks.
> 2; I've tried running different jobs manually. They both work.
> On the advice I got last week, I have verified that the Event Log service
> and SQL Server Agent are both running. Its probably worth noting though that
> while I do see the deadlock in the SQL Error Log, it doesnnt show up in the
> Event Viewer.
> Any ideas?
> TIA, ChrisR
>|||I keep trying to add this but it doesnt save it. I add it, hit OK, reopen and
its gone. Im logged in as local admin so I know thats not it. Any ideas?
"Tibor Karaszi" wrote:
> You need to configure 1205 so it is written to the eventlog. In EM, right-click the server, Manage
> Messages. Here you search for 1205 and check to write to eventlog. In 2005, you cannot customize
> system messages this way, though.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:EA439440-08D7-4BBA-8EA5-E69C4DEC6C44@.microsoft.com...
> > sql2k
> > sp4
> >
> > Howdy all. I set up an Alert for deadlocks (# 1205) and have the checkbox
> > checked to fire off a job when it occurs. I then generate a deadlock, but the
> > job never gets fired off. Some important fun facts:
> >
> > 1; I ran dbcc traceon with 1204 and 1205 to log deadlocks.
> > 2; I've tried running different jobs manually. They both work.
> >
> > On the advice I got last week, I have verified that the Event Log service
> > and SQL Server Agent are both running. Its probably worth noting though that
> > while I do see the deadlock in the SQL Error Log, it doesnnt show up in the
> > Event Viewer.
> >
> > Any ideas?
> >
> > TIA, ChrisR
> >
>|||Tibor I just realized this is more of a "not write to error log" issue, so I
reposted accordingly, thanks.
"Tibor Karaszi" wrote:
> You need to configure 1205 so it is written to the eventlog. In EM, right-click the server, Manage
> Messages. Here you search for 1205 and check to write to eventlog. In 2005, you cannot customize
> system messages this way, though.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:EA439440-08D7-4BBA-8EA5-E69C4DEC6C44@.microsoft.com...
> > sql2k
> > sp4
> >
> > Howdy all. I set up an Alert for deadlocks (# 1205) and have the checkbox
> > checked to fire off a job when it occurs. I then generate a deadlock, but the
> > job never gets fired off. Some important fun facts:
> >
> > 1; I ran dbcc traceon with 1204 and 1205 to log deadlocks.
> > 2; I've tried running different jobs manually. They both work.
> >
> > On the advice I got last week, I have verified that the Event Log service
> > and SQL Server Agent are both running. Its probably worth noting though that
> > while I do see the deadlock in the SQL Error Log, it doesnnt show up in the
> > Event Viewer.
> >
> > Any ideas?
> >
> > TIA, ChrisR
> >
>
Subscribe to:
Posts (Atom)