This is terrible thing to happed at 4:30 pm on Friday!
I was working yesterday on some of deployment packages using file system (by the way, my msdb can not expand )
and just an hour ago I wanted to try some parent child deployment using file system.
but,
The only two folders I see in Integration services are Running Packages and Stored Packages. Nothing under those ones...
I have checked default location for File System (C:\Program Files\Microsoft SQL Server\90\DTS\Packages) and there are three packages there but these do not show in IServices.
And another question, if I execute package by double clicking on .dstx file should that make it show under File System?
thanks
Have you talked to the DBA? Sounds like access permissions, to me.|||Hi Ljiljana,
1) Answer to Phils question - Yes ? goto (2). No ? Contact your Admin for the Privilleges mentioned by Phil.
2) Open the Services window, Restart your Integration Service Instance. Successful ? goto (3), No ? Check if the Service account has necessary privileges.
3) Log into your SSMS using your Integration Services Instance, You might see List of Packages in your Folder - Yes ? End of the Step, No ? goto 4)
4) Are you running Integration Services in a Cluster Environment (Note that IS is not cluster aware). Yes? Configure your Integration Services as described here.
Reply, if you are still having issues
Thanks
Subhash Subramanyam
|||
Hi and thanks all!
Subhash, direction you gave me with msDTSsrvr.ini.xml helped.
This is an article I came across before when I wanted to resolve issue with msdb not being able to expand.
I wanted to add that my previous question was no so clear as I was able to see File System and MSDB (not expandable) and the Friday afternoon they disappeared.
Now that I think about what I have done was following;
I copied piece of code under Configuration File for a Named Instance of SQL Server from http://msdn2.microsoft.com/en-us/library/ms137789.aspx and added my server info. However, this has not changed anything for me as I forgot to restart SSIS.
Then on Friday mid day I shut down my PC and that is when that file kicked in creating more issues for me.
So I asked my coworker to send me his file and, except for server name where I had my info he had dot (.) the only other difference was following code (two last lines from the above link)
<?xml version="1.0" encoding="utf-8"?>
<DtsServiceConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
So I took these lines out, left my server info, restarted SSIS and it worked. All of it, including MSDB which I can expand now.
made me happy...
|||
Sorry, I do not know why part of the post is this bold and large; I was not yelling
