I am going through the same thing and have concluded you have to upgrade Vista. When I bought the computer, I asked everybody I could find about that issue and got many shoulder shrugs. Apparently, you and I are the only people trying to run SSRS off a home addition of Vista.
Follow-up:
At the end of the sp2 install there is an applet that runs to give admin rights on SQL. Apparently, when you install SQL 2005 on Vista, they don't grant admin rights to the win account of the dbo.
Also, I found out, I have to upgrade from the home elete or what ever I have to get...
I am installing SQL 2005 (64)on my new machine and I have 2 issues I hope someone can help with:
1 The installation cannot see the IIS so I can't install reporting services.
2 When the installation is complete, I don't have a management studio or the Business Intelligence studio.
Does anybody...
I have an .MDE on my desktop for testing. When I open it and load data, everything is fine. However, if I open a second instance of the app, and load a second set of data, the data in the first instance is lost. What is happening?
To be specific, can you run regsvr32 from Access?
I have a custom DLL I want to register to an undetermined number of users.
In order to do this, I plan to trap the 429 error and call Regsvr32.exe to register the DLL and continue the program.
I am having a problem linking tables in a replica. When I direct the links in the design master, they are not changed in the replica. When I go to the replica and try to direct the links I get the error that I can't do that in a replica.
The only way I can get it done is to designate the...
How do you keep the error message from appearing when the "Not in List" event fires. I am handling the error and I know there is a trick to it but I can't find it.
I have seen that error when I accidently connected through a 97 workgroup.
Also, MDE files are version specific so if someone has a 2002 version you will probably get a similar error.
Name the first two queries. That will save them and you can refer to them in the third query.
If you don't want them hanging around, delete them after the routine runs.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.