Hi All
I am trying to install MDSE SP 4 for BCM V2 and get the message setup failed
to configure server.This is what the confsgvr.out states
An error occurred while attempting to start the service (1460)
SQL Server configuration failed.
I have already tried renaming the SQL folder and reinstall still the same
issue .Also did download and install ISS Script.Any ideas ?Thanks in advance
for your time and effort
With Regards
Raul Thomas
hi Raul,
Raul wrote:
> Hi All
> I am trying to install MDSE SP 4 for BCM V2 and get the message setup
> failed to configure server.This is what the confsgvr.out states
> An error occurred while attempting to start the service (1460)
> SQL Server configuration failed.
> I have already tried renaming the SQL folder and reinstall still the
> same issue .Also did download and install ISS Script.Any ideas
> ?Thanks in advance for your time and effort
if the machine is "clean" and no leftover are present at OS level and/or
registry level
(http://support.microsoft.com/default...99&Product=sql),
the problem can be related, on WinXP sp2, to MDAC stack corruption... you
can not fix it by reinstalling MDAC as no package exists for 2.8.1 level,
but you can fix it as described in
http://www.macropool.com/en/download/mdac_xp_sp2.html
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks for the update.Will the same and keep you updated
With Regards
Raul Thomas
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:40q4a5F1be76uU1@.individual.net...
> hi Raul,
> Raul wrote:
> if the machine is "clean" and no leftover are present at OS level and/or
> registry level
> (http://support.microsoft.com/default...99&Product=sql),
> the problem can be related, on WinXP sp2, to MDAC stack corruption... you
> can not fix it by reinstalling MDAC as no package exists for 2.8.1 level,
> but you can fix it as described in
> http://www.macropool.com/en/download/mdac_xp_sp2.html
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||You might check your computer hostname is all uppercase rather than a mix of
upper and lower case characters...worked for me.
"Raul" <v_2rath@.hotmail.com> wrote in message
news:%23rIP2OdBGHA.3064@.TK2MSFTNGP10.phx.gbl...
> Thanks for the update.Will the same and keep you updated
> --
> With Regards
> Raul Thomas
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:40q4a5F1be76uU1@.individual.net...
>
Showing posts with label configure. Show all posts
Showing posts with label configure. Show all posts
Wednesday, March 28, 2012
Monday, March 26, 2012
reg Caching Configuration
Hi ,
I am trying to configure the Caching in Reporting Services. I came to know
that i have to store the credentials in the Report server. After storing the
credentitals in the report server using Datasource properties and i tried to
acess the report. i am getting following error.
â?¢ â'An error has occurred during report processing.
o Cannot create a connection to data source '<datasourcename>'.
Login failed for user '<user>'. The user is not associated with a trusted
SQL Server connection.
Is there anything I am missing here.
Thanks in advance
BhaskarBhaskar
I would suggest that sql server is rejecting the user name you are
using . Try to create a connection by using the connection wizard
which will allow you to test the connection. In visual studio right
click on shared datas sources and click on add new data source . In
the dialog box, instead of typing your connection string , click edit
try specifying sql server authentication. Click on test connection. if
that works , try using the connection to execute a query or stored
proc by creating a new data set .
Cheers
Shai
On Nov 20, 8:03 am, Bhaskar <Bhas...@.discussions.microsoft.com>
wrote:
> Hi ,
> I am trying to configure the Caching in Reporting Services. I came to know
> that i have to store the credentials in the Report server. After storing the
> credentitals in the report server using Datasource properties and i tried to
> acess the report. i am getting following error.
> * 'An error has occurred during report processing.
> o Cannot create a connection to data source '<datasourcename>'.
> Login failed for user '<user>'. The user is not associated with a trusted
> SQL Server connection.
> Is there anything I am missing here.
> Thanks in advance
> Bhaskar|||On Nov 19, 5:03 pm, Bhaskar <Bhas...@.discussions.microsoft.com> wrote:
> Hi ,
> I am trying to configure the Caching in Reporting Services. I came to know
> that i have to store the credentials in the Report server. After storing the
> credentitals in the report server using Datasource properties and i tried to
> acess the report. i am getting following error.
> * 'An error has occurred during report processing.
> o Cannot create a connection to data source '<datasourcename>'.
> Login failed for user '<user>'. The user is not associated with a trusted
> SQL Server connection.
> Is there anything I am missing here.
> Thanks in advance
> Bhaskar
Bhaskar,
Any time you see the word "Trusted" in an error messege it means you
have the database set to Windows Authentication only and you are
passing a User ID and Password in your connection. Either
1) Change the connection to Windows Authentication which will not
prompt for credentials OR
2) Right click on your SQL Server, not the database but the server,
and go to Properties -> Security; then change to SQL Server and
Windows Authenication mode.
Dennis
I am trying to configure the Caching in Reporting Services. I came to know
that i have to store the credentials in the Report server. After storing the
credentitals in the report server using Datasource properties and i tried to
acess the report. i am getting following error.
â?¢ â'An error has occurred during report processing.
o Cannot create a connection to data source '<datasourcename>'.
Login failed for user '<user>'. The user is not associated with a trusted
SQL Server connection.
Is there anything I am missing here.
Thanks in advance
BhaskarBhaskar
I would suggest that sql server is rejecting the user name you are
using . Try to create a connection by using the connection wizard
which will allow you to test the connection. In visual studio right
click on shared datas sources and click on add new data source . In
the dialog box, instead of typing your connection string , click edit
try specifying sql server authentication. Click on test connection. if
that works , try using the connection to execute a query or stored
proc by creating a new data set .
Cheers
Shai
On Nov 20, 8:03 am, Bhaskar <Bhas...@.discussions.microsoft.com>
wrote:
> Hi ,
> I am trying to configure the Caching in Reporting Services. I came to know
> that i have to store the credentials in the Report server. After storing the
> credentitals in the report server using Datasource properties and i tried to
> acess the report. i am getting following error.
> * 'An error has occurred during report processing.
> o Cannot create a connection to data source '<datasourcename>'.
> Login failed for user '<user>'. The user is not associated with a trusted
> SQL Server connection.
> Is there anything I am missing here.
> Thanks in advance
> Bhaskar|||On Nov 19, 5:03 pm, Bhaskar <Bhas...@.discussions.microsoft.com> wrote:
> Hi ,
> I am trying to configure the Caching in Reporting Services. I came to know
> that i have to store the credentials in the Report server. After storing the
> credentitals in the report server using Datasource properties and i tried to
> acess the report. i am getting following error.
> * 'An error has occurred during report processing.
> o Cannot create a connection to data source '<datasourcename>'.
> Login failed for user '<user>'. The user is not associated with a trusted
> SQL Server connection.
> Is there anything I am missing here.
> Thanks in advance
> Bhaskar
Bhaskar,
Any time you see the word "Trusted" in an error messege it means you
have the database set to Windows Authentication only and you are
passing a User ID and Password in your connection. Either
1) Change the connection to Windows Authentication which will not
prompt for credentials OR
2) Right click on your SQL Server, not the database but the server,
and go to Properties -> Security; then change to SQL Server and
Windows Authenication mode.
Dennis
Refuse connections
Hi guys,
I would like to know how could I configure my SQL Server (2000) to refuse every connection except localhost or server-name ?
I am sure this can be acomplished, but I've looked everywhere and can't find it.
I use asp.net only and I want to configure the server to accept connections from local computer and that's it. Any thoughts?
ThanksDisable all network protocols except shared memory.|||Thanks.
Also, I have two instances of MSSQL installed, one is SQL 2000 & other is Desktop Edition, will the client configurations apply to both or just to SQL 2000 and if just to SQL 2000 how can I configure it also for the Desktop Edition?|||It doesn't work. Tested it today, disabled all protocols except shared memory and I still can connect from another box to that specific box with Enterprise Manager (for example)
Any other ideas?|||It doesn't work. Tested it today, disabled all protocols except shared memory and I still can connect from another box to that specific box with Enterprise Manager (for example)
Any other ideas?
Did you restart SQL after changing the network configuration? Look at the error log for SQL Server when it restarts, there should be entries in there to indicate what protocols/ports SQL is listening on.
Regards,
hmscott|||Restarted, still same thing. I can connect from one box to the other. Log file:
2005-12-06 04:11:31.10 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2005-12-06 04:11:31.10 server Copyright (C) 1988-2002 Microsoft Corporation.
2005-12-06 04:11:31.10 server All rights reserved.
2005-12-06 04:11:31.10 server Server Process ID is 3336.
2005-12-06 04:11:31.10 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2005-12-06 04:11:31.20 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2005-12-06 04:11:32.78 server SQL Server configured for thread mode processing.
2005-12-06 04:11:32.79 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2005-12-06 04:11:32.85 server Attempting to initialize Distributed Transaction Coordinator.
2005-12-06 04:11:35.71 spid3 Starting up database 'master'.
2005-12-06 04:11:36.10 spid3 Server name is 'SERVER9'.
2005-12-06 04:11:36.10 spid3 Skipping startup of clean database id 44
2005-12-06 04:11:36.26 server Using 'SSNETLIB.DLL' version '8.0.766'.
2005-12-06 04:11:36.26 spid5 Starting up database 'model'.
2005-12-06 04:11:36.35 spid8 Starting up database 'msdb'.
2005-12-06 04:11:36.35 spid9 Starting up database 'pubs'.
2005-12-06 04:11:36.37 spid10 Starting up database 'Northwind'.
2005-12-06 04:11:36.37 spid11 Starting up database 'ahsweb'.
2005-12-06 04:11:38.68 spid5 Clearing tempdb database.
2005-12-06 04:11:39.42 server SQL server listening on 69.56.147.XXX: 1433.
2005-12-06 04:11:39.42 server SQL server listening on 69.56.147.XXX: 1433.
2005-12-06 04:11:39.42 server SQL server listening on 69.56.147.XXX: 1433.
2005-12-06 04:11:39.42 server SQL server listening on 69.56.147.XXX: 1433.
2005-12-06 04:11:39.42 server SQL server listening on 69.93.178.XXX: 2005-12-06 04:11:39.42 server SQL server listening on 69.93.178.XXX: 1433.
2005-12-06 04:11:39.42 server SQL server listening on 127.0.0.1: 1433.
2005-12-06 04:11:40.45 server SQL server listening on TCP, Named Pipes.
2005-12-06 04:11:40.48 server SQL Server is ready for client connections
2005-12-06 04:11:39.95 spid9 Starting up database 'ahl'.
2005-12-06 04:11:40.06 spid10 Starting up database 'afp'.
2005-12-06 04:11:40.31 spid8 Starting up database 'act'.
2005-12-06 04:12:19.15 spid8 Recovery is checkpointing database 'eah' (73)
2005-12-06 04:12:29.78 spid51 Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.
2005-12-06 04:12:55.46 spid3 Recovery complete.
2005-12-06 04:12:55.46 spid3 SQL global counter collection task is created.|||The Enterprise Manager says TCP is disabled but it still shows up on the logs
Any work arround?|||2005-12-06 05:37:02.30 server SQL server listening on 69.9.44.XXX 1433.
2005-12-06 05:37:02.30 server SQL server listening on 69.9.44.XXX: 1433.
2005-12-06 05:37:02.30 server SQL server listening on 69.9.44.XXX: 1433.
2005-12-06 05:37:02.30 server SQL server listening on 69.9.44.XXX: 1433.
2005-12-06 05:37:02.30 server SQL server listening on 69.9.44.XXX: 1433.
2005-12-06 05:37:02.30 server SQL server listening on 127.0.0.1: 1433.
2005-12-06 05:37:02.30 server SuperSocket Info: Bind failed on TCP port 1433.
2005-12-06 05:37:02.30 server SuperSocket Info: Bind failed on TCP port 1433.
2005-12-06 05:37:02.32 server SQL server listening on TCP, Shared Memory.
2005-12-06 05:37:02.32 server SQL Server is ready for client connections
Even thought TCP is disabled|||Any more thoughts? Anyone?|||You're sure you are diabling TCP in the Server Network Parameters (or Server Network Utility)? The Client network utility looks the same, but it has a different function. Also, why the multiple IP addresses? I don't usually multi-home a database server (except for a cluster), so I don't know how SQL will behave with multiple IP addresses.
Regards,
hmscott
I would like to know how could I configure my SQL Server (2000) to refuse every connection except localhost or server-name ?
I am sure this can be acomplished, but I've looked everywhere and can't find it.
I use asp.net only and I want to configure the server to accept connections from local computer and that's it. Any thoughts?
ThanksDisable all network protocols except shared memory.|||Thanks.
Also, I have two instances of MSSQL installed, one is SQL 2000 & other is Desktop Edition, will the client configurations apply to both or just to SQL 2000 and if just to SQL 2000 how can I configure it also for the Desktop Edition?|||It doesn't work. Tested it today, disabled all protocols except shared memory and I still can connect from another box to that specific box with Enterprise Manager (for example)
Any other ideas?|||It doesn't work. Tested it today, disabled all protocols except shared memory and I still can connect from another box to that specific box with Enterprise Manager (for example)
Any other ideas?
Did you restart SQL after changing the network configuration? Look at the error log for SQL Server when it restarts, there should be entries in there to indicate what protocols/ports SQL is listening on.
Regards,
hmscott|||Restarted, still same thing. I can connect from one box to the other. Log file:
2005-12-06 04:11:31.10 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2005-12-06 04:11:31.10 server Copyright (C) 1988-2002 Microsoft Corporation.
2005-12-06 04:11:31.10 server All rights reserved.
2005-12-06 04:11:31.10 server Server Process ID is 3336.
2005-12-06 04:11:31.10 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2005-12-06 04:11:31.20 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2005-12-06 04:11:32.78 server SQL Server configured for thread mode processing.
2005-12-06 04:11:32.79 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2005-12-06 04:11:32.85 server Attempting to initialize Distributed Transaction Coordinator.
2005-12-06 04:11:35.71 spid3 Starting up database 'master'.
2005-12-06 04:11:36.10 spid3 Server name is 'SERVER9'.
2005-12-06 04:11:36.10 spid3 Skipping startup of clean database id 44
2005-12-06 04:11:36.26 server Using 'SSNETLIB.DLL' version '8.0.766'.
2005-12-06 04:11:36.26 spid5 Starting up database 'model'.
2005-12-06 04:11:36.35 spid8 Starting up database 'msdb'.
2005-12-06 04:11:36.35 spid9 Starting up database 'pubs'.
2005-12-06 04:11:36.37 spid10 Starting up database 'Northwind'.
2005-12-06 04:11:36.37 spid11 Starting up database 'ahsweb'.
2005-12-06 04:11:38.68 spid5 Clearing tempdb database.
2005-12-06 04:11:39.42 server SQL server listening on 69.56.147.XXX: 1433.
2005-12-06 04:11:39.42 server SQL server listening on 69.56.147.XXX: 1433.
2005-12-06 04:11:39.42 server SQL server listening on 69.56.147.XXX: 1433.
2005-12-06 04:11:39.42 server SQL server listening on 69.56.147.XXX: 1433.
2005-12-06 04:11:39.42 server SQL server listening on 69.93.178.XXX: 2005-12-06 04:11:39.42 server SQL server listening on 69.93.178.XXX: 1433.
2005-12-06 04:11:39.42 server SQL server listening on 127.0.0.1: 1433.
2005-12-06 04:11:40.45 server SQL server listening on TCP, Named Pipes.
2005-12-06 04:11:40.48 server SQL Server is ready for client connections
2005-12-06 04:11:39.95 spid9 Starting up database 'ahl'.
2005-12-06 04:11:40.06 spid10 Starting up database 'afp'.
2005-12-06 04:11:40.31 spid8 Starting up database 'act'.
2005-12-06 04:12:19.15 spid8 Recovery is checkpointing database 'eah' (73)
2005-12-06 04:12:29.78 spid51 Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.
2005-12-06 04:12:55.46 spid3 Recovery complete.
2005-12-06 04:12:55.46 spid3 SQL global counter collection task is created.|||The Enterprise Manager says TCP is disabled but it still shows up on the logs
Any work arround?|||2005-12-06 05:37:02.30 server SQL server listening on 69.9.44.XXX 1433.
2005-12-06 05:37:02.30 server SQL server listening on 69.9.44.XXX: 1433.
2005-12-06 05:37:02.30 server SQL server listening on 69.9.44.XXX: 1433.
2005-12-06 05:37:02.30 server SQL server listening on 69.9.44.XXX: 1433.
2005-12-06 05:37:02.30 server SQL server listening on 69.9.44.XXX: 1433.
2005-12-06 05:37:02.30 server SQL server listening on 127.0.0.1: 1433.
2005-12-06 05:37:02.30 server SuperSocket Info: Bind failed on TCP port 1433.
2005-12-06 05:37:02.30 server SuperSocket Info: Bind failed on TCP port 1433.
2005-12-06 05:37:02.32 server SQL server listening on TCP, Shared Memory.
2005-12-06 05:37:02.32 server SQL Server is ready for client connections
Even thought TCP is disabled|||Any more thoughts? Anyone?|||You're sure you are diabling TCP in the Server Network Parameters (or Server Network Utility)? The Client network utility looks the same, but it has a different function. Also, why the multiple IP addresses? I don't usually multi-home a database server (except for a cluster), so I don't know how SQL will behave with multiple IP addresses.
Regards,
hmscott
Wednesday, March 7, 2012
Redundant SQL server
Hi, good day everyone.
I would like to have a question here,
I want to configure a redundant SQL server. Let's said if server A is down, then server B can take over the workload of server A, and this is transparent to users which means they won't notify server A is down.
Besides the failover clustering method, is there any other solution?
My requirement is needed to run in Microsoft SQL 2000 standard edition and Microsoft Windows 2000 standard edition
Thanks,First, you need to determine what the business is willing to pay for that type of solution. I often find if it costs $100,000 to provide a undetectable failover with no data loss versus paying $5,000 to have a slightly detectable failover with up to 5 minutes of data loss, the business chooses the latter 95% of the time.
Once you've got budget commitment, you decide what approach you use.
In the real world, you are expected to do it for free. However, I always ask the above question the first time. That way, they're prepared the next time.
The answer to the question you are asking is entirely dependent on knowing the resources you have available to do it. Once you know that, let us know the details on what you have committed to do and we'll help you. You should expect hardware to not be an issue because you must have at least the same firepower as your production to ensure you can handle the load for an indefinite time.
Finally, the highest % (by a landslide) of failures that require you to failover are due to user error - for example, a 'DBA' forgetting a WHERE clause. You can handle that with the $5,000 option.|||FWIW: I would think that Windows Server 2003 might be a better option for the OS...|||a redundant server for SQL 2k is known as a standby server
in the absence of a clustered solution, log shipping can be used to copy transaction logs from server a to server b
the logs can be copied at any interval you wish and are restored to the server b database with the standby option.
with standby restores logs to the database places the db in a read only state and allows the subsequent restoration of tlog backups to server b until you change the with standby clause to with recovery.
the switch from SA to SB is much quicker than in prior editions becuase of the addition of stored procedures that will allow the mapping of logins and the changing of server roles.
Books Online {log shipping}|||Scott, that would be nice, except...Log Shipping is avalable only in EE, not standard. You can simulate log shipping behavior by doing it yourself through scheduled tasks, or you can ask someone to make copies of system stored procedures from the enterprise edition and semi-emulate its behavior.
EDITED: wait a minute, does it mean that SQL Server can qualify for "open source product" label?|||you might want to take some of your glycerin before you read this old man.
Scott, that would be nice, except...Log Shipping is avalable only in EE, not standard. You can simulate log shipping behavior by doing it yourself through scheduled tasks, or you can ask someone to make copies of system stored procedures from the enterprise edition and semi-emulate its behavior.
EDITED: wait a minute, does it mean that SQL Server can qualify for "open source product" label?
as you notice i invoked the "with standby" clause of restore and the phrase "standby server". this was to illustrate that it is a process available to all editions
while the sqlmaint process of log shipping and the sp's are exclusive to ent, standby servers are available to all systems.
let' s do lunch next week.|||blah-blah-blah...
OK, lunch sounds great! I'll give you a call.
I would like to have a question here,
I want to configure a redundant SQL server. Let's said if server A is down, then server B can take over the workload of server A, and this is transparent to users which means they won't notify server A is down.
Besides the failover clustering method, is there any other solution?
My requirement is needed to run in Microsoft SQL 2000 standard edition and Microsoft Windows 2000 standard edition
Thanks,First, you need to determine what the business is willing to pay for that type of solution. I often find if it costs $100,000 to provide a undetectable failover with no data loss versus paying $5,000 to have a slightly detectable failover with up to 5 minutes of data loss, the business chooses the latter 95% of the time.
Once you've got budget commitment, you decide what approach you use.
In the real world, you are expected to do it for free. However, I always ask the above question the first time. That way, they're prepared the next time.
The answer to the question you are asking is entirely dependent on knowing the resources you have available to do it. Once you know that, let us know the details on what you have committed to do and we'll help you. You should expect hardware to not be an issue because you must have at least the same firepower as your production to ensure you can handle the load for an indefinite time.
Finally, the highest % (by a landslide) of failures that require you to failover are due to user error - for example, a 'DBA' forgetting a WHERE clause. You can handle that with the $5,000 option.|||FWIW: I would think that Windows Server 2003 might be a better option for the OS...|||a redundant server for SQL 2k is known as a standby server
in the absence of a clustered solution, log shipping can be used to copy transaction logs from server a to server b
the logs can be copied at any interval you wish and are restored to the server b database with the standby option.
with standby restores logs to the database places the db in a read only state and allows the subsequent restoration of tlog backups to server b until you change the with standby clause to with recovery.
the switch from SA to SB is much quicker than in prior editions becuase of the addition of stored procedures that will allow the mapping of logins and the changing of server roles.
Books Online {log shipping}|||Scott, that would be nice, except...Log Shipping is avalable only in EE, not standard. You can simulate log shipping behavior by doing it yourself through scheduled tasks, or you can ask someone to make copies of system stored procedures from the enterprise edition and semi-emulate its behavior.
EDITED: wait a minute, does it mean that SQL Server can qualify for "open source product" label?|||you might want to take some of your glycerin before you read this old man.
Scott, that would be nice, except...Log Shipping is avalable only in EE, not standard. You can simulate log shipping behavior by doing it yourself through scheduled tasks, or you can ask someone to make copies of system stored procedures from the enterprise edition and semi-emulate its behavior.
EDITED: wait a minute, does it mean that SQL Server can qualify for "open source product" label?
as you notice i invoked the "with standby" clause of restore and the phrase "standby server". this was to illustrate that it is a process available to all editions
while the sqlmaint process of log shipping and the sp's are exclusive to ent, standby servers are available to all systems.
let' s do lunch next week.|||blah-blah-blah...
OK, lunch sounds great! I'll give you a call.
Subscribe to:
Posts (Atom)