Do Sql 2005 and Access not play well together?

Does anyone know if I can't put Access 2003 and SQL 2005 on the same server together? I've got an old, well not that old, application that was farmed out coming back home and apparently it's backend is Access and the frontend is ASP, I think. Anyway, the power's that be would like to upgrade to SQL 2005 and would like everything on the same box together. I've heard rumors that's not possible... Does anyone have any ideas? Thanks a ton.

Nicole (not Anna) Smith

It is NOT a problem to install both Access and SQL Server on the same computer.|||Well as Arnie said, in general it is no problem, don′t know if this is officially supported (like outlook and Exchange isn′t), but I also saw that many times working smootly.

Jens K. Suessmeyer.

http://www.sqlserver2005.desql

Distruibuted Reports showing old machine name in the url.

I have a machine with Sql Server 2005 running the Reporting Services. The
server runs both the front-end and back-end.
I change the machine name after installation of Sql Server 2005 and the
Reporting Services.
I subscribed to a report, but the report is delivered to me with the old
machine name in the url.
E.g.
http://ewisql4/reportserver?%2fUNAUTHORIZED+JOB+CREATION+MONITORING%2fUNAUTHORIZED+JOB+CREATION+ORS&rs%3aParameterLanguage=en-US
But it should be:
http://ewisql3/reportserver?%2fUNAUTHORIZED+JOB+CREATION+MONITORING%2fUNAUTHORIZED+JOB+CREATION+ORS&rs%3aParameterLanguage=en-US
What can do to resolve this? Thanks in advanceHi,
Try to change the SSRS box name in the %Program Files%\Microsoft SQL
Server\MSSQL.3\Reporting Services\ReportServer\ folder,
rsreportserver.config file.
Change the value of the <UrlRoot>http://ewisql4/reportserver</UrlRoot> to
<UrlRoot>http://ewisql3/reportserver</UrlRoot> or whatever the new server
name.
Restart the SSRS service, then try to render the report again.
I hope it will help for you.
Regards,
Janos
"yardi4life" <yardi4life.nospam@.discussions.microsoft.com> wrote in message
news:6C3C9E0C-0F36-4DDD-BB2F-F960FED4299F@.microsoft.com...
>I have a machine with Sql Server 2005 running the Reporting Services. The
> server runs both the front-end and back-end.
> I change the machine name after installation of Sql Server 2005 and the
> Reporting Services.
> I subscribed to a report, but the report is delivered to me with the old
> machine name in the url.
> E.g.
> http://ewisql4/reportserver?%2fUNAUTHORIZED+JOB+CREATION+MONITORING%2fUNAUTHORIZED+JOB+CREATION+ORS&rs%3aParameterLanguage=en-US
> But it should be:
> http://ewisql3/reportserver?%2fUNAUTHORIZED+JOB+CREATION+MONITORING%2fUNAUTHORIZED+JOB+CREATION+ORS&rs%3aParameterLanguage=en-US
> What can do to resolve this? Thanks in advance
>
>

Distrubuter has sick hardware. Need to change box.

We run our distribution on another server ie not on the publisher.
We have had some hardware errors and to be honest it's an old machine and
spares are getting sparse.
Is there a step by step for moving distribution to another server?
Thanks
Paul
The short answer is no. The longer answer is no there is not step by step
guide for moving a distributor to another server.
An even longer answer is, no, but it is possible to do a tape restore to the
new distributor with the same name bounce it and hope for the best. I don't
like remote distributors. DBAs IMHO are too quick to migrate to them, and
you need to cluster them otherwise you have a single point of failure which
can be problematic for you as you have discovered.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Paul Cahill" <noname@.anon.com> wrote in message
news:e6FVdryzFHA.2792@.tk2msftngp13.phx.gbl...
> We run our distribution on another server ie not on the publisher.
> We have had some hardware errors and to be honest it's an old machine and
> spares are getting sparse.
> Is there a step by step for moving distribution to another server?
> Thanks
> Paul
>

Distribution clean up: distribution job not removing snapshots

On SQL Server 2005 SP2 for Publisher and Distributor on the same instance, my old snapshots are not being cleaned up.

The following error is in the agent history:

Executed as user: Domain\MyUser. Could not remove directory '\\vmsql01\ReplData\unc\Publication_TRANSACTIONAL\20070702104416\'. Check the security context of xp_cmdshell and close other processes that may be accessing the directory. [SQLSTATE 42000] (Error 20015). The step failed.

xp_cmdshell is enabled and I can run commands like :

exec master.dbo.xp_cmdshell ' md c:\TestFolder\'

The permissions to the snapshot share and file system are that Domain\MyUser has full control.

I have logged into the machine as this user and can remove snapshots so it does not seem to be a permission issue.

On other machines I do not get any errors but the snapshot folder still is not cleaned up.

Any suggestion as to what the problem could be?

Thanks,

Amy

hi amy,

i think there's a sql job in msdb

if i quite remember well to do the

clean up

you may manually trigger

regards,

joey

|||

Update:

I ran filemonitor while the cleanup job was running and noticed it was telling me the user that owns the SQL Server Service had access denied errors. I gave that user permissions to the snapshot folder and it is now cleaning up (well any of the really old stuff it is not but anything that has expired lately it has cleaned up).

My SQLUser1 owns the SQL Server Server and SQLUser2 owns the SQL Server Agent Service.

I thought the SQLUser2 would be the one who required permissions to the snapshot folder to clean it up?

Does xp_cmdshell need to be enabled for the cleanup job to work? I have not found anything in BOL to suggest that but ...

The other machines are still running cleanup jobs without error and still not removing any snapshots.

Any suggestions?

Thanks,

Amy