Could not allocate space for object because the 'PRIMARY' filegroup is full

Hi,
I hope that someome could help me with this issue and give me some hints on how resolve it.
The issue is with the job optimization. first, let me give you some settings :

I have an application that have a db in SQLServer 2000. The application have created a mainteance plan that does the folowing :
- Optimization :
* Reoganize data and indexes pages
** change free space per page percentage to : 10%
* Remove unused space from database file
** Shrink database when it grows beyond : 50 MB
** Amount of free space to remain after shrink : 10%

For information, xp_fixeddrives gives me :
C : 5331
D : 174932 -> all dbs files are located here
E : 3817
S : 33044


The db itself have the folowing size, according to the taskpad view :
* Space allocated
** Data : 110785 MB (106753 used, 4032 free)
** Log : 175.99 MB (14.19 used, 161.8 free)

Also, the data and log system files are on the D: drive

For the data file settings :
* Space allocated for data : 110787 MB (PRIMARY)
* Auto grow file is set, file growth in MB : 256
* Max file size, restrict file grow : 110880
For the Log file settings :
* Space allocated for data : 176 MB (PRIMARY)
* Auto grow file is set, file growth in MB : 128
* Max file size, restrict file grow : 22176


The tempdb now,
* Space allocated
** Data : 8 MB (1.12 used, 6.88 free)
** Log : 0.74 MB (0.34 used, 0.4 free)

Also, the data and log system files are on the D: drive

For the data file settings :
* Space allocated for data : 8 MB (PRIMARY)
* Auto grow file is set, by percent : 10
* unrestricted file growth
For the Log file settings :
* Space allocated for data : 1 MB (PRIMARY)
* Auto grow file is set, by percent : 10
* unrestricted file growth

Now, for the issue itself, everytime the optimization job is launch, the error log gives me :
Could not allocate space for object '(SYSTEM table id: -637536758)' in database 'DB' because the 'PRIMARY' filegroup is full..

I have cheked on the internet without finding the right way to solve this issue and I am not an expert in SQLServer 2000.

I suspect that when the job is launch, the reindexing or the remove spave operation is filling the DB space to the max but I not sure of this...
What setting should I need to modify in order to the job to complete without failure? I am pretty sure that some settings ar e not correct or that I need to add more space to the DB, but what and where is the question...
The only drive that I can use is the D drive whitch has as you can see plenty of free space.

Please, give me any hints to tricks that could help me (and others).
If you need more details, feel free to ask.
Thanks.

Don't shrink db, there are enough free space and shrinking db will affect performance. To rebuild index, db usually needs around 20% free space. So set db file size limit to proper value. By the way, why don't put db log files on other disk array?