I know that you can't have an optimizer hint when running an ad-hoc query
from another server. My question is why? What prevents it from using the
hint?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200509/1PButler,
Use the OPENQUERY function instead of the 4 part name.
HTH
Jerry
"PButler via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:54C0F66FA391C@.SQLMonster.com...
>I know that you can't have an optimizer hint when running an ad-hoc query
> from another server. My question is why? What prevents it from using the
> hint?
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200509/1|||Thank you Jerry,
I guess I'm looking for a deeper explination of why? What prevents it from
using the hints in this way?
Also, Are there any performance issues with using OPENQUERY? Is it
faster/slower in general?
Jerry Spivey wrote:
>PButler,
>Use the OPENQUERY function instead of the 4 part name.
>HTH
>Jerry
>>I know that you can't have an optimizer hint when running an ad-hoc query
>> from another server. My question is why? What prevents it from using the
>> hint?
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200509/1|||If I had to guess I would guess that it is because of where the processing
occurs with respect to the 4 part name vs. OPENQUERY. You'll probably find
OPENQUERY slightly to much faster depending on the number of rows in the
destination table(s).
HTH
Jerry
"PButler via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:54C468F4CB638@.SQLMonster.com...
> Thank you Jerry,
> I guess I'm looking for a deeper explination of why? What prevents it
> from
> using the hints in this way?
> Also, Are there any performance issues with using OPENQUERY? Is it
> faster/slower in general?
> Jerry Spivey wrote:
>>PButler,
>>Use the OPENQUERY function instead of the 4 part name.
>>HTH
>>Jerry
>>I know that you can't have an optimizer hint when running an ad-hoc query
>> from another server. My question is why? What prevents it from using
>> the
>> hint?
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200509/1|||I am not a linked server expert but I suspect it has to do with the fact it
simply may not be supported on the other end. A linked server can be to
many things not just sql server. In addition to that there are distributed
transaction issues that may come into play. If you want all the features
supported you should create a stored proc on the lined server and call that.
Then all the processing is done on the other server just as if it was issued
locally and only the results are sent back.
--
Andrew J. Kelly SQL MVP
"PButler via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:54C468F4CB638@.SQLMonster.com...
> Thank you Jerry,
> I guess I'm looking for a deeper explination of why? What prevents it
> from
> using the hints in this way?
> Also, Are there any performance issues with using OPENQUERY? Is it
> faster/slower in general?
> Jerry Spivey wrote:
>>PButler,
>>Use the OPENQUERY function instead of the 4 part name.
>>HTH
>>Jerry
>>I know that you can't have an optimizer hint when running an ad-hoc query
>> from another server. My question is why? What prevents it from using
>> the
>> hint?
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200509/1
Showing posts with label prevents. Show all posts
Showing posts with label prevents. Show all posts
Sunday, March 25, 2012
(NOLOCK) and Linked Servers
I know that you can't have an optimizer hint when running an ad-hoc query
from another server. My question is why? What prevents it from using the
hint?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200509/1PButler,
Use the OPENQUERY function instead of the 4 part name.
HTH
Jerry
"PButler via droptable.com" <forum@.droptable.com> wrote in message
news:54C0F66FA391C@.droptable.com...
>I know that you can't have an optimizer hint when running an ad-hoc query
> from another server. My question is why? What prevents it from using the
> hint?
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200509/1|||Thank you Jerry,
I guess I'm looking for a deeper explination of why? What prevents it from
using the hints in this way?
Also, Are there any performance issues with using OPENQUERY? Is it
faster/slower in general?
Jerry Spivey wrote:[vbcol=seagreen]
>PButler,
>Use the OPENQUERY function instead of the 4 part name.
>HTH
>Jerry
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200509/1|||If I had to guess I would guess that it is because of where the processing
occurs with respect to the 4 part name vs. OPENQUERY. You'll probably find
OPENQUERY slightly to much faster depending on the number of rows in the
destination table(s).
HTH
Jerry
"PButler via droptable.com" <forum@.droptable.com> wrote in message
news:54C468F4CB638@.droptable.com...
> Thank you Jerry,
> I guess I'm looking for a deeper explination of why? What prevents it
> from
> using the hints in this way?
> Also, Are there any performance issues with using OPENQUERY? Is it
> faster/slower in general?
> Jerry Spivey wrote:
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200509/1|||I am not a linked server expert but I suspect it has to do with the fact it
simply may not be supported on the other end. A linked server can be to
many things not just sql server. In addition to that there are distributed
transaction issues that may come into play. If you want all the features
supported you should create a stored proc on the lined server and call that.
Then all the processing is done on the other server just as if it was issued
locally and only the results are sent back.
Andrew J. Kelly SQL MVP
"PButler via droptable.com" <forum@.droptable.com> wrote in message
news:54C468F4CB638@.droptable.com...
> Thank you Jerry,
> I guess I'm looking for a deeper explination of why? What prevents it
> from
> using the hints in this way?
> Also, Are there any performance issues with using OPENQUERY? Is it
> faster/slower in general?
> Jerry Spivey wrote:
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200509/1
from another server. My question is why? What prevents it from using the
hint?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200509/1PButler,
Use the OPENQUERY function instead of the 4 part name.
HTH
Jerry
"PButler via droptable.com" <forum@.droptable.com> wrote in message
news:54C0F66FA391C@.droptable.com...
>I know that you can't have an optimizer hint when running an ad-hoc query
> from another server. My question is why? What prevents it from using the
> hint?
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200509/1|||Thank you Jerry,
I guess I'm looking for a deeper explination of why? What prevents it from
using the hints in this way?
Also, Are there any performance issues with using OPENQUERY? Is it
faster/slower in general?
Jerry Spivey wrote:[vbcol=seagreen]
>PButler,
>Use the OPENQUERY function instead of the 4 part name.
>HTH
>Jerry
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200509/1|||If I had to guess I would guess that it is because of where the processing
occurs with respect to the 4 part name vs. OPENQUERY. You'll probably find
OPENQUERY slightly to much faster depending on the number of rows in the
destination table(s).
HTH
Jerry
"PButler via droptable.com" <forum@.droptable.com> wrote in message
news:54C468F4CB638@.droptable.com...
> Thank you Jerry,
> I guess I'm looking for a deeper explination of why? What prevents it
> from
> using the hints in this way?
> Also, Are there any performance issues with using OPENQUERY? Is it
> faster/slower in general?
> Jerry Spivey wrote:
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200509/1|||I am not a linked server expert but I suspect it has to do with the fact it
simply may not be supported on the other end. A linked server can be to
many things not just sql server. In addition to that there are distributed
transaction issues that may come into play. If you want all the features
supported you should create a stored proc on the lined server and call that.
Then all the processing is done on the other server just as if it was issued
locally and only the results are sent back.
Andrew J. Kelly SQL MVP
"PButler via droptable.com" <forum@.droptable.com> wrote in message
news:54C468F4CB638@.droptable.com...
> Thank you Jerry,
> I guess I'm looking for a deeper explination of why? What prevents it
> from
> using the hints in this way?
> Also, Are there any performance issues with using OPENQUERY? Is it
> faster/slower in general?
> Jerry Spivey wrote:
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200509/1
(NOLOCK) and Linked Servers
I know that you can't have an optimizer hint when running an ad-hoc query
from another server. My question is why? What prevents it from using the
hint?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200509/1
PButler,
Use the OPENQUERY function instead of the 4 part name.
HTH
Jerry
"PButler via droptable.com" <forum@.droptable.com> wrote in message
news:54C0F66FA391C@.droptable.com...
>I know that you can't have an optimizer hint when running an ad-hoc query
> from another server. My question is why? What prevents it from using the
> hint?
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200509/1
|||Thank you Jerry,
I guess I'm looking for a deeper explination of why? What prevents it from
using the hints in this way?
Also, Are there any performance issues with using OPENQUERY? Is it
faster/slower in general?
Jerry Spivey wrote:[vbcol=seagreen]
>PButler,
>Use the OPENQUERY function instead of the 4 part name.
>HTH
>Jerry
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200509/1
|||If I had to guess I would guess that it is because of where the processing
occurs with respect to the 4 part name vs. OPENQUERY. You'll probably find
OPENQUERY slightly to much faster depending on the number of rows in the
destination table(s).
HTH
Jerry
"PButler via droptable.com" <forum@.droptable.com> wrote in message
news:54C468F4CB638@.droptable.com...
> Thank you Jerry,
> I guess I'm looking for a deeper explination of why? What prevents it
> from
> using the hints in this way?
> Also, Are there any performance issues with using OPENQUERY? Is it
> faster/slower in general?
> Jerry Spivey wrote:
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200509/1
|||I am not a linked server expert but I suspect it has to do with the fact it
simply may not be supported on the other end. A linked server can be to
many things not just sql server. In addition to that there are distributed
transaction issues that may come into play. If you want all the features
supported you should create a stored proc on the lined server and call that.
Then all the processing is done on the other server just as if it was issued
locally and only the results are sent back.
Andrew J. Kelly SQL MVP
"PButler via droptable.com" <forum@.droptable.com> wrote in message
news:54C468F4CB638@.droptable.com...
> Thank you Jerry,
> I guess I'm looking for a deeper explination of why? What prevents it
> from
> using the hints in this way?
> Also, Are there any performance issues with using OPENQUERY? Is it
> faster/slower in general?
> Jerry Spivey wrote:
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200509/1
from another server. My question is why? What prevents it from using the
hint?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200509/1
PButler,
Use the OPENQUERY function instead of the 4 part name.
HTH
Jerry
"PButler via droptable.com" <forum@.droptable.com> wrote in message
news:54C0F66FA391C@.droptable.com...
>I know that you can't have an optimizer hint when running an ad-hoc query
> from another server. My question is why? What prevents it from using the
> hint?
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200509/1
|||Thank you Jerry,
I guess I'm looking for a deeper explination of why? What prevents it from
using the hints in this way?
Also, Are there any performance issues with using OPENQUERY? Is it
faster/slower in general?
Jerry Spivey wrote:[vbcol=seagreen]
>PButler,
>Use the OPENQUERY function instead of the 4 part name.
>HTH
>Jerry
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200509/1
|||If I had to guess I would guess that it is because of where the processing
occurs with respect to the 4 part name vs. OPENQUERY. You'll probably find
OPENQUERY slightly to much faster depending on the number of rows in the
destination table(s).
HTH
Jerry
"PButler via droptable.com" <forum@.droptable.com> wrote in message
news:54C468F4CB638@.droptable.com...
> Thank you Jerry,
> I guess I'm looking for a deeper explination of why? What prevents it
> from
> using the hints in this way?
> Also, Are there any performance issues with using OPENQUERY? Is it
> faster/slower in general?
> Jerry Spivey wrote:
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200509/1
|||I am not a linked server expert but I suspect it has to do with the fact it
simply may not be supported on the other end. A linked server can be to
many things not just sql server. In addition to that there are distributed
transaction issues that may come into play. If you want all the features
supported you should create a stored proc on the lined server and call that.
Then all the processing is done on the other server just as if it was issued
locally and only the results are sent back.
Andrew J. Kelly SQL MVP
"PButler via droptable.com" <forum@.droptable.com> wrote in message
news:54C468F4CB638@.droptable.com...
> Thank you Jerry,
> I guess I'm looking for a deeper explination of why? What prevents it
> from
> using the hints in this way?
> Also, Are there any performance issues with using OPENQUERY? Is it
> faster/slower in general?
> Jerry Spivey wrote:
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200509/1
Thursday, March 22, 2012
(Cancel this) Can’t paste into XML field in Management Studio.
Hi Folks,
It looks like Management Studio prevents pasting XML directly into a field of the type xml. Sometimes, it might be best to stay with varchar(max).
Original post below: >>
I want to paste some XML into an SQL Server 2005 xml type field, but the null is grayed out and paste simply does not work. What is going on?
Thanks,
Rob
Rob:
I see the same behavior. It appears to me that the COPY function is not active for the XML field and that you cannot directly modify it. You can copy from the XML field, but you cannot paste into it. I suggest that you use an XML query to update your field?
Sunday, March 11, 2012
"Polling" problem prevents ReportServer to start/work properly
When I start ReportServer I get error in the "Polling" the following error in the LogFiles:
<Header>
<Product>Microsoft SQL Server Reporting Services Version 9.00.1399.00</Product>
<Locale>en-US</Locale>
<TimeZone>W. Europe Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles\ReportServerService__01_02_2006_20_16_38.log</Path>
<SystemName>********</SystemName>
<OSName>Microsoft Windows NT 5.0.2195 Service Pack 4</OSName>
<OSVersion>5.0.2195.262144</OSVersion>
</Header>
ReportingServicesService!library!4!1/2/2006-20:16:38:: i INFO: Initializing ConnectionType to '0' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file.
ReportingServicesService!configmanager!4!1/2/2006-20:16:39:: w WARN: WebServiceAccount is not specified in the config file. Using default: SEMACLW2K237\ASPNET
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing ProcessRecycleOptions to '0' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file.
ReportingServicesService!resourceutilities!4!1/2/2006-20:16:39:: i INFO: Reporting Services starting SKU: Developer
ReportingServicesService!resourceutilities!4!1/2/2006-20:16:39:: i INFO: Evaluation copy: 0 days left
ReportingServicesService!runningjobs!4!1/2/2006-20:16:39:: i INFO: Database Cleanup (NT Service) timer enabled: Next Event: 600 seconds. Cycle: 600 seconds
ReportingServicesService!runningjobs!4!1/2/2006-20:16:39:: i INFO: Running Requests Scavenger timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
ReportingServicesService!runningjobs!4!1/2/2006-20:16:39:: i INFO: Running Requests DB timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
ReportingServicesService!runningjobs!4!1/2/2006-20:16:39:: i INFO: Execution Log Entry Expiration timer enabled: Next Event: 20600 seconds. Cycle: 86400 seconds
ReportingServicesService!runningjobs!4!1/2/2006-20:16:39:: i INFO: Memory stats update timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
ReportingServicesService!runningjobs!4!1/2/2006-20:16:39:: i INFO: SQM timer timer enabled: Next Event: 24200 seconds. Cycle: 86400 seconds
ReportingServicesService!library!8!1/2/2006-20:16:39:: i INFO: Catalog SQL Server Edition = Developer
ReportingServicesService!crypto!8!1/2/2006-20:16:39:: i INFO: Initializing crypto as user: NT AUTHORITY\SYSTEM
ReportingServicesService!crypto!8!1/2/2006-20:16:39:: i INFO: Exporting public key
ReportingServicesService!crypto!8!1/2/2006-20:16:39:: i INFO: Performing sku validation
ReportingServicesService!crypto!8!1/2/2006-20:16:39:: i INFO: Importing existing encryption key
ReportingServicesService!dbpolling!8!01/02/2006-20:16:39:: EventPolling polling service started
ReportingServicesService!dbpolling!a!1/2/2006-20:16:39:: EventPolling heartbeat thread started.
ReportingServicesService!dbpolling!8!01/02/2006-20:16:40:: NotificationPolling polling service started
ReportingServicesService!dbpolling!b!1/2/2006-20:16:40:: NotificationPolling heartbeat thread started.
ReportingServicesService!dbpolling!8!01/02/2006-20:16:40:: SchedulePolling polling service started
ReportingServicesService!dbpolling!8!01/02/2006-20:16:40:: UpgradePolling polling service started
ReportingServicesService!dbpolling!c!1/2/2006-20:16:40:: Polling started
ReportingServicesService!dbpolling!c!1/2/2006-20:16:40:: Polling caught an exception, restarting polling. Error Message System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.Diagnostics.WebConfigUtil.GetWebConfigAuthenticationAttribute(String attrName)
at Microsoft.ReportingServices.Diagnostics.WebConfigUtil.GetAuthenticationType()
at Microsoft.ReportingServices.Diagnostics.WebConfigUtil.get_AuthenticationType()
at Microsoft.ReportingServices.Library.NotificationQueueWorker.get_PollCommand()
at Microsoft.ReportingServices.Library.DBPoll.PollingFunction()
at Microsoft.ReportingServices.Library.DBPoll.PollingStartFunction().
ReportingServicesService!dbpolling!4!1/2/2006-20:24:52:: EventPolling polling service stopped
ReportingServicesService!dbpolling!a!1/2/2006-20:24:52:: EventPolling heartbeat thread exiting for stop.
ReportingServicesService!dbpolling!4!1/2/2006-20:24:52:: NotificationPolling polling service stopped
ReportingServicesService!dbpolling!b!1/2/2006-20:24:52:: NotificationPolling heartbeat thread exiting for stop.
ReportingServicesService!dbpolling!4!1/2/2006-20:24:52:: SchedulePolling polling service stopped
ReportingServicesService!dbpolling!4!1/2/2006-20:24:52:: UpgradePolling polling service stopped
ReportingServicesService!servicecontroller!4!1/2/2006-20:24:52:: Service controller exiting.
Any hints would be most helpful. I'm running on Win2000, SQL 2005 and IIS 5.0.
Thanks in advance
Johan Lindell
I'm having this exact same error.
I am running on Windows XP Pro, IIS 5.1, and SQL 2005.
|||Can you check if the following attribute is in the web.config file:
xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0
If so, then remove it all (attribute name and value).
|||I had that... I removed it and it worked perfectly.
Thanks Daniel!
|||Good to hear. This is an issue with VS adding this attribute. If you edit the file in notepad you should not have to worry about this."Polling" problem prevents ReportServer to start/work properly
When I start ReportServer I get error in the "Polling" the following error in the LogFiles:
<Header>
<Product>Microsoft SQL Server Reporting Services Version 9.00.1399.00</Product>
<Locale>en-US</Locale>
<TimeZone>W. Europe Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles\ReportServerService__01_02_2006_20_16_38.log</Path>
<SystemName>********</SystemName>
<OSName>Microsoft Windows NT 5.0.2195 Service Pack 4</OSName>
<OSVersion>5.0.2195.262144</OSVersion>
</Header>
ReportingServicesService!library!4!1/2/2006-20:16:38:: i INFO: Initializing ConnectionType to '0' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file.
ReportingServicesService!configmanager!4!1/2/2006-20:16:39:: w WARN: WebServiceAccount is not specified in the config file. Using default: SEMACLW2K237\ASPNET
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing ProcessRecycleOptions to '0' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
ReportingServicesService!library!4!1/2/2006-20:16:39:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file.
ReportingServicesService!resourceutilities!4!1/2/2006-20:16:39:: i INFO: Reporting Services starting SKU: Developer
ReportingServicesService!resourceutilities!4!1/2/2006-20:16:39:: i INFO: Evaluation copy: 0 days left
ReportingServicesService!runningjobs!4!1/2/2006-20:16:39:: i INFO: Database Cleanup (NT Service) timer enabled: Next Event: 600 seconds. Cycle: 600 seconds
ReportingServicesService!runningjobs!4!1/2/2006-20:16:39:: i INFO: Running Requests Scavenger timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
ReportingServicesService!runningjobs!4!1/2/2006-20:16:39:: i INFO: Running Requests DB timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
ReportingServicesService!runningjobs!4!1/2/2006-20:16:39:: i INFO: Execution Log Entry Expiration timer enabled: Next Event: 20600 seconds. Cycle: 86400 seconds
ReportingServicesService!runningjobs!4!1/2/2006-20:16:39:: i INFO: Memory stats update timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
ReportingServicesService!runningjobs!4!1/2/2006-20:16:39:: i INFO: SQM timer timer enabled: Next Event: 24200 seconds. Cycle: 86400 seconds
ReportingServicesService!library!8!1/2/2006-20:16:39:: i INFO: Catalog SQL Server Edition = Developer
ReportingServicesService!crypto!8!1/2/2006-20:16:39:: i INFO: Initializing crypto as user: NT AUTHORITY\SYSTEM
ReportingServicesService!crypto!8!1/2/2006-20:16:39:: i INFO: Exporting public key
ReportingServicesService!crypto!8!1/2/2006-20:16:39:: i INFO: Performing sku validation
ReportingServicesService!crypto!8!1/2/2006-20:16:39:: i INFO: Importing existing encryption key
ReportingServicesService!dbpolling!8!01/02/2006-20:16:39:: EventPolling polling service started
ReportingServicesService!dbpolling!a!1/2/2006-20:16:39:: EventPolling heartbeat thread started.
ReportingServicesService!dbpolling!8!01/02/2006-20:16:40:: NotificationPolling polling service started
ReportingServicesService!dbpolling!b!1/2/2006-20:16:40:: NotificationPolling heartbeat thread started.
ReportingServicesService!dbpolling!8!01/02/2006-20:16:40:: SchedulePolling polling service started
ReportingServicesService!dbpolling!8!01/02/2006-20:16:40:: UpgradePolling polling service started
ReportingServicesService!dbpolling!c!1/2/2006-20:16:40:: Polling started
ReportingServicesService!dbpolling!c!1/2/2006-20:16:40:: Polling caught an exception, restarting polling. Error Message System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.Diagnostics.WebConfigUtil.GetWebConfigAuthenticationAttribute(String attrName)
at Microsoft.ReportingServices.Diagnostics.WebConfigUtil.GetAuthenticationType()
at Microsoft.ReportingServices.Diagnostics.WebConfigUtil.get_AuthenticationType()
at Microsoft.ReportingServices.Library.NotificationQueueWorker.get_PollCommand()
at Microsoft.ReportingServices.Library.DBPoll.PollingFunction()
at Microsoft.ReportingServices.Library.DBPoll.PollingStartFunction().
ReportingServicesService!dbpolling!4!1/2/2006-20:24:52:: EventPolling polling service stopped
ReportingServicesService!dbpolling!a!1/2/2006-20:24:52:: EventPolling heartbeat thread exiting for stop.
ReportingServicesService!dbpolling!4!1/2/2006-20:24:52:: NotificationPolling polling service stopped
ReportingServicesService!dbpolling!b!1/2/2006-20:24:52:: NotificationPolling heartbeat thread exiting for stop.
ReportingServicesService!dbpolling!4!1/2/2006-20:24:52:: SchedulePolling polling service stopped
ReportingServicesService!dbpolling!4!1/2/2006-20:24:52:: UpgradePolling polling service stopped
ReportingServicesService!servicecontroller!4!1/2/2006-20:24:52:: Service controller exiting.
Any hints would be most helpful. I'm running on Win2000, SQL 2005 and IIS 5.0.
Thanks in advance
Johan Lindell
I'm having this exact same error.
I am running on Windows XP Pro, IIS 5.1, and SQL 2005.
|||Can you check if the following attribute is in the web.config file:
xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0
If so, then remove it all (attribute name and value).
|||I had that... I removed it and it worked perfectly.
Thanks Daniel!
|||Good to hear. This is an issue with VS adding this attribute. If you edit the file in notepad you should not have to worry about this.Thursday, March 8, 2012
"Login timeout expired" prevents package deployment
I'm trying to deploy an SSIS package to a server ("SQL Server" deployment). The package does have an encrypted password, which has both worked nicely and not in the past. It's entirely possible that our other "DBA" has busted something on the server, thus preventing my access to it, but I'm curious if anyone has any experience w/ error code 0x80004005 (Login timeout expired) in the SaveToSqlServer method.
Thanks for any help,
Ben
===================================
Could not save the package "C:\Documents and Settings\foo\bar\bin\Deployment\foo.dtsx" to SQL Server "BAR". (Package Installation Wizard)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
Hi Ben,
Did you ever receive a response to this issue? We're experiencing the exact same error.
Thanks!
Kim -
|||I just wonder if there is a firewall in place blocking RPC or something.|||Hi - Did anyone ever receive a response to this thread? I am having the exact same problem.
Thanks!!
Tyra
|||All of the sudden I am getting this also. No password on packages. Config files used. Was able to install to SSIS server before, the same package. This was to update a package. I can still import from SSIS manager. I tried both integrated auth and SQL auth with no success. Careful, after it throws up gthe error on screen, the process looks like it could finish successfully, and tells you it does. Your old script is left though.
SSIS is running on the same server as I run the package manifest from. Tried killing SQL server agaent so no packages would run while installing, no luck.
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired)
===================================
Could not save the package "C:\DtsDeploy\UpdateDevAdpDms\Load_SoHeaderDim.dtsx" to SQL Server "(local)". (Package Installation Wizard)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
It had been 3 whole days since I last deployed a package, so I guess I forgot how.
I think my problem was using the deployment package. I figured since it was the SSIS deployment utility, it was installing to the SSIS (Integration Servcies) which does not have a named instance. All of my Database engines are named (SQLSERVER/myInstance).
When you use the SSIS deployment utility, you are installing the packages to the Database engine, not the Integration Services....so you have to specify which instance to install the package to. If I am wrong, then there is something wrong with my SQL install.
SO in short, make sure you are using the right server name and instance when deploying packages.
"Login timeout expired" prevents package deployment
I'm trying to deploy an SSIS package to a server ("SQL Server" deployment). The package does have an encrypted password, which has both worked nicely and not in the past. It's entirely possible that our other "DBA" has busted something on the server, thus preventing my access to it, but I'm curious if anyone has any experience w/ error code 0x80004005 (Login timeout expired) in the SaveToSqlServer method.
Thanks for any help,
Ben
===================================
Could not save the package "C:\Documents and Settings\foo\bar\bin\Deployment\foo.dtsx" to SQL Server "BAR". (Package Installation Wizard)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
Hi Ben,
Did you ever receive a response to this issue? We're experiencing the exact same error.
Thanks!
Kim -
|||I just wonder if there is a firewall in place blocking RPC or something.|||Hi - Did anyone ever receive a response to this thread? I am having the exact same problem.
Thanks!!
Tyra
|||
All of the sudden I am getting this also. No password on packages. Config files used. Was able to install to SSIS server before, the same package. This was to update a package. I can still import from SSIS manager. I tried both integrated auth and SQL auth with no success. Careful, after it throws up gthe error on screen, the process looks like it could finish successfully, and tells you it does. Your old script is left though.
SSIS is running on the same server as I run the package manifest from. Tried killing SQL server agaent so no packages would run while installing, no luck.
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired)
===================================
Could not save the package "C:\DtsDeploy\UpdateDevAdpDms\Load_SoHeaderDim.dtsx" to SQL Server "(local)". (Package Installation Wizard)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
"Login timeout expired" prevents package deployment
I'm trying to deploy an SSIS package to a server ("SQL Server" deployment). The package does have an encrypted password, which has both worked nicely and not in the past. It's entirely possible that our other "DBA" has busted something on the server, thus preventing my access to it, but I'm curious if anyone has any experience w/ error code 0x80004005 (Login timeout expired) in the SaveToSqlServer method.
Thanks for any help,
Ben
===================================
Could not save the package "C:\Documents and Settings\foo\bar\bin\Deployment\foo.dtsx" to SQL Server "BAR". (Package Installation Wizard)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
Hi Ben,
Did you ever receive a response to this issue? We're experiencing the exact same error.
Thanks!
Kim -
|||I just wonder if there is a firewall in place blocking RPC or something.|||Hi - Did anyone ever receive a response to this thread? I am having the exact same problem.
Thanks!!
Tyra
|||All of the sudden I am getting this also. No password on packages. Config files used. Was able to install to SSIS server before, the same package. This was to update a package. I can still import from SSIS manager. I tried both integrated auth and SQL auth with no success. Careful, after it throws up gthe error on screen, the process looks like it could finish successfully, and tells you it does. Your old script is left though.
SSIS is running on the same server as I run the package manifest from. Tried killing SQL server agaent so no packages would run while installing, no luck.
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired)
===================================
Could not save the package "C:\DtsDeploy\UpdateDevAdpDms\Load_SoHeaderDim.dtsx" to SQL Server "(local)". (Package Installation Wizard)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
It had been 3 whole days since I last deployed a package, so I guess I forgot how.
I think my problem was using the deployment package. I figured since it was the SSIS deployment utility, it was installing to the SSIS (Integration Servcies) which does not have a named instance. All of my Database engines are named (SQLSERVER/myInstance).
When you use the SSIS deployment utility, you are installing the packages to the Database engine, not the Integration Services....so you have to specify which instance to install the package to. If I am wrong, then there is something wrong with my SQL install.
SO in short, make sure you are using the right server name and instance when deploying packages.
"Login timeout expired" prevents package deployment
I'm trying to deploy an SSIS package to a server ("SQL Server" deployment). The package does have an encrypted password, which has both worked nicely and not in the past. It's entirely possible that our other "DBA" has busted something on the server, thus preventing my access to it, but I'm curious if anyone has any experience w/ error code 0x80004005 (Login timeout expired) in the SaveToSqlServer method.
Thanks for any help,
Ben
===================================
Could not save the package "C:\Documents and Settings\foo\bar\bin\Deployment\foo.dtsx" to SQL Server "BAR". (Package Installation Wizard)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
Hi Ben,
Did you ever receive a response to this issue? We're experiencing the exact same error.
Thanks!
Kim -
|||I just wonder if there is a firewall in place blocking RPC or something.|||Hi - Did anyone ever receive a response to this thread? I am having the exact same problem.
Thanks!!
Tyra
|||
All of the sudden I am getting this also. No password on packages. Config files used. Was able to install to SSIS server before, the same package. This was to update a package. I can still import from SSIS manager. I tried both integrated auth and SQL auth with no success. Careful, after it throws up gthe error on screen, the process looks like it could finish successfully, and tells you it does. Your old script is left though.
SSIS is running on the same server as I run the package manifest from. Tried killing SQL server agaent so no packages would run while installing, no luck.
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired)
===================================
Could not save the package "C:\DtsDeploy\UpdateDevAdpDms\Load_SoHeaderDim.dtsx" to SQL Server "(local)". (Package Installation Wizard)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
It had been 3 whole days since I last deployed a package, so I guess I forgot how.
I think my problem was using the deployment package. I figured since it was the SSIS deployment utility, it was installing to the SSIS (Integration Servcies) which does not have a named instance. All of my Database engines are named (SQLSERVER/myInstance).
When you use the SSIS deployment utility, you are installing the packages to the Database engine, not the Integration Services....so you have to specify which instance to install the package to. If I am wrong, then there is something wrong with my SQL install.
SO in short, make sure you are using the right server name and instance when deploying packages.
"Login timeout expired" prevents package deployment
I'm trying to deploy an SSIS package to a server ("SQL Server" deployment). The package does have an encrypted password, which has both worked nicely and not in the past. It's entirely possible that our other "DBA" has busted something on the server, thus preventing my access to it, but I'm curious if anyone has any experience w/ error code 0x80004005 (Login timeout expired) in the SaveToSqlServer method.
Thanks for any help,
Ben
===================================
Could not save the package "C:\Documents and Settings\foo\bar\bin\Deployment\foo.dtsx" to SQL Server "BAR". (Package Installation Wizard)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)
===================================
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
Hi Ben,
Did you ever receive a response to this issue? We're experiencing the exact same error.
Thanks!
Kim -
|||I just wonder if there is a firewall in place blocking RPC or something.|||Hi - Did anyone ever receive a response to this thread? I am having the exact same problem.
Thanks!!
Tyra
Subscribe to:
Posts (Atom)